From: Jody G. <jga...@re...> - 2004-05-05 20:53:21
|
Martin Desruisseaux wrote: > Paul Ramsey a =E9crit : > >> Auto projections are just another way of encoding a projection, like=20 >> an EPSG code or a WKT. The reason they are called "auto" is because=20 >> they can allow WMS servers to create projections "on the fly" instead=20 >> of referencing an existing EPSG definition. >> So, "AUTO:42001,9001,-71.69,45.75" provides all the information you=20 >> need to construct a particular UTM projection, just as "EPSG:26910"=20 >> does. The implementation would be another Factory, like the EPSGFactor= y. > > Ah? Sorry for my misunderstanding. Then yes you are right, it would be=20 > an other CRSAuthorityFactory. I was thinking of either of the following: - Having AutoFactory delegate to the EPSGFactory (once it has determined=20 what what code is required) or; - if not I can simply do the WKT search and replace as suggested in the=20 specification. The specification also links to:" OpenGIS Consortium, Automatic=20 Projections for Web Mapping" http://www.digitalearth.gov/wmt/auto.html>.=20 This apparently contains a list of "informal" mappings developed by the=20 community that have not yet been standardized. Of course that url timed out on me (the web is such a good archival mediu= m) Jody |