GPX to GeoJSON Geo Format Converter

All six directions between GPX, KML and GeoJSON: GPX to KML or GeoJSON, KML to GPX or GeoJSON, and GeoJSON to GPX or KML. Choose the format of your file as From and the format you need as To.

Files up to 5 MiB and 10,000 features are converted. GPX and KML must be UTF-8 encoded XML, and GeoJSON must be a FeatureCollection, a Feature or a geometry in WGS84 longitude and latitude.

Waypoints become points, and tracks and routes become lines with their names, descriptions, elevations and point timestamps. Converting to GPX writes points as waypoints, lines as tracks, routes that came from GPX as routes again, and polygon outlines as track segments.

Each feature becomes a Placemark with its name, description and timestamp, and its simple properties are written to ExtendedData. Styles are not translated, so Google Earth shows the converted file with its default colors.

No. KMZ is a zipped KML archive, so unzip it first and upload the KML file inside, usually named doc.kml. Network links and ground overlays inside KML are not converted.

Placemarks with points, lines, polygons, multi geometries and Google Earth tracks are converted, including names, descriptions, timestamps and extended data. Folders are flattened into one list of features.

Yes. Elevations are carried as the third coordinate in GeoJSON and KML and as the ele element in GPX, in meters. Points without an elevation stay two-dimensional.

The file must match the From format: a GPX file needs a gpx root element, a KML file a kml root element, and GeoJSON must be valid JSON with coordinates in range. Files with a document type declaration are refused for security reasons.

No. The file is converted in memory during the request and the result is returned to you directly. The file itself is not kept after the response is sent.

GPX, KML and GeoJSON all use WGS84 longitude and latitude, so coordinates are copied without reprojection or rounding. GeoJSON in a projected coordinate system is not valid input.