Ben, Thanks for the clarification.
Best regards, Wen -----Original Message----- From: Ben Caradoc-Davies [mailto:[email protected]] Sent: Thursday, September 24, 2015 4:57 PM To: Yin, Wentao (IS) (Contr); [email protected] Subject: EXT :Re: [Geoserver-users] BBOX questions Wen, I think that you are correct and that for KVP style bbox to work you may need to include the geometry in the top level feature. The underlying conceptual problem is that, for complex features, nested geometries may belong to features only weakly related to the containing feature, such as the geometry of neighbouring features or the location of a remote observer. There is no general rule for when a nested geometry might be appropriate for a kvp bbox request. Kind regards, Ben. On 25/09/15 08:34, Yin, Wentao (IS) (Contr) wrote: > Some questions about BBOX filter: > > In app-schema tutorial, MappedFeatrue is nested in GeologicUnit. If I want to > use KVP bbox query, it will fail. > > http://localhost:8081/geoserver/wfs?request=GetFeature&version=1.1.0&t > ypeName=gsml:GeologicUnit&BBOX=120,-39,150,-33 > > But it works when using XML which specifies the path to the nested geometry. > > Does this mean we have to include the geometry in the top level feature in > order for KVP style bbox to work? > > Thanks, > Wen > > ---------------------------------------------------------------------- > -------- _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
