Hi Albrecht,
Albrecht.Weiser@anonymised.com wrote:
Hi list,
i'm currently testing mapbender as wfs-t client. When trying to set a new point-feature (digitize) in mapbender, i get the following error: "fatal error: EPSG mismatch EPSG:4326 / EPSG:31467". The mapbender list statet out, that this is a problem of the SRS definitions in the capabilities. Mapbender retrieves some initial informations to build a gui from the capabilities-doc served by the wfs (wms). In the caps coming from geoserver are following definitions:
<Layer>
<Title>HMULV Geoserver WMS</Title>
<Abstract>This is a description of your Web Map Server. </Abstract>
<!--All supported EPSG projections:-->
<SRS>EPSG:2000</SRS>
...
<SRS>EPSG:42304</SRS>
<SRS>EPSG:42303</SRS>
<LatLonBoundingBox minx="7.730792251272924" miny="49.389425754740856" maxx="10.251024832358658" maxy="51.66073535342488"/>
<Layer queryable="1">
<Name>ora:FFH_SDO</Name>
Mapbender gets the reference-information from the top Layer. Here is only a LatLonBoundingBox-definition which is by default WGS84 (epsg:4326). If no additiional BoundingBox-element is defined, mapbender takes epsg:4326 as default for the gui. But the layers beyond the top-layer are defined as epsg:31467. Therefore the mapbender epsg mismatch.
GeoServer behavior is to only set the bounds on the top or root layer in EPSG:4326, and then the individual bounds for each layer in both 4326, and in the SRS set on the layer/feature type (through the admin UI).
So i guess what you want is another bounding box on the root layer, which is the SRS of all its child layers? Currently GeoServer wont do this.
Now i was looking, how can i add the BoundingBox information to the capabilities, but i didn't find a way. The only place to do it in the admin-gui of geoserver could be configuration/data/FeatureTypes But there i can do only the settings for the layers itself. Is the only way to add the information to edit the capabilities manually? If yes ist there a place, where the capabilities.xml are stored to from mapserver or is it built on the fly for every request?
The capabilities document is generated on the fly every time. One thing you can do is load the caps document (in your browser say), and save it out somewhere so that it is web accessible to some client. You can then modify the file with anything you want, as long as its on the same server or a server which can see that server, all the links from the capabilities to individual operations should work fine. Does that make sense? The downside of this is of course that if the layers change it is not reflected in the capabilities document.
Another question: can i supress the output of all available srs in the capabilities?
Yes, although I believe this feature is only available in the last 1.6.x release. In the configuration ui you can from from the main page to Config->WMS->Contents and specify the Limited SRS list there.
Best wishes
Hope that helps, let us know if anything is still unclear.
-Justin
Albrecht
!DSPAM:4007,4889b6dd256153362379201!
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
!DSPAM:4007,4889b6dd256153362379201!
------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
!DSPAM:4007,4889b6dd256153362379201!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com