gml_uri directive missing in docu

[tomkralidis]

Don't ask me how I got there, but I notice that in mapwfs.c (line 481, 761),
there is a "gml_uri" setting which allows one to specify their own namespace for
their WFS responses.  If it is not set, an arbitrary one is set.

This is a valuable thing to have, and not specified in the documentation, but it
should be.

i.e. in the web metadata object:

"gml_uri" "http://www.ec.gc.ca/cise"

[dmorissette]

Reassigned to Jeff.  This gml_uri should be added to the WFS-server docs. You
can talk to Assefa if you need clarifications.

[jmckenna@…]

in fact i also see "wfs_namespace_uri" and "wfs_namespace_prefix" ... I'll ask
assefa

[assefa]

wfs_namespace_uri" and "wfs_namespace_prefix are the proper names to use to add
a user name space in the response. gml_uri was a test I was doing and made it in
the  code by error. Tom do you see any problem if I remove it ?
wfs_namespace_xxx should normally do the trick too.

 As for the doc :

 wfs_namespace_prefix and wfs_namespace_uri are map level metadata used to give
the user the possiblity to add a user defined name space and uri that will be
used in the response of a WFS GetFeature request.  

[tomkralidis]

gml_uri is relatively uncharted waters (I think).  So, we should remove it from
the code and go with (and document) wfs_namespace_uri and wfs_namespace_prefix.

One question, though: should wfs_namespace_uri and wfs_namespace_prefix be
declared at the WEB/METADATA level, or foreach layer (i.e. LAYER/METADATA)
level?  The reason is that a user may want to specify different namespaces
(prefix and uri) at the layer level.

Comments?

[assefa]

Tom,

 The user defined name space are usually used in the <wfs:FeatureCollection ...
The feature collection can include elements from more than one layer. 
 What is possible is to add the all name spaces defined in each layer when
returning the results. If the layer does not have these metadatas and the
metadata is defined in the web object, we will use this last one. Note sure how
useful this is but if is something usuful from user points of vue, I will do the
changes.

 

[tomkralidis]

We can leave as is, and just delete gml_uri

[dmorissette]

What's the next action on this bug?

Are "wfs_namespace_uri" and "wfs_namespace_prefix" already properly documented?
 If they are then I assume this means that the action for this bug is to remove
the gml_uri from the code?

[jmckenna@…]

i will document the 2 new metadata now.

[assefa]

Fixed in the code in both cvs branches.

[jmckenna@…]

huge wrist-slap for me..seems i never got around to doing this one.  
I added the 2 metadata to wfs-server-howto...Tom if you can verify this, and
feel free to suggest that i change the wording (or provide an example for each).
 thanks.

(the live doc will get updated overnight)

[tomkralidis]

Note that gml_uri should be deleted, as it is not supported anymore.  We should
be supporting and documenting:

"wfs_namespace_uri" "http://somehost/someurl"
"wfs_namespace_prefix" "someprefix"

[jmckenna@…]

um...maybe i missed something...gml_uri is not mentioned in the docs....are you
referring to mapwfs.c?

i will add the examples to the doc that you provided.

[tomkralidis]

Ah, ok.  I see that Assefa stated this in comment 3 in this bug.  So yeah,
forget about gml_uri completely.

[jmckenna@…]

examples have been added to the 4.4 doc.