OGCJSON aims to get your axis in order

So this happened:

Make sure you click on that link to read something quite interesting. Howard Butler’s response is well thought out that I’ll just let him frame the situation. I myself am curious if there is really any need to fork GeoJSON into “OGCJSON” to solve something I’m not sure really is any issue. As others have said on Twitter, GML was designed to handle just these issues. I don’t want to get down the rabbit hole of being critical of OGC, but what’s the point of creating these standards (KML, GML, etc) and then not use them?

Why does this come to mind every time I heard the OGC thinking about creating a new “standard”?

Car Wash

Leave a Reply