What the validator checks
JSON syntax — missing commas, trailing commas, unquoted keys and unbalanced brackets are reported with the line and column where parsing failed.
GeoJSON structure (RFC 7946)
typemust be FeatureCollection, Feature or a geometry type; features need ageometrymember (it may benull).- Positions must be arrays of at least two numbers.
- LineStrings need at least 2 positions; polygon rings need at least 4 and must be closed (first position = last).
- GeometryCollections must contain valid geometries.
Common mistakes (warnings)
- Coordinates outside ±180 / ±90 — usually latitude and longitude swapped, or data in a projected coordinate system.
- Unclosed rings — closed automatically when loading, and reported.
- Winding order — RFC 7946 recommends counterclockwise outer rings and clockwise holes. Many tools don't care, but some libraries do; press Fix winding order to rewind all polygons to the RFC 7946 order.
- The obsolete
crsmember.
Each issue shows a path such as features[2].geometry.coordinates[0] so you can find it in your file. Valid features are drawn on the map even if others fail.
How to use it
Paste into the GeoJSON tab (replacing the empty collection), press Validate, fix the text, and press Apply to map to see the result.