GeoJSON Viewer & Editor

View GeoJSON features on an interactive map with editing, styling, and property inspection.

Tested tool guide Tested browser tools Checked August 16, 2026

What GeoJSON Viewer & Editor does, with a checked example

GeoJSON Viewer & Editor turns pasted GeoJSON into mapped points, lines, and polygons while keeping each feature connected to its properties. The interactive view helps you inspect locations, revise features, and apply styling that makes overlapping or related data easier to distinguish. The common surprise is coordinate order: RFC 7946 positions place longitude before latitude. Reversing a familiar latitude-longitude pair can move a feature to an entirely different location even when both numbers remain valid.

Worked example

A concrete input and expected output from the current implementation.

Input

{"type":"Feature","properties":{"name":"Origin"},"geometry":{"type":"Point","coordinates":[0,0]}}

Expected output

The map displays one Point at longitude 0 and latitude 0, where the prime meridian meets the equator. Its inspected properties show name as Origin.

A GeoJSON Point takes its position directly from the coordinates array in longitude, latitude order. The name member belongs to the feature's properties and describes the mapped point without changing its position.

How the result is produced

Mapping GeoJSON features

Paste a GeoJSON feature or collection into the editor to see its geometries on the interactive map. Point coordinates identify individual positions, LineString coordinates describe connected paths, and Polygon coordinates describe boundary rings. Selecting a mapped feature exposes its associated properties, allowing the geometry and descriptive fields to be checked together.

Editing and styling

Use the editing controls to revise GeoJSON features and observe the resulting geography in the map view. Styling controls change how features are visually distinguished, which is useful when several geometries overlap or share similar shapes. Processing occurs in the browser, so pasted coordinates and properties are not uploaded, a relevant consideration for unpublished location data.

Good uses

Check an API response containing delivery zones to confirm that its Polygon features cover the intended areas and retain their zone identifiers.
Inspect a FeatureCollection of survey points to compare mapped locations with property fields such as sample ID, status, or collection date.
Correct misplaced route coordinates and give multiple LineString features contrasting styles so their paths can be compared visually.

Limits and checks

GeoJSON positions use longitude, latitude order. A reversed pair may still contain two valid numbers, so the viewer cannot reliably determine that the author's intended order was different.
RFC 7946 GeoJSON uses geographic coordinates based on WGS 84. Projected eastings and northings are not interchangeable with longitude and latitude and can produce absent or severely misplaced features.
A geometry appearing plausible on the map does not prove that it is topologically sound. Self-intersections, overlapping polygons, unintended duplicate positions, or inaccurate source coordinates may still require dedicated validation.

Common questions

Can one FeatureCollection contain different geometry types?

Yes. GeoJSON permits a FeatureCollection to contain features with different geometries, so points, lines, and polygons can be viewed together when represented as separate Feature objects. Each feature can also have its own properties. This is useful for checking relationships such as a point lying within a boundary or a route crossing several regions.

Will latitude and longitude fields inside properties place a feature on the map?

No. Map placement comes from the coordinates inside the feature's geometry object. Property members are descriptive data and have no predefined geographic meaning, even when they are named latitude, longitude, lat, or lon. To plot such tabular fields, they must first be represented as coordinates in a valid GeoJSON geometry.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.