May 8, 2026

Map nerds found their main character

GeoJSON

The map-data format everyone loves—until it starts lying about where things are

TLDR: GeoJSON is a standard way to describe places and shapes on maps, and commenters say it quietly makes everything from delivery zones to custom map apps much easier. The only drama: fans love its simplicity, but some warn it can cause serious mistakes when software assumes you’re mapping the whole Earth instead of a local space.

A dry little data format somehow sparked the kind of comment-section energy normally reserved for app redesigns and price hikes. GeoJSON—a simple way to write down places, lines, and shapes on a map—got the spotlight, and the crowd reaction was basically: boring name, huge impact. The biggest mood? People were almost suspiciously enthusiastic. One commenter said it’s so common and easy to read that it saved them a ton of work building a map project, which is the geek equivalent of writing a love letter.

But the real fun started when users rolled in with receipts from the real world. A delivery-tech worker praised GeoJSON for helping draw shipping zones and calculate prices without the usual headache, while others casually name-dropped tools like Vega-Lite and PostGIS like proud parents at a school play. The vibe was clear: this format may be old enough to have an official internet rulebook since 2016, but it’s still quietly running a shocking amount of modern map stuff.

Then came the plot twist. One warehouse-robot mapper warned that GeoJSON is great "as long as you squint just a bit"—because some software assumes you’re mapping the actual Earth, not a flat indoor space, and can totally mangle the math. So yes, the community mostly agrees GeoJSON is a lifesaver. But the hottest take is also the spiciest warning: this beloved map format is amazing right up until it confidently sends your robots, rates, or regions into geometric chaos.

Key Points

  • GeoJSON is a format for encoding geographic data structures.
  • The format supports Point, LineString, Polygon, MultiPoint, MultiLineString, and MultiPolygon geometry types.
  • GeoJSON uses Feature objects for geometries with additional properties and FeatureCollection objects for sets of features.
  • A GeoJSON example in the article shows a Feature containing a Point geometry and a name property for Dinagat Islands.
  • The IETF formed a GeoJSON Working Group in 2015, and RFC 7946 was published in August 2016 as the standard specification replacing the 2008 version.

Hottest takes

"the format itself is great" — sam_lowry_
"persistently annoying thing to do until we discovered this format" — jackconsidine
"works great as long as you squint just a bit" — Waterluvian
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.