You can read the WFS spec here:
https://portal.opengeospatial.org/files/?artifact_id=7176
It pretty much defines everything.
There is a separate Filter spec here:
http://portal.opengeospatial.org/files/?artifact_id=1171
The top of page 72 you'll see it talk about the namespace issues:
In order to not obfuscate the essential information, however, the
namespace and schema location attribute tags have been omitted from the
examples in this section. In addition, the schema locations shown are
only example locations and the correct schema locations would need to
be substituted.
It also defines how to all the operations
(GetFeature,GetFeatureWithLock,Transaction) etc... with both XML POST
and with GET symantics.
There isnt really any other way of doing Filters except through
filter=...xml....
You can, however, also do a simple BBOX filter another way:
http://www.someserver.com/wfs.cgi?
SERVICE=WFS&
VERSION=1.0.0&
REQUEST=Transaction&
OPERATION=Delete&
TYPENAME=INWATER_1M,BUILTUPA_1M&
BBOX=10,10,20,20
There's not too much in the document about it - see page 74.
I am making so many questions because we are developing a quite
similar protocol to WFS and we have to deal with same issues...
Why not just use the WFS protocol -- its a standard so hopefully other
applications will be able to automagically communicate with your
application.
dave
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/