Merge LineStrings — Combine Coordinate Paths Into One KML Line
Free merge LineStrings tool for KML and map workflows: paste two lon,lat coordinate lists, join them into one continuous LineString, collapse duplicate joints, and copy coordinates or full KML for Google Earth. Ideal for stitching survey legs, route segments, and edited path pieces.
Key features
- Paste each path as space-separated lon,lat pairs (KML order)
- Order is LineString A then LineString B
- Shared endpoints are de-duplicated at the join
- Copy merged coordinates or a ready LineString KML block
What Merge LineStrings does
It concatenates two coordinate lists into one polyline. When line B starts where line A ends, the shared vertex is collapsed so Google Earth does not show a gap or duplicate spike at the joint.
Why local SEO and map teams use it
Stitch edited survey legs, recombine segmented coverage paths, or join route pieces after Segment LineString — then export a single KML LineString for Earth or GIS viewers.
Order and direction
Merge runs A then B. If the combined path should run the opposite way, use Reverse on the output or swap which list you paste into A vs B.
How to use this tool (best practice)
1) Paste LineString A as lon,lat pairs. 2) Paste LineString B. 3) Merge. 4) Copy coordinates or KML. Next: Segment LineString to divide, or Reader to extract from existing KML.
Frequently asked questions
Is this Merge LineStrings tool free?
Yes. It is free on GBP Local Ranker’s KML Workbench at /free-tools/kml-workbench/merge-linestrings — no login required for basic use.
What format should I paste?
Space-separated lon,lat pairs in KML order — for example: 78.3489,17.4401 78.35,17.441 78.36,17.442.
How many lines can I merge?
This UI merges two lists (A then B). Paste additional legs into the boxes in sequence, or merge output with another leg in a second pass.
Will order reverse automatically?
No. Order is A then B. Use Reverse if the combined path should run the other direction.
What happens at shared endpoints?
Duplicate joints at the join are collapsed so only one vertex remains at the shared location.
Does it work for closed polygons?
Designed for LineStrings. For rings, ensure the first and last point close after merge if you need a closed polygon.
Are altitude values kept?
Only lon,lat are kept — altitude tokens are not preserved in this merge UI.
Can I open the result in Google Earth?
Yes — copy the KML block into a .kml file and open it in Google Earth or compatible GIS tools.
How is this different from Segment LineString?
Merge joins paths together. Segment divides one path into equal-length pieces.
Where is the full KML Workbench suite?
Open All KML Workbench Tools at /free-tools/kml-workbench for reader, reverse, segment, circle generator, and more.