Ek Google encoded polyline kya hai?

Yeh latitude/longitude points ke ek path ka ek compact ASCII encoding hai, jo Google ke Encoded Polyline Algorithm Format se define hota hai. Directions aur Roads APIs routes is tarah return karti hain kyunki string coordinates ki poori list se kaafi chhoti hoti hai, aur yeh wapas exact points par decode ho jaati hai.

Apni polyline ke liye mujhe precision 5 use karni chahiye ya 6?

Google Maps aur Google Directions API ke liye 5 use karein, aur OSRM, Valhalla, GraphHopper aur Mapbox ke liye 6. Precision 6 ek extra decimal rakhti hai, isliye 6 par encode ki gayi lekin 5 par decode ki gayi string lagbhag das guna door land karti hai — hamesha us tool se match karein jisne polyline banai.

Main ek encoded polyline ko GeoJSON mein kaise convert karoon?

Decode par switch karein, polyline paste karein, aur tool plain coordinate list ke saath-saath ek GeoJSON LineString Feature output karta hai. GeoJSON pehle se [longitude, latitude] order use karta hai, isliye aap use seedha geojson.io, Leaflet ya ek mapping library mein paste kar sakte hain.

Kya main ek GeoJSON LineString ko ek polyline mein encode kar sakta hoon?

Haan. Encode mode mein aap ek GeoJSON LineString paste kar sakte hain, ya use wrap karne wala ek Feature ya FeatureCollection, aur tool uske coordinates padhta hai aur encoded string return karta hai. Agar aapke paas GeoJSON nahi hai to aap plain "lat, lng" lines bhi paste kar sakte hain.

Kya jab main encode ya decode karta hoon to mera route data kahin bheja jaata hai?

Nahi. Encoding aur decoding standard algorithm use karke poori tarah aapke browser mein chalti hain, isliye aap jo coordinates aur polylines paste karte hain woh aapke device par process hote hain aur kabhi kisi server par upload nahi hote.

Polyline Encoder / Decoder

Coordinates ko ek Google polyline string mein encode karein ya use wapas lat/lng aur GeoJSON mein decode karein, seedha aapke browser mein. Aapka route aapke device par rehta hai.

Aap jo coordinates aur polyline strings paste karte hain woh aapke browser mein locally encode aur decode hote hain aur kabhi upload nahi hote; jo aap enter karte hain woh kisi server par store nahi hota.

Route ko map par dekhna hai? Coordinate Map Viewer kholein.

Polyline Encoder ke baare mein

Yeh polyline encoder aur decoder Google ke Encoded Polyline Algorithm Format ko poori tarah aapke browser mein handle karta hai. Encode mode mein, ek line par ek "lat, lng" paste karein — ya ek GeoJSON LineString — aur woh compact encoded string paayein jo Directions APIs ek route ke liye return karti hain. Decode mode mein, ek encoded polyline paste karein aur coordinate list plus ek ready-to-use GeoJSON LineString padhein jise aap ek map mein daal sakte hain. Ek precision toggle 5 (Google Maps default) aur 6 (OSRM, Valhalla aur Mapbox dwara use) ke beech switch karta hai, jo aksar wajah hoti hai ki ek decoded route galat jagah land karta hai. Polylines ek poore path ko ek chhoti ASCII string mein pack karte hain, isliye yeh tab kaam ka hai jab ek API aapko ek encoded route deti hai aur aapko plain coordinates chahiye hote hain, ya iska ulta. Sab kuch aapke device par compute hota hai aur aap jo route paste karte hain woh kabhi upload nahi hota.

Features

Lat/lng coordinates ki ek list ko ek Google Encoded Polyline string mein encode karein
Ek polyline ko wapas coordinates aur ek equivalent GeoJSON LineString mein decode karein
Dono directions ke liye precision 5 (Google Maps) ya 6 (OSRM, Valhalla, Mapbox) toggle karein
Encode input ke roop mein ek line par ek "lat, lng", ya ek GeoJSON LineString / Feature accept karta hai
Ek GeoJSON LineString emit karta hai jise aap seedha ek map ya geojson.io mein paste kar sakte hain
Ek wrong-precision decode ko flag karta hai, jo route ke ~10x door land karne ki classic wajah hai
Encoded string, coordinate list, ya GeoJSON ko ek click mein copy karein
Apna route paste karne se pehle format dekhne ke liye ek canonical example load karein

Polyline Encoder kaise use karein

Coordinates ko ek polyline mein badalne ke liye Encode chunein, ya ek ko expand karne ke liye Decode.
Apne data source se match karne ke liye precision 5 (Google) ya 6 (OSRM/Valhalla) chunein.
Coordinates paste karein (ek line par ek "lat, lng" ya ek GeoJSON LineString), ya ek encoded polyline.
Results mein encoded string padhein, ya coordinate list aur GeoJSON LineString.
Apne map, API request, ya data file ke liye koi bhi output copy karein.

Example

Input

38.5, -120.2
40.7, -120.95
43.252, -126.453

Output

_p~iF~ps|U_ulLnnqC_mqNvxq`@

Google ke docs se canonical teen-point route, precision 5 par encode kiya gaya.

Common errors aur troubleshooting

Ek decoded route lagbhag das guna door offset ya scaled hai. — Precision mismatch hai. Google aur Google Maps 5 use karte hain; OSRM, Valhalla aur Mapbox 6 use karte hain. Jo bhi string bana usse match karne ke liye precision toggle switch karein.
Decoded points sahi lagte hain lekin map line samundar mein draw karta hai. — Polylines aur yeh tool pehle latitude store karte hain, lekin GeoJSON positions [longitude, latitude] hoti hain. Pairs khud swap karne ke bajaye GeoJSON output ko waisa hi use karein.
Decoding ek "malformed polyline" message ke saath ruk jaati hai. — String truncated thi ya extra characters ke saath copy ki gayi. Poori polyline copy karein, aur koi aaspaas ke quotes ya JSON escaping jaise ek doubled backslash hata dein.

Aksar pooche jaane wale sawaal

Ek Google encoded polyline kya hai?: Yeh latitude/longitude points ke ek path ka ek compact ASCII encoding hai, jo Google ke Encoded Polyline Algorithm Format se define hota hai. Directions aur Roads APIs routes is tarah return karti hain kyunki string coordinates ki poori list se kaafi chhoti hoti hai, aur yeh wapas exact points par decode ho jaati hai.
Apni polyline ke liye mujhe precision 5 use karni chahiye ya 6?: Google Maps aur Google Directions API ke liye 5 use karein, aur OSRM, Valhalla, GraphHopper aur Mapbox ke liye 6. Precision 6 ek extra decimal rakhti hai, isliye 6 par encode ki gayi lekin 5 par decode ki gayi string lagbhag das guna door land karti hai — hamesha us tool se match karein jisne polyline banai.
Main ek encoded polyline ko GeoJSON mein kaise convert karoon?: Decode par switch karein, polyline paste karein, aur tool plain coordinate list ke saath-saath ek GeoJSON LineString Feature output karta hai. GeoJSON pehle se [longitude, latitude] order use karta hai, isliye aap use seedha geojson.io, Leaflet ya ek mapping library mein paste kar sakte hain.
Kya main ek GeoJSON LineString ko ek polyline mein encode kar sakta hoon?: Haan. Encode mode mein aap ek GeoJSON LineString paste kar sakte hain, ya use wrap karne wala ek Feature ya FeatureCollection, aur tool uske coordinates padhta hai aur encoded string return karta hai. Agar aapke paas GeoJSON nahi hai to aap plain "lat, lng" lines bhi paste kar sakte hain.
Kya jab main encode ya decode karta hoon to mera route data kahin bheja jaata hai?: Nahi. Encoding aur decoding standard algorithm use karke poori tarah aapke browser mein chalti hain, isliye aap jo coordinates aur polylines paste karte hain woh aapke device par process hote hain aur kabhi kisi server par upload nahi hote.

Related tools

GeoJSON Viewer — GeoJSON ko validate karein aur map par preview karein, feature summary aur bounding box ke saath.
GPX se GeoJSON — GPX ko GeoJSON mein aur wapas convert karein — GPS tracks, routes aur waypoints ko GeoJSON features, ya GeoJSON ko wapas GPX file mein.
Coordinate Converter — Ek lat/long pair ko decimal degrees, DMS aur DDM ke beech convert karein.
Coordinate Map Viewer — Latitude/longitude ko OpenStreetMap map par plot karein aur click se coordinates padhein.
GeoJSON se CSV — Ek GeoJSON FeatureCollection ko CSV mein aur wapas convert karein — Point features apni properties ke saath latitude/longitude columns bante hain.
WKT se GeoJSON — WKT (Well-Known Text) ko GeoJSON mein aur wapas convert karein, aapke browser mein.