Some of our users can’t send requests to our server directly, they are required to send their requests through a gateway (run by a the central state IT agency called ITD) that validates them. Currently the .xsd from http://schemas.opengis.net/ are used. However, there are extra bits that GeoServer supports, such as srsName attribute on wfs:Query element. I’ve just modified the .xsd to add this attribute, but I wonder if there are other additions these users might want to take advantage of in the future. Are there XSD documents available that have the GeoServer additions that we should be using instead (so I don’t have to modify the standard ones bit by bit?). This is a followup to http://www.nabble.com/WFS-schema-validation-and-srsName-td17553617.html 
Aleda
Hi Aleda,
Unfortunately there is not formal XSD around but per Andrea's suggestion we could provide a modified schema. I guess first we need a list of all the additional parameters we support. srsName on Query is definitely one of them.
Can anyone think of any others?
-Justin
Freeman, Aleda (EEA) wrote:
Some of our users can't send requests to our server directly, they are required to send their requests through a gateway (run by a the central state IT agency called ITD) that validates them. Currently the .xsd from _http://schemas.opengis.net/_ are used. However, there are extra bits that GeoServer supports, such as srsName attribute on wfs:Query element. I've just modified the .xsd to add this attribute, but I wonder if there are other additions these users might want to take advantage of in the future. Are there XSD documents available that have the GeoServer additions that we should be using instead (so I don't have to modify the standard ones bit by bit?). This is a followup to _http://www.nabble.com/WFS-schema-validation-and-srsName-td17553617.html_
Aleda/
/
------------------------------------------------------------------------
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
That's what I was wondering... if the user would run into something else
they wanted, then something else... but I don't know how many
differences there are. 10? 50? I <am> aware of a few vendor-specific
SLD options (such as road shield labeling). But those could be created
as named styles for them to use.
Justin Deoliveira ha scritto:
Hi Aleda,
Unfortunately there is not formal XSD around but per Andrea's suggestion we could provide a modified schema. I guess first we need a list of all the additional parameters we support. srsName on Query is definitely one of them.
Can anyone think of any others?
Do we have anything for paging support, or is that a GET request extra
param only?
And I know we have some custom params in SLD... it would be used
in a WMS post request, which is not that common.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
On Fri, Jan 9, 2009 at 4:12 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi Aleda,
Unfortunately there is not formal XSD around but per Andrea's suggestion
we could provide a modified schema. I guess first we need a list of all
the additional parameters we support. srsName on Query is definitely one
of them.
srsName on Query is part of the WFS 1.1 spec. From the spec: "The
optional srsName attribute of the <Query> element is used to specify a
specific
WFS-supported SRS to be used for returned feature geometries."
So if just this one is what is causing problems for Aleda's users, I'd
suggest checking if the Query references the correct version of the
WFS schema.
Regards,
Andreas.
--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
Andreas Hocevar ha scritto:
On Fri, Jan 9, 2009 at 4:12 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi Aleda,
Unfortunately there is not formal XSD around but per Andrea's suggestion
we could provide a modified schema. I guess first we need a list of all
the additional parameters we support. srsName on Query is definitely one
of them.
srsName on Query is part of the WFS 1.1 spec. From the spec: "The
optional srsName attribute of the <Query> element is used to specify a
specific
WFS-supported SRS to be used for returned feature geometries."
So if just this one is what is causing problems for Aleda's users, I'd
suggest checking if the Query references the correct version of the
WFS schema.
Well, we actually support srsName in WFS 1.0 xml requests as well.
The reason is simple, reprojection is a very common need, and
WFS 1.1/GML 3 are not properly supported by the vast majority
of software, whilst GML2 is.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.