A GeoJSON Feature JSON example following RFC 7946 — includes geometry (Point), coordinates, and properties. Copy-ready for maps, Leaflet, Mapbox, and geospatial APIs.
→Rendering markers and shapes on Leaflet, Mapbox, or Google Maps
→Exchanging geospatial data between mapping APIs and databases (PostGIS)
→Storing points of interest with coordinates and attributes
geojsonmapsgeospatialcoordinatesleafletmapbox
Validate or format this JSON
One click loads this exact example into the tool — no copy-paste needed. Format it, validate it, explore the tree, or generate TypeScript types instantly.
GeoJSON (RFC 7946) mandates [longitude, latitude] order to match the x, y convention. This trips many people up because mapping libraries like Leaflet use [lat, lng] in their APIs. Always double-check the order when converting between formats.
A Geometry is just the shape (type + coordinates). A Feature wraps a geometry with 'properties' (attributes like name or category) and an optional id. A FeatureCollection holds many Features. Most apps work with Features so they can attach metadata.
Yes. For Polygon and MultiPolygon, each linear ring must start and end with the same coordinate pair. Many tools tolerate unclosed rings, but per the spec they should be explicitly closed.