[Geojson] State of the GeoJSON

[Raj Singh]

I'm a little confused by the wording here. Let me try a rewrite, with  
the additional information that there are *no* EPSG codes that do  
decimal degrees in lon, lat order:
   * Don't use EPSG codes if your data is in decimal degrees.
   * Support OGC URNs, e.g.
     {"type":"OGC",{"urn":"urn:ogc:def:crs:OGC:1.3:CRS84"}}
     for decimal degrees: lon, lat
   * EPSG:4326 in lon, lat order is called urn:ogc:def:crs:OGC:1.3:CRS84
   * If you can find an EPSG code that fits your data, you should prefer
     EPSG codes over OGC URNs.
   * If you can't find an EPSG or OGC code that fits your data,
      you should define a spatial reference URL. If you can't do that,
      you should not include an SRS at all.

---
Raj


On Sep 27, 2007, at 2:35 AM, Christopher Schmidt wrote:

>   * Support OGC URNs,
>     {"type":"OGC",{"urn":"urn:ogc:def:crs:OGC:1.3:CRS84"}}
>   * "Don't use EPSG:4326 or other CRSes in lat, lon order." If you  
> have data
>      in a projection which is defined to be in lat, lon order, you
>      should either find another EPSG or OGC code to use. If you can't,
>      you should define a spatial reference URL. If you can't do that,
>      you should not include an SRS at all.
>   * If your EPSG code doesn't use lat, lon order, you should prefer
>     EPSG codes over OGC URNs.
>   * EPSG:4326 in lon, lat order is called urn:ogc:def:crs:OGC: 
> 1.3:CRS84