Some issues have been reported with GetFeaturById finding features, in
particular with app-schema layers (see
http://osgeo-org.1560.x6.nabble.com/urn-ogc-def-query-OGC-WFS-GetFeatureById-td5402041.html
and
https://gis.stackexchange.com/questions/342744/geoserver-getfeaturebyid-stored-query-not-working
It turns out that the Storedquery GetFeatureById is implemented in such
a way that it assumes that ID’s are always of the form “layername.id
<http://layername.id>”. But this is only a convention, for which each
datastore’s own implementation is responsible. In App-schema, this
convention is not automatically followed (but can be, if so specified in
the mapping file). I don’t really see another way of implementing this
feature though: it would have unacceptable performance to search in all
layers (particularly if you have 100s or 1000s of them).
But perhaps it should at least be documented somewhere that this
convention is assumed for the storedquery to work, and that app-schema
users (or other stores that do not follow the convention automatically)
should be aware of that?
Kind Regards
Niels
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
