chiming in late due to vacations. The idea is sound and needed. I'm wondering if there's any conceptual difference between your EPSG:0 CRS and the CRS:1 special CRS defined in the WMS 1.3 spec (see section 6.7.2 and 6.7.3.5). If there's not we should use CRS:1, but I think there is a difference in that CRS:1 forcedly has a 0,0 coordinate origin and yours is tied to the layer bounds as declared by the datastore?
In any case, CRS:1 seems worth to support at some point. excerpt: "6.7.3.5 Geographic information with undefined CRS A server may offer two-dimensional geographic information whose precise spatial reference is undefined. For example, a hand-drawn historical map may represent an area of the Earth but not employ a modern coordinate reference system, and an aerial photograph may not be precisely georeferenced. Such types of graphical information shall be treated as an image, and the Map CS label “CRS:1” shall be used when declaring the Layer CRS of such an object. Clients should not attempt to overlay a layer for which CRS=CRS:1 with another layer." Cheers, Gabriel On Mon, 2011-01-10 at 12:47 +0100, Andrea Aime wrote: > On Sun, Jan 9, 2011 at 7:31 PM, Chris Holmes <cho...@gmail.com> wrote: > > I like the idea. The use case that strikes me as quite nice is someone > > having no idea what the epsg is, but just wanting to look at it in the layer > > preview. 0 seems like a nice way to represent that. And a nice way to get > > it in to our system where maybe they could figure out the epsg. With this > > there you could put in EPSG:0 and then use our force CRS to basically > > declare what the CRS should be after the fact, no? So you wouldn't have to > > do your guessing before, you could just try various forces and seeing if > > they overlay right. > > > > As for confusing clients - are thinking of advertising EPSG:0 in the > > capabilities document? I suppose we could consider not putting EPSG:0 > > layers in the caps documents, but exposing them in the layer previews and > > rest pages and let people make non-capabilities requests against them. Once > > someone declares a forceCRS it would then appear. > > I actually wanted to publish it in the capabilities. The reasoning is that > it's > no different from any other custom code. > 900913 is well known about open > source apps, but commercial apps do not know anything about it, yet we > commonly publish through it. > If you have a custom srs it's the same, you come up with a fancy code and > publish it. > > So I think we should treat 0 just the same, it's our easy to remember custom > code, some client will have troubles dealing with it, yet if you're using it, > it means you don't have a meaningful epsg code to use anyways. > > Cheers > Andrea > -- Gabriel Roldan grol...@opengeo.org Expert service straight from the developers ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
