Hi,
since I keep on getting trapped by silly constructions
errors in the XML requests I make by hand I've enabled
schema validation in most of my configs in order to
get good error messages and see what's really wrong in
the XML I'm writing.
This has the side effect that reprojecting GetFeature
WFS 1.0 requests, like:
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs" service="WFS" version="1.0.0" outputFormat="GML2" xmlns:topp="http://www.openplans.org/topp" xmlns:ogc="http://www.opengis.net/ogc">
<wfs:Query xmlns:wfs="http://www.opengis.net/wfs" typeName="topp:archsites" srsName="EPSG:900913">
<ogc:Filter xmlns:ogc="http://www.opengis.net/ogc">
<ogc:BBOX>
<ogc:PropertyName>the_geom</ogc:PropertyName>
<gml:Box xmlns:gml="http://www.opengis.net/gml">
<gml:coordinates decimal="." cs="," ts=" ">
-20037508.34,-20037508.34 20037508.34,20037508.34
</gml:coordinates>
</gml:Box>
</ogc:BBOX>
</ogc:Filter>
</wfs:Query>
</wfs:GetFeature>
do not pass validation anymore. This is formally correct,
WFS 1.0 does not support reprojection, but in fact we
do support it anyways.
I'm wondering, shall we
include in GeoServer /schemas directory and in the wfs
module classpath an amended version of the WFS 1.0
schema that includes the srsName attribute?
Cheers
Andrea
It sounds like a good idea. However once we start modifying the schema we start walking a fine line... I guess it would only affect people that validate geoserver output... i am curious to hear if any users have an insight on this.
Andrea Aime wrote:
Hi,
since I keep on getting trapped by silly constructions
errors in the XML requests I make by hand I've enabled
schema validation in most of my configs in order to
get good error messages and see what's really wrong in
the XML I'm writing.
This has the side effect that reprojecting GetFeature
WFS 1.0 requests, like:
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs" service="WFS" version="1.0.0" outputFormat="GML2" xmlns:topp="http://www.openplans.org/topp" xmlns:ogc="http://www.opengis.net/ogc">
<wfs:Query xmlns:wfs="http://www.opengis.net/wfs" typeName="topp:archsites" srsName="EPSG:900913">
<ogc:Filter xmlns:ogc="http://www.opengis.net/ogc">
<ogc:BBOX>
<ogc:PropertyName>the_geom</ogc:PropertyName>
<gml:Box xmlns:gml="http://www.opengis.net/gml">
<gml:coordinates decimal="." cs="," ts=" ">
-20037508.34,-20037508.34 20037508.34,20037508.34
</gml:coordinates>
</gml:Box>
</ogc:BBOX>
</ogc:Filter>
</wfs:Query>
</wfs:GetFeature>
do not pass validation anymore. This is formally correct,
WFS 1.0 does not support reprojection, but in fact we
do support it anyways.
I'm wondering, shall we
include in GeoServer /schemas directory and in the wfs
module classpath an amended version of the WFS 1.0
schema that includes the srsName attribute?
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4007,483fb4cb256301804284693!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
Justin Deoliveira wrote:
It sounds like a good idea. However once we start modifying the schema we start walking a fine line... I guess it would only affect people that validate geoserver output... i am curious to hear if any users have an insight on this.
That may trip up our parser; depends on how it is done. You can always run GeoServerOnlineTest to verify...
Jody