Frequently asked questions
Plain-language answers about the converter, exports, and privacy.
- What JSON shape does this tool expect?
- A JSON array of objects. Each object should include numeric lat and lng (WGS84). Optional fields such as color, speed, battery, timestamp, and distance_to_route_m are preserved in GeoJSON properties and KML ExtendedData.
- Should I export as points or as a LineString?
- Use Points when each row is an independent observation you want as separate features. Use LineString when the array is ordered along a path and you want one continuous line (for example a vehicle route). In the app you can also sort by timestamp or reverse the array before export so the map and downloads stay in sync.
- Is there a fullscreen map or keyboard shortcut?
- Yes. Use the Fullscreen map control on the preview panel, or press F when focus is not inside a text field. Escape exits fullscreen. You can switch Google map types (roadmap, satellite, hybrid, terrain), hover the coordinate table to sync the map, and scrub through points when that option is enabled.
- What do the quick stats mean?
- Path length sums great-circle distances between successive points in the current order. Time span uses the earliest and latest parseable timestamps. Max speed and max off-route come from your numeric fields when present.
- What is the difference between KML and KMZ?
- KML is a single XML file. KMZ is a ZIP archive containing doc.kml (and optionally images). Most tools, including Google Earth, accept both. KMZ is convenient for sharing a single file.
- Does my data leave my computer?
- Parsing, conversion, and file downloads run entirely in your browser. The preview uses Google Maps when you add an API key; your pasted JSON is not uploaded to us for processing. Google’s terms and logging apply to map requests.