Sample GeoJSON, GPX and KML files — free download
Geospatial fixtures for mapping pipelines: point and track data, a KML placemark set, plus the two cases that break naive geo code — antimeridian crossing and out-of-range coordinates.
5 ready-made geospatial test files
| File | Size | What it catches | |
|---|---|---|---|
| placemarks.kml | 508 bytes | Google Earth / Maps import and any KML parser. Includes a <Style> block, so it catches readers that render geometry but silently drop styling. | download |
| antimeridian.geojson | 592 bytes | The classic map bug: renderers that draw a horizontal line all the way across the world instead of wrapping at the date line. Also catches bbox maths that assumes min<max longitude. | download |
| track.gpx | 596 bytes | Fitness and mapping apps. Includes elevation and ISO-8601 timestamps, so it catches parsers that ignore <ele> or mishandle the timezone on <time>. | download |
| malformed-coords.geojson | 682 bytes | Validation beyond "is it JSON". A latitude above 90 and an unclosed polygon ring are both invalid per RFC 7946; a robust importer rejects or repairs them rather than plotting a point off the globe. | download |
| points.geojson | 1.2 KB | Map ingestion and GIS import. Covers all three core geometry types plus a feature with mixed property types, so a viewer that only handles points will visibly drop the rest. | download |
Every file is generated from source — no third-party copyright — and each has its own page with a published SHA-256 you can verify after download.
Questions
Where can I download a sample GeoJSON file?
The points GeoJSON below is a valid FeatureCollection, ready to drop into Leaflet, Mapbox or QGIS.
What is the antimeridian problem?
A line crossing longitude 180 either renders correctly or wraps the wrong way around the globe. The antimeridian file makes that bug visible immediately.