All tools

GeoJSON Structural Validator

JSON

Validate a GeoJSON document against RFC 7946's structural rules: correct geometry type/coordinates shape, polygon ring closure and winding, and a FeatureCollection's required fields.

Utilix has no geo or mapping tools today despite GeoJSON being a widely used interchange format for everything from a map editor's export to an API response. This validator checks a document's structure against RFC 7946 itself, not just that it parses as JSON: the correct coordinates shape for each of the seven geometry types, closed linear rings for Polygon and MultiPolygon, a Feature's required properties and geometry members, and a FeatureCollection's required features array. It also flags a Polygon ring that winds the wrong way under RFC 7946's right-hand rule as a warning rather than an error, since plenty of real-world producers don't follow that recommendation and it would be wrong to fail validation over it. Everything runs as pure structural validation; no map is ever rendered and no tile server is contacted.

geojsongeovalidatorrfc7946mappinggis

How to use GeoJSON Structural Validator

  • 1.Paste a GeoJSON document: a bare geometry, a Feature, or a FeatureCollection.
  • 2.Read the errors list for structural problems like an unclosed polygon ring or a missing required member.
  • 3.Check the warnings list for non-failing issues, like a ring that winds the wrong way under the right-hand rule.

Frequently asked questions

Does this validate coordinate values against real-world latitude/longitude ranges?
No. It checks structure per RFC 7946 (position shape, ring closure, required members), not whether a coordinate pair falls within valid lat/lng bounds.
Why is a clockwise exterior ring a warning instead of an error?
RFC 7946's right-hand rule (counterclockwise exterior rings, clockwise interior rings) is a SHOULD, not a MUST, and many real-world GeoJSON producers don't follow it. Flagging it as a hard error would reject plenty of otherwise-valid documents.
Does it support GeometryCollection and nested geometries?
Yes, GeometryCollection is validated recursively, so an invalid geometry anywhere inside it is reported with its own path.
Is my GeoJSON uploaded anywhere?
No, the browser tool validates entirely client-side. The REST API and SDKs process whatever document you send them, same as any other API call.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/geojson-validator \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"geojson":"{\"type\":\"Point\",\"coordinates\":[30,10]}"}'

Get an API key from your dashboard · Full API docs →

Related tools

.editorconfig ValidatorParse an .editorconfig file into its root flag and glob sections, and flag structural mistakes: unknown properties, invalid values for known properties, a root declaration outside the preamble, and duplicate properties within a sectionCodeARIA Role & Attribute ValidatorCheck every role and aria-* attribute in a pasted HTML snippet against a curated WAI-ARIA 1.2 role table: unknown roles, attributes not permitted on a given role, and widget roles missing a required aria-* stateCodeBarcode Checksum ValidatorValidate EAN-13, EAN-8, and UPC-A barcode numbers via their weighted mod-10 check digit algorithmCode