[Geojson] [OSGeo-Standards] EPSG + Coordinate Ordering (Was Re: GeoJSON '1.0'?)

Christopher Schmidt crschmidt at metacarta.com
Thu Mar 13 14:59:26 PDT 2008

On Thu, Mar 13, 2008 at 02:55:07PM -0700, Paul Ramsey wrote:
> I'm with Frank: say what you mean, and mean what you say.
> EPSG:4326 has a particular meaning, but as long as you explicitly
> over-ride that meaning in your document, at least you are saying what
> *you* mean by EPSG:4326.  The WMS 1.1.0 specification did exactly
> this.
> You should, as Frank suggests, go one step further and say that, "for
> all geographic coordinate systems, we expect lon/lat, but that for
> projected systems, we'll go with the explicit definition in the
> database".
> Because this was botched (depending on your perspective, by WMS 1.0 or
> by WMS 1.3) the meaning of EPSG:4326 when applied to web services is
> somewhat in dispute, so just be clear about what you want in the
> specification document.  Don't allow optional flags to flip the
> behavior around at run-time.

That was not the plan for GeoJSON. The additional flag would not change
the data in any way, all it would do would be to accept, and describe,
the mapping from EPSG:4326 to the way GeoJSON works. The spec was (is)
very clear that the coordinate order is *always* x, y, z.

Christopher Schmidt

More information about the GeoJSON mailing list