GeoJSON Validator (RFC 7946 Compliance)
Validate GeoJSON syntax, coordinate ordering [longitude, latitude], ring closures, and RFC 7946 specifications with line error reports.
The GeoJSON Validator performs real-time syntax and topological compliance checking against the official IETF RFC 7946 GeoJSON standard. It validates coordinate ordering ([longitude, latitude]), polygon ring closure, linear ring winding direction, bounding box values, and JSON hierarchy with line-by-line error reports.
RFC 7946 Validation Report
All 6 Standard Conformance Checks Passed:
- Valid JSON Syntax & Root Type Structure
- Coordinate Ordering: [Longitude, Latitude] WGS84
- Coordinate Boundaries: Longitude [-180, 180], Latitude [-90, 90]
- Polygon Rings: Correctly closed (First vertex equals Last vertex)
- Feature & Geometry Attribute Specifications
GeoJSON Validator Technical Specifications & Standards
WGS84 (EPSG:4326)
Standard global ellipsoidal coordinate reference system
IETF Geodesics
Strict syntax and semantic validation
GeoJSON · KML · CSV · SVG
Compatible with QGIS, ArcGIS, Google Earth & CAD
100% Client-Side
Calculations run in-browser. Zero coordinate logging.
How to Use the GeoJSON Validator (RFC 7946 Compliance)
Follow this step-by-step procedure to execute precise spatial measurements and export results.
- 1Paste GeoJSON code: Paste your raw GeoJSON FeatureCollection or Geometry into the code editor.
- 2Inspect validation status: Review the automated compliance scorecard (Pass / Fail).
- 3Check identified issues: Inspect highlighted errors including reversed coordinates, unclosed rings, or missing geometry fields.
- 4Fix and re-test: Correct syntax errors directly in the editor to achieve 100% RFC 7946 validation.
Geodesic Precision vs. Competitor Mapping Approaches
Most legacy mapping utilities (such as CalcMaps and FreeMapTools) rely on planar Web Mercator projections or spherical approximations, causing significant mathematical distortion at higher latitudes. GeoMap Suite computes exact ellipsoidal geodesics on the WGS84 reference ellipsoid.
| Calculation Model | Mathematical Basis | Distortion on WGS84 | Standard Tools | Practical Application |
|---|---|---|---|---|
| Planar (Web Mercator) | Cartesian dx² + dy² | 10% to 200%+ error | CalcMaps / Simple map tools | Distorts drastically away from equator. Inaccurate for true distance. |
| Spherical Great-Circle | Haversine (R = 6,371 km) | Up to 0.5% (~5 km/1,000 km) | Basic Google Maps wrappers | Ignores Earth's polar flattening. Reasonable for rough estimates. |
| GeoMap Suite Ellipsoidal | Karney Direct/Inverse WGS84 | < 15 nanometers (<0.0001%) | GeoMap Suite | Geodetic surveying, maritime, flight paths & legal boundary analysis. |
Worked Example: Detecting Reversed Coordinate Error [Lat, Lng]
A developer troubleshoots why their GeoJSON polygon appears in Antarctica instead of San Francisco.
Input Parameters
- Faulty Geometry
- Point coordinates: [37.7749, -122.4194]
Computed Outputs
- Rule Failed
- RFC 7946 Coordinate Ordering
- Error
- Latitude -122.4194 exceeds [-90, 90]
- Resolution
- Swap array order to [Longitude, Latitude]
Step-by-Step Mathematical Process
- Evaluate RFC 7946 Section 3.1.1 (Position ordering: [longitude, latitude, elevation]).
- Detect that longitude value (37.7749) and latitude value (-122.4194) are inverted because latitude must be between -90 and +90.
- Flag fatal error: "Invalid Latitude -122.4194 out of range [-90, 90]".
- Suggest fix: Invert to [-122.4194, 37.7749].
Understanding Your Results & Practical Interpretation
The Right-Hand Rule (Winding Order)
RFC 7946 requires that exterior polygon rings follow a counter-clockwise winding order, and interior holes follow a clockwise winding order.
Practical Applications & Real-World Use Cases
API Integration Testing
Verify spatial API endpoints return valid RFC 7946 payloads before production deployment.
MapLibre & Mapbox Debugging
Diagnose why custom vector layers fail to render in client-side mapping engines.
Mathematical Methodology & Geodetic Accuracy
IETF RFC 7946 Compliance Rules Engine
Validates JSON abstract syntax tree (AST) against GeoJSON schema specifications and geometric topology constraints.
Validate(GeoJSON) -> { IsValid: boolean, Errors: string[], Warnings: string[] }Limitations & Boundary Conditions
- •Complex polygon self-intersection validation requires O(N log N) Bentley-Ottmann sweep-line analysis.
Authoritative Reference Standards
Troubleshooting & Geographic Edge Cases
Why does RFC 7946 require [Longitude, Latitude]?
In Cartesian mathematics, X comes before Y. Since Longitude represents horizontal X and Latitude represents vertical Y, GeoJSON uses [X, Y] = [Lng, Lat].
Frequently Asked Questions
RFC 7946 (published in 2016 by the IETF) removed support for alternative non-WGS84 coordinate reference systems (mandating EPSG:4326), standardized the right-hand winding rule for polygons, and deprecated crs member objects.