[...]
>> So there definitely needs to be documentation for how each CRS to be
>> used in the geo URI is to be mapped (note that there are many many
>> CRSes that don't use the longitude/latitude scheme, for a start -
>> also many CRSes have completely different definitions of the third
>> dimension).
>> So, just adding the CRS to the URI parameter is not good enough for
>> a full definition - which means that we need a document for new
>> CRSes anyway.
[...]
>> BTW, i have tried to locate that URN registry - could you provide me
>> with a pointer?
> If this helps at all: The official EPSG CRS registry is here
> http://www.epsg-registry.org/
Thanks for the link! (Looks like I should look for something
speaking JavaScript to work with the resource, though.)
> and the OGC urn resolver (beta) is here: http://urn.opengis.net/
> Please note that the OGC urn registry against which the resolver
> works has not been fully.
Apparently, I've stumbled upon this one earlier, but haven't
figured out how to make any use of it. Could you provide any
examples (with respect to the URN-mapped CRS definitions)?
> Should be in the next few months. There are also seveal OGC standards
> documents that specify the rules for the "def" branch of the OGC urn
> - including type "crs".
> Alexandre is correct - there are thousands of CRS's. Relatively few
> specify latitude/longitude.
Is this a problem for a modern ``geospatially-enabled''
application? (I've got a feeling like I'm missing something
both trivial and widely known...)
--
FSF associate member #7257
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
