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:

NO result:
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/vnd.ogc.gml&I=488&J=574&FEATURE_COUNT=10

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

Note: from original capabilities:
<Format>application/json</Format>
<Format>application/json; subtype=geojson</Format>
<Format>application/vnd.ogc.gml</Format>
<Format>text/html</Format>
<Format>text/plain</Format>
<Format>text/xml</Format>
<Format>text/xml; subtype=gml/3.1.1</Format>

Anybody a hint if this should or should not be possible? OR if I miss some 
setting?

I think cascading WMS/WMTS becomes more and more needed, because Browsers (AND 
Firewalls) getting more and more strict/picky about 
CORS/Access-Control-Allow-Headers settings etc etc. As an example the 
(municipality) firewall here eats almost all Headers from requests/responses if 
not configured in the firewall, so it's getting harder and harder to use layers 
from external services...

Thanks for any pointers.

Regards,

Richard Duivenvoorde


_______________________________________________
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

Reply via email to