Open gannebamm opened 2 months ago
Sprint Review:
v4.3.x
Response of stable.demo is the same as of thuenen_atlas:
<?xml
version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ows="http://www.opengis.net/ows" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.0.0" xsi:schemaLocation="http://www.opengis.net/ows http://172.18.0.1/geoserver/schemas/ows/1.0.0/owsExceptionReport.xsd">
<ows:Exception exceptionCode="InvalidParameterValue" locator="service">
<ows:ExceptionText>No service: ( ows )</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>
@gannebamm it seems the WMS parameters got removed by geosolutions by intent: https://github.com/GeoNode/geonode-mapstore-client/issues/1505
If I use the OGC Webservice button at our atlas.thuenen.de instance, eg this one https://atlas.thuenen.de/catalogue/#/?d=321%3Bdataset
resulting in https://atlas.thuenen.de/geoserver/geonode/ns_Pollachius_virens_first_decade_hs_1970/ows
It won´t work with QGIS
2024-09-10T09:22:31 WARNING Eigenschaften-Abfrage gescheitert:
Error transferring https://atlas.thuenen.de/geoserver/geonode/ns_Pollachius_virens_first_decade_hs_1970/ows?SERVICE=WMS&REQUEST=GetCapabilities - server replied:
While the 'same' request to stable.demo.geonode.org will work. Fetching the URL from https://stable.demo.geonode.org/catalogue/#/?d=4481%3Bdataset
results in : https://stable.demo.geonode.org/geoserver/geonode/a__20_2022_03_31/ows
Which loads properly in QGIS.
@gannebamm this is kind of funny .. GeoServer actually "finds" seven layers containing 1970
but does not display them:
Could you check, if this could be a permission thing (login as admin and perform the search above), just to check?
I can confirm it will find layers if authenticated:
But how to fix it?
Interesstingly the layer list will not display results after layer with number 251 these lists are full of layers:
next list is empty:
postponed until geosolutions is on board
Problem: The fetch OGC webservice url does not provide a valid endpoint. If you take a look at a dataset from the catalogue you can get the URL like:
But those result in a 404.
I have tested this feature successfully on stable (https://stable.demo.geonode.org/geoserver/geonode/a__20_2022_03_31/ows). Without this functionality I have to load the whole catalogue of OGC services.
Objective: As a user I want to load a specific dataset into my GIS client. The fetched URL should work as OGC endpoint. If a WMS is retrieved the styling shall be applied. (this doest work on stable)