Sean Gillies http://sgillies.net
This work is licensed under the Creative Commons Attribution 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.
GeoJSON is not just wrong, it is spectacularly , 45-helium-weather-balloons-and-a-lawn-chair wrong. It invites coordinate order confusion. There is no language for defining schemata. It doesn't conform to ISO 191**. It is not even a real standard! And yet somehow people seem to find it good enough for everyday use, applying it to solve real problems without suffering major catastrophes. How can this be? How can something so wrong feel so right to developers?
GeoJSON is a success because it has low technical and social barriers to entry and because it is incomplete and imperfect. I will discuss these properties and their happy consequences along with the overall strengths and weaknesses of the format, and offer some new patterns for using the format.
data, json, schema, schemaless, semantics, design, patterns, agreement, standards, web, irony, right, wrong, english, esperanto, bad, metaphors