GeoJSON to CSV / KML / GPX
Convert GeoJSON FeatureCollections into CSV tables, KML, or GPX — 100% private client-side processing.
Active Converter
GeoJSON to CSV / KML / GPX: Exporting Mapbox, Leaflet & PostGIS Layers
Technical Anatomy of RFC 7946 GeoJSON
GeoJSON (RFC 7946) is the dominant spatial data interchange format for modern web mapping APIs. Every valid .geojson file defines a FeatureCollection containing an array of Feature objects. Each feature combines a geometry (Point, MultiPoint, LineString, or Polygon in WGS84 [lon, lat] order) with a properties JSON map holding domain attributes.
While browsers render GeoJSON natively inside Leaflet or Mapbox GL, field technicians need GPX for handheld GPS devices, executives want KML for Google Earth presentations, and analysts need flat CSV coordinate tables for Excel and Power BI.
Raw GeoJSON FeatureCollection vs. Spreadsheet & KML Output
// Input: PostGIS / Mapbox Export (towers.geojson)
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": { "name": "5G Tower North", "status": "active" },
"geometry": { "type": "Point", "coordinates": [-6.8498, 34.0209] }
}
]
}
# Converted .CSV Output:
Name,Latitude,Longitude,Properties
"5G Tower North",34.0209,-6.8498,"status=active"
Real-World Software & Hardware Ecosystem
GIS developers and urban planners export .geojson layers from QGIS, PostGIS (ST_AsGeoJSON), geojson.io, Mapbox Studio, OpenStreetMap Overpass Turbo, and Leaflet, then convert them to CSV, KML, or GPX without installing GDAL/OGR command-line binaries.
Troubleshooting & Edge Cases
- Projected CRS (EPSG:3857 Web Mercator) Coordinates: Strict RFC 7946 mandates WGS84 degrees (
-180..180,-90..90). If your coordinates look like huge numbers (e.g.,-762518.4, 4031592.1), reproject from EPSG:3857 to EPSG:4326 in QGIS before exporting to KML/GPX. - TopoJSON vs. GeoJSON: TopoJSON encodes shared arcs mathematically to shrink file size and uses
"type": "Topology"instead of"FeatureCollection"; convert TopoJSON to GeoJSON first. - Null Geometries: Database exports occasionally emit features with
"geometry": null; our converter skips null geometries safely without throwing runtime errors.
RFC 7946 GeoJSON Geometry Types & Nesting Depth
| Geometry Type | Coordinate Array Nesting | Common GIS Application |
|---|---|---|
| Point | [lon, lat] | Store locators, cell towers, IoT sensors |
| LineString | [[lon, lat], ...] | Fiber routes, pipelines, transit corridors |
| Polygon | [[[lon, lat], ...]] | Delivery zones, postal codes, geofences |
Exporting GeoJSON Directly from PostGIS SQL
-- Generate an RFC 7946 GeoJSON FeatureCollection straight from PostgreSQL/PostGIS:
SELECT json_build_object('type', 'FeatureCollection',
'features', json_agg(ST_AsGeoJSON(t.*)::json)) FROM delivery_zones AS t;
Frequently Asked Questions
A GeoJSON FeatureCollection wraps an array of Feature objects, each pairing a geometry object (Point, LineString, Polygon with [longitude, latitude] arrays) alongside a free-form properties dictionary holding metadata like population, postal code, or sensor readings.
RFC 7946 follows standard Cartesian X,Y axis convention (East-West longitude first, North-South latitude second). When exporting to CSV, we split them into explicit Longitude and Latitude columns so spreadsheet users never mix them up.
Yes. Select Export .KML to wrap every GeoJSON Feature into a Google Earth
Property attributes (such as name, category, or ID) are carried alongside the extracted coordinates so your tabular dataset retains full GIS context.