Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relax requirement for a GetCapabilities URL ? #47

Open
fvanderbiest opened this issue Sep 11, 2017 · 5 comments
Open

Relax requirement for a GetCapabilities URL ? #47

fvanderbiest opened this issue Sep 11, 2017 · 5 comments

Comments

@fvanderbiest
Copy link
Member

#1
  UUID : FR-256702788-20160125_001_COM_COL
  DONNEES - Communes colonisées par le moustique tigre Aedes albopictus
    WMS url: KO: https://www.cigalsace.org/geoserver/SLM67/wms: Metadata FR-256702788-20160125_001_COM_COL references a layer : SLM67_COMMUNES_COL_L93 on https://www.cigalsace.org/geoserver/SLM67/wms which is not a valid WMS GetCapabilities URL
    WFS url: KO: No wfs url found in the metadata
@pmauduit
Copy link
Member

It has been explicitely specified by Rennes métropole that WxS url should be fully-qualified (i.e. with parameters to get the actual GetCapabilities document)

@fvanderbiest
Copy link
Member Author

I would be happy to hear @bchartier or @fphg or @jpklipfel on the subject ...

@jpklipfel
Copy link

UUID : FR-256702788-20160125_001_COM_COL
WFS url: KO: No wfs

This is true

It has been explicitely specified by Rennes métropole that WxS url should be fully-qualified (i.e. with parameters to get the actual GetCapabilities document)

We were more on a non-qualitative wfs url so that the catalog can itself put the qualification at the time of the action (getcapabilities, getfeature ...)
But we can adapt @MaelREBOUX why this specification?

@bchartier
Copy link

mdchecker (https://github.com/geobretagne/mdchecker) also expects a fully qualified GetCapabilities URL in the datasets metadata. I think it has been designed this way in order to pass the metadata conformance tests build by french environment ministry for Inspire annual reports.

An official european metadata testing tool has been release a few weeks ago:
http://inspire-sandbox.jrc.ec.europa.eu/validator/
It would be interesting to identify if this tool is expecting fully qualified GetCapabilities URLs or not.

In my humble opinion, service URLs should remain service URLs and URLs of a specific operation. The current W*S service specification should be rewritten in order that the service URL lead to an internet resource instead of a 404 error.

@fvanderbiest
Copy link
Member Author

Anyway I found an issue while extracting when a GetCapabilties URL is provided: georchestra/georchestra#1781

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants