Download a sample GeoJSON file of any size
Choose the data and the size, then download. Every file is valid GeoJSON (RFC 7946), made on your device.
- Valid GeoJSON
- Points, lines, polygons
- 100 KB to 1 GB
- Nothing is uploaded
Download a sample GeoJSON file in the size you need, from 100 KB to 1 GB, to test a map, a spatial import or a GeoJSON parser. Each file is one FeatureCollection of places around seven cities: mostly points, with some lines and polygons, each with properties such as name, category and rating. The file is written in your browser. To look inside a big one, open it in the Large JSON Viewer. For other kinds of test data, see Sample JSON files.
What people use these files for
- Test a map
See how Leaflet, Mapbox or OpenLayers draws thousands of features, and where it slows down.
- Check a spatial import
Load the file into PostGIS with ogr2ogr, or into QGIS, and check the geometry and properties.
- Test a parser
Check that your code reads points, lines and polygons, and longitude before latitude.
- Check an upload limit
Pick a size just under or over your limit to see how your form or API responds.
To cut a big file into smaller ones, use the JSON Splitter.
How to get a sample GeoJSON file
- Choose a size from 100 KB to 1 GB, or type a custom size. The file holds whole features and stays within it.
- Click Generate and download, or Open in GigaJSON instead to look inside it.
- Open the .geojson file in your map, GIS tool or code.
Private, and made for big files
This tool runs in your browser, in a background worker: the file is made on your computer and never uploaded, and nothing is kept after you leave. Files up to 1 GB are written in pieces, so the page keeps responding. Already loaded features keep working if your connection drops. Loading another tool or jq for the first time needs a connection. When one tool isn't enough, GigaJSON opens your data with a tree, a table, JSONPath/JMESPath/jq queries, transforms, diff and history.
Sample GeoJSON questions
What is in a sample GeoJSON file?
One FeatureCollection. About 70% of the features are points, and the rest are lines and polygons, all near Portland, Berlin, Lagos, Osaka, Lima, Oslo and Pune. Each feature has properties: id, name, category, city, rating, open and updated.
Is it valid GeoJSON?
Yes. It follows RFC 7946: positions are [longitude, latitude] in WGS 84 with six decimals, and each polygon's outer ring is closed (its last position repeats the first) and runs counterclockwise.
Where can I open it?
Anything that reads GeoJSON: QGIS, PostGIS through ogr2ogr, Leaflet, Mapbox GL and OpenLayers. Small files also work in geojson.io. To read the raw data, open it in GigaJSON.
Is the file the same every time?
Yes. The same size always gives the same file, which helps when a test needs to be repeatable.
Is anything uploaded?
No. The file is made in your browser and saved from there. Nothing is kept after you leave.
All tools
- JSON FormatterIndent with 2 or 4 spaces, sort keys
- JSON ValidatorLine and column of the first error
- JSON MinifierRemove whitespace, see the bytes saved
- JSON RepairFixes quotes, commas, comments, AI output
- JSON Schema GeneratorA JSON Schema from examples
- JSON Schema ValidatorCheck JSON against a schema
- JSON Token CounterCount tokens, select data, compare JSON and TOON
- JSON EditorTree and code editing, undo and history
- Large JSON ViewerTree, table and search for huge files
- JSON Lines ViewerJSONL and NDJSON logs as a table
- JSON Log ViewerCount and filter JSON Lines logs
- Large CSV ViewerCSV files too big for Excel, up to 1 GB
- JSON VisualizerThe data as a graph, PNG and SVG export
- JSON DiffChanges between two documents
- JSON Path FinderClick a value, copy its path
- JSONPath TesterJSONPath, JMESPath and jq, live
- JMESPath PlaygroundJMESPath, for AWS CLI queries too
- jq PlaygroundReal jq in your browser
- JSON to CSVNested objects become dotted columns
- JSON to ExcelAn .xlsx sheet, numbers kept as numbers
- CSV to JSONDelimiters detected, 007 stays 007
- JSON to XML@keys become attributes
- XML to JSONRSS feeds, sitemaps, SOAP responses
- JSON to YAMLReadable YAML, ambiguous strings quoted
- YAML to JSONAnchors and multiple documents
- JSON Lines to JSONNDJSON or JSONL into one array
- JSON to JSON LinesA JSON array as one record per line
- JSON to TOONConvert JSON to TOON, with token counts
- JSON to MermaidA flowchart or class diagram, drawn
- JSON SplitterCut a big file into parts, or sample it
- JSON to TypeScriptInterfaces inferred from your data
- JSON to GoGo structs with json tags
- JSON to RustRust structs that derive serde's Serialize and Deserialize
- JSON to PythonPython dataclasses with type hints
- JSON to JavaJava classes with getters and setters
- JSON to C#C# classes with System.Text.Json attributes
- JSON to KotlinKotlin data classes
- JSON to SwiftSwift structs that conform to Codable, with CodingKeys
- JSON to DartDart classes with fromJson and toJson
- JSON to ZodZod schemas with TypeScript types inferred from them
- JWT DecoderHeader, payload and expiry, locally
- JSON EscapeText to a JSON string and back
- Sample JSON FilesDownload test JSON, 100 KB to 1 GB
- Sample JSON Lines FilesDownload test NDJSON, one record per line
- Sample CSV FilesDownload test CSV, 100 KB to 1 GB
- Sample XML FilesDownload test XML, 100 KB to 1 GB
- Sample GeoJSON FilesPoints, lines and polygons, up to 1 GB
- Sample Nested JSONRecords 8 levels deep, up to 1 GB
- Sample Unicode JSON13 scripts, emoji and escapes
- Sample API ResponsesJSON:API, HAL, GraphQL, pages, errors
- Large JSON File GeneratorTest data from 100 KB to 1 GB