>> With such a parameter, a sheer number of already defined CRS becomes
>> available for the use in the geo: URIs.
[...]
> Another issue that bothers me is that the sheer number of defined
> CRSes would almost make it impossible to support all those CRSes -
> which would probably hurt interopability.
First of all, there's PROJ.4 [1], readily supporting more than
approximately...
$ grep -vE ^\# /usr/share/proj/epsg | wc -l
3519
$
... coordinate systems.
Also, I'm in doubt that most of the parties handling the geo:
URIs are ought to have some ``specific'' support for the
particular CRSes. To my mind, most of the ``simple'' software
(when it comes to the geography knowledge; should I call such
software ``geosimple''?) would simply pass the geo: URIs to the
other parties, without any need to ever interpret it.
And the complex software (such as GRASS, MapServer, and,
perhaps, Google Maps) is expected to support this sheer number
of coordinate systems anyway.
[...]
[1] http://trac.osgeo.org/proj/
--
FSF associate member #7257
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
