Hi, I don't remember last time I used WFS 1.0.0, with a first quick look I noticed that there is an extra comma in the bbox coordinates: <ogc:BBOX> <ogc:PropertyName>geometry</ogc:PropertyName> <gml:Box xmlns:gml="http://www.opengis.net/gml"; srsName="urn:x- ogc:def:crs:EPSG:102113"> <gml:coordinates>-13632748.557201,4455827.325574---HERE--->,-135119 78.052511,4513995.904099</gml:coordinates> </gml:Box> </ogc:BBOX> ... should be (unless is some WFS 1.0.0 specific thing): <ogc:BBOX> <ogc:PropertyName>geometry</ogc:PropertyName> <gml:Box xmlns:gml="http://www.opengis.net/gml"; srsName="urn:x- ogc:def:crs:EPSG:102113"> <gml:coordinates>-13632748.557201,4455827.325574 -13511978.052511,4513995.904099</gml:coordinates> </gml:Box> </ogc:BBOX> That say, to be sure of what's going on, I suggest that you select GEOT OOLS_DEVELOPER_LOGGING [1] log profile and check the query that's actually produced by GeoServer. Hope it helps, Nuno Oliveira [1] https://docs.geoserver.org/latest/en/user/configuration/globalsetti ngs.html#logging-profile On Wed, 2019-10-09 at 19:25 -0700, Deirdre H wrote: > Hi, folks ... > > I have an situation where I need a WMS query and a WFS query to match > each other, with both the right bbox and filter (the WFS query needs > to return the same set of features as is displayed on the tile). The > WMS query works just fine with the bbox and filter. > > As I learned, a WFS request cannot have both a bbox and filter, the > bbox must be integrated into the filter. So I came up with two > different filters. > > WMS request parameters (from developer console): > > LAYERS: xxx > STYLES: xxx > FORMAT: image/png > SERVICE: WMS > REQUEST: GetMap > VERSION: 1.1.1 > TRANSPARENT: TRUE > FILTER: > properties.status > Terminated > > properties.actual.startTime > yyyy-MM- > dd'T'HH:mm:ssXXX 2019-10-01T09:00:00- > 07:00 > > properties.actual.endTime > yyyy-MM- > dd'T'HH:mm:ssXXX 2019-10-01T08:00:00- > 07:00 > > BBOX: -13632748.557201,4455827.3255735,- > 13511978.052511,4513995.9040985 > SRS: EPSG:102113 > WIDTH: 1580 > HEIGHT: 761 > > WFS request parameters: > > service: WFS > version: 1.0.0 > request: GetFeature > typeName: xxx > FILTER: > properties.status > Terminated > geometry > xmlns:gml="http://www.opengis.net/gml"; srsName="urn:x- > ogc:def:crs:EPSG:102113">- > 13632748.557201,4455827.325574,- > 13511978.052511,4513995.904099 > > properties.actual.startTime > yyyy-MM- > dd'T'HH:mm:ssXXX 2019-10-01T09:00:00- > 07:00 > > properties.actual.endTime > yyyy-MM- > dd'T'HH:mm:ssXXX 2019-10-01T08:00:00- > 07:00 > > outputFormat: application/json > > I have moved that BBOX declaration around in the wfs filter and > exactly the same thing continues to happen. It seems to completely > ignore the status filter and date range filter and dump the thousands > of records from the database out to the browser. > > If I remove the BBOX from the WFS filter, the WFS request matches the > WMS request except for the boundary box limitations (the status and > date range are handled correctly). > > What am I doing wrong here? > Thanks. > > > _______________________________________________ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting > to this list: > - Earning your support instead of buying it, but Ian Turton: http://w > ww.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: http://geoserver.org/co > mm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: ht > tps://github.com/geoserver/geoserver/wiki/Successfully-requesting- > and-integrating-new-features-and-improvements-in-GeoServer > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Regards, Nuno Oliveira == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. ==
Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
