Geographic & Coordinate Tools

GeoJSON Validator

Validate a bounded structural GeoJSON profile locally, inspect geometry and see explicit warnings.

Your content stays on your device Free, with no account
GeoJSON Validator · private geographic toolsLocal analysis · no map requests

Coordinates & source

No file selected.

UTF-8 · 1 MiB / 200,000 UTF-16 units. Invalid imports retain previous working text.

Text coordinate lines use latitude, longitude. GeoJSON arrays use longitude, latitude. Elevation is informational and is ignored for distance/area.

Enter coordinates or load the example to begin.

Scope & measurement model

Measurements use a sphere of radius 6,371,008.8 m and minor great-circle legs, not a WGS84 ellipsoidal geodesic or terrain/road route. No live location, geocoding, map tiles or magnetic declination. Coordinates are interpreted as WGS84 lon/lat.

GeoJSON: 200,000 UTF-16 units, 50,000 JSON tokens, 5,000 positions, 1,000 features, geometry nesting ≤16. Supported structural profile, not full topology certification; empty coordinate arrays and legacy CRS are outside scope. Polygon area: one Polygon, ≤1,000 non-closing vertices, all within 89.4° of a common exterior center; rejects crossing/touching/nested holes and ambiguous/degenerate rings.

GPX: supported 1.0/1.1 geometry extraction, not full XSD validation. DTD/entity directives reject. Links/extensions are ignored. Segments stay separate; elevation/time do not create speed, travel time or 3D distance estimates. Local worker timeout 10 seconds.

References: GeoJSON RFC 7946 · GPX 1.1 schema. These links open only if you choose them.

LOCAL COORDINATE VIEW

Geometry & result

Unprojected longitude/latitude diagram · no basemap. Drag to pan, wheel or +/− to zoom, arrows to pan, F to fit. Select a feature below to inspect it.

No geometry loaded.

    A FEW SIMPLE STEPS

    How to use GeoJSON Validator

    1. Enter coordinates, paste source or choose a local UTF-8 file. Coordinate lines use latitude then longitude; GeoJSON arrays use longitude then latitude.
    2. Run locally, review model/scope warnings and inspect the actual geometry. Pan, zoom, fit or use fullscreen; feature visibility changes only the view.
    3. Check measurements, individual route legs or feature properties. Reports retain unrounded calculated values.
    4. Download the actual view PNG, source/result GeoJSON or analysis reports. Clear or workspace switching releases local data.
    PRIVATE BY DESIGN

    Why use this tool?

    Your coordinates, routes and local files never leave your browser. All parsing, validation, drawing and calculations run locally without external map tiles, accounts, live-location requests or file uploads.

    Tool inputs stay in your browser. Only your theme preference is saved on this device.

    A few things worth knowing

    Does the viewer need an external basemap?

    No. It draws an interactive, unprojected longitude/latitude diagram using only your geometry and a coordinate grid. It does not load map tiles, place labels, imagery or external styles.

    Are these survey-grade or live routing results?

    No. Measurements use a sphere of radius 6,371,008.8 m and shortest great-circle legs. They are not ellipsoidal, road/terrain or cadastral results. Bearing is true rather than magnetic and may be undefined near degenerate endpoints. Route tools sum your supplied segments without inventing connections across gaps.

    What does GeoJSON validation cover?

    A bounded structural profile: supported types, finite geographic positions, required Feature members, minimum line/ring sizes and exact ring closure. It reports winding/dateline/bbox caveats. It does not certify full RFC compliance, topology, overlap, hole containment or geographic accuracy. Polygon Area has a separate bounded simple-ring/hole check.

    Are files or properties uploaded or executed?

    No. UTF-8 files stay local with filename, size and loading/ready/error status. Property strings and GPX XML are treated as inert data; links/extensions are never loaded. Invalid imports keep previous working text. Source/settings edits invalidate old reports, and Clear/page exit releases application state.