tuliq
TuliqGeospatialReference
ReferenceUpdated Sep 13, 2026

GeoJSON vs KML vs GPX vs Shapefile: Format Comparison

A quick side-by-side of file structure, coordinate systems, and typical use for the four most commonly compared geospatial formats.

Quick lookup for the four most commonly compared geospatial formats. For the fuller explanation of how each one works — plus CSV, WKT, and TopoJSON — see Geospatial File Formats.

GeoJSONKMLGPXShapefile
File layoutOne .json fileOne .kml fileOne .gpx file.zip bundle (.shp + .dbf + .prj)
GeometryPoint/Line/PolygonPoint/Line/PolygonPoint/Line onlyPoint/Line/Polygon
Coordinate order[longitude, latitude][longitude, latitude]lat/lon as separate attributesOften projected, not lat/lon at all
Coordinate systemAlways WGS84Always WGS84Always WGS84Often UTM/State Plane — needs a .prj to know
PropertiesArbitrary JSONName + descriptionName, time, elevation.dbf attribute table
Typical sourceWeb maps, APIsGoogle Earth, GIS exportsGPS devices, fitness appsDesktop GIS (QGIS, ArcGIS)

The one thing that actually differs in practice

GPX is the one format here that can't hold a Polygon at all — only points (waypoints) and lines (tracks/routes). If your data includes areas (a boundary, a zone), GPX simply isn't an option; GeoJSON, KML, or Shapefile all handle it fine.

Shapefile is the one format here that isn't reliably plain latitude/longitude — the other three always are. Opening or converting a Shapefile without accounting for its projection is the single most common way this format goes wrong.

Quick answer

Convert or verify a file

Tools mentioned in this guide

Related reading