On Thu, Apr 8, 2021 at 2:58 PM Richard Duivenvoorde <rdmaili...@duif.net> wrote:
> Hi All, > > I'm trying to cascade the following public/open service: > > https://service.pdok.nl/bzk/brocptkenset/wms/v1_0?request=getcapabilities > it has one layer: 'cpt_kenset' (epsg:28992) being borehole-information. > > After setting up as a cascading store/layer I can just get a WMS map fine. > > But trying to retrieve getfeatureinfo, I receive an empty > FeatureCollection?? > > The url from my local (2.19) test server (from geotools develment log) > returns in an empty resultset: > > > http://localhost/geoserver/ows?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetFeatureInfo&BBOX=136329.07250007192487828,448242.24533979734405875,136573.94125728702056222,448591.21790481149218976&CRS=EPSG:28992&WIDTH=708&HEIGHT=1009&LAYERS=cite:cpt_kenset&STYLES=&FORMAT=image/png&QUERY_LAYERS=cite:cpt_kenset&INFO_FORMAT=application/json&I=488&J=574&FEATURE_COUNT=10 > > Taking this url, but changing the host/url part AND the layername (to > remove the cite-namespace): > > > https://service.pdok.nl/bzk/brocptkenset/wms/v1_0?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetFeatureInfo&BBOX=136329.07250007192487828,448242.24533979734405875,136573.94125728702056222,448591.21790481149218976&CRS=EPSG:28992&WIDTH=708&HEIGHT=1009&LAYERS=cpt_kenset&STYLES=&FORMAT=image/png&QUERY_LAYERS=cpt_kenset&INFO_FORMAT=application/json&I=488&J=574&FEATURE_COUNT=10 > > you get a fine result. > > Testing with 'application/vnd.ogc.gml' instead of 'application/json' > (because I googled something around that), is also fine: > GeoServer can cascade feature info only if the remote server can produce a GML feature collection as the output: > OK result: > > https://service.pdok.nl/bzk/brocptkenset/wms/v1_0?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetFeatureInfo&BBOX=136329.07250007192487828,448242.24533979734405875,136573.94125728702056222,448591.21790481149218976&CRS=EPSG:28992&WIDTH=708&HEIGHT=1009&LAYERS=cpt_kenset&STYLES=&FORMAT=image/png&QUERY_LAYERS=cpt_kenset&INFO_FORMAT=application/vnd.ogc.gml&I=488&J=574&FEATURE_COUNT=10 > > "Not ok" result, it's starting with a tag named "msGMLOutput". That's not a GML feature collection, just something that looks somehow similar to it. We'd need to build a GML parser that's not "schema driven" to parse that thing (being schema driven means, it follows the structure expected by the GML during a parse, failing to find it, it returns nothing or throws an error)... or build a specific one for that output. A possibly better alternative would be adding support for GeoJSON output in cascading a FeatureInfo. In anyone is interested in contributing a change, believe it should happen around here: https://github.com/geoserver/geoserver/blob/b05e92aa12fb0bf7568d28908d88d67d759919ac/src/wms/src/main/java/org/geoserver/wms/featureinfo/WMSLayerIdentifier.java#L82-L81 Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users