Justin Deoliveira ha scritto: > Good idea, I believe at the moment all we do is set the "DefaultSRS", > which i think is just hardcoded to EPSG:4326. It would be nice to > provide the filtered list as "OtherSRS" elements.
Quick check on geo: http://geo.openplans.org:8080/geoserver/wfs?service=WFS&request=GetCapabilities http://geo.openplans.org:8080/geoserver/wfs?service=WFS&request=GetCapabilities&version=1.0.0 Same layer, archsites, declares: WFS 1.0: <SRS>EPSG:26713</SRS> WFS 1.1: <DefaultSRS>urn:x-ogc:def:crs:EPSG:6.11.2:26713</DefaultSRS> Looking at the schema, WFS 1.0 does not have a place to declare extra SRS, you can declare the BBOX in multiple SRS, but I guess it's not the same (plus, bbox reprojection could cause transformation failures... maybe it's better to stay away?) WFS 1.1 has indeed the OtherSRS element that could be used to declare the extra SRS. Pros: the client knows that we're capable of reprojecting the layer in other srs Cons: - we have to move the srs list up to GeoServer config - the srs list may be short or long. If long and we have many many layers (say, hundreds?) boom, the cap doc becomes quite long. E.g., picture this baby: http://giswebservices.massgis.state.ma.us/geoserver/wfs?request=GetCapabilities with 10 extra rows for each feature type (it's true that we already have quite a bit of rows for the output formats). Opinions? Cheers Andrea ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
