Geoserver WMS : Layer has no metadataurl

[zulf10]

Hello,

on GeoServer WMS return lot of "Layer has no metadataurl" but most of layer has good metadata on GeoServer configuration.
It seems that is related to the type of metadata 19139.

Gaia return no error on other layer with metadata type TC211.

Is metadata type analysed on Gaia ?

[landryb]

can you post the url of the getcapabilites, or a sample of it if not public ? or your gaia url ? the check done is here: https://github.com/georchestra/gaia/blob/master/geordash/checks/ows.py#L105, eg it lists the metadataurls parsed by owslib, and returns NoMetadataUrl in https://github.com/georchestra/gaia/blob/master/geordash/checks/ows.py#L129 if none is found.

it's not checking the type/mimetype yet, because i planned to do so to ensure the bare minimum is here for proper metadata display in mapstore

[zulf10]

Global getcapabilities : https://www.datagrandest.fr/geoserver/geograndest/ows?service=WMS&version=1.3.0&request=GetCapabilities

Layer getcapabilities example : https://www.datagrandest.fr/geoserver/geograndest/GGE_ORTHOIRC_2018_54_TIF_L93/ows?service=WMS&version=1.3.0&request=GetCapabilities

In GeoServer, we have this configuration

text/html link : https://www.datagrandest.fr/geonetwork/srv/fre/catalog.search#/metadata/FR-200052264-GGE_ORTHORVB_2018_54_TIF_L93
text/xml link : https://www.datagrandest.fr/geonetwork/srv/api/records/FR-200052264-GGE_ORTHORVB_2018_54_TIF_L93/formatters/xml

Metadata is on 19139 type

[landryb]

what i was saying in #44 (comment) is that im not sure the WMS spec allows 'freeform' values for type, iirc mapstore for example only supported TC211, ISO 19115:2003, FGDC:1998 is also apparently allowed by the spec. That doesnt explain why the NoMetadataUrl though, since owslib manages to find them:

>>> from owslib.wms import WebMapService
>>> x=WebMapService('https://www.datagrandest.fr/geoserver/geograndest/GGE_ORTHOIRC_2018_54_TIF_L93/ows?service=WMS&version=1.3.0&request=GetCapabilities',version='1.3.0')
>>> l=x.contents['GGE_ORTHOIRC_2018_54_TIF_L93']
>>> l.metadataUrls
[{'type': '19139', 'format': 'text/html', 'url': 'https://www.datagrandest.fr/geonetwork/srv/fre/catalog.search#/metadata/FR-200052264-GGE_ORTHORVB_2018_54_TIF_L93'}, {'type': '19139', 'format': 'text/xml', 'url': 'https://www.datagrandest.fr/geonetwork/srv/api/records/FR-200052264-GGE_ORTHORVB_2018_54_TIF_L93/formatters/xml'}]

were the metadataUrls present when you did the initial check, or you added them afterwards ? or that can be due to a previous version of the getcapabilities, cached in the worker ?

[zulf10]

It's strange, Geoserver allows the following types to be used :

metadataUrls present when Gaia setup. I don't think that can be due to a previous version of the getcapabilities (maybe @jeanmi151 confirm ?)

Is OWSlib problem with 19139 type ? 🤔

[landryb]

im not sure geoserver 'allows' those values, it's just autocompletion from values that were manually entered in the field.. and below you have the warning for WMS 1.1.1: Note only FGDC and TC211 metadata links show up in WMS 1.1.1 capabilities

owslib doesnt seem to have an issue with plain 19139 string (as shown in my previous comment) so i dont really know why it failed. I'll have to recheck

[zulf10]

I'm sure metadata type are not manually add.

On second browser (privacy mode on) :

Thanks for your check :)

[landryb]

that's strange, because for me it was a free-form textfield, and not a select box in a list of options.. and on my 2.27.3 instance i dont have that behaviour.

maybe browser-dependant..

[zulf10]

By Default, this field is ISO19115:2003. If you clear field, all type are displayed ;-)

[bchartier]

that's strange, because for me it was a free-form textfield, and not a select box in a list of options..

Yes, it's a free form but when the text field is empty, it suggests a list of predefined values (as said by @zulf10). I have just checked this on another geOrchestra plateform (Géo2France) : the same values are proposed (ISO19115:2003, FGDC, TC211, 19119 and other).

[bchartier]

iirc mapstore for example only supported TC211, ISO 19115:2003, FGDC:1998 is also apparently allowed by the spec

From the WMS 1.3 spec:

The Web Map Service provider decides what information to include, exclude or aggregate in each layer. However,
each layer should be documented in accordance with ISO 19115 or FGDC-STD-001-1998 [1], and a link to that
metadata should be provided in the element defined below.

Two “type” attribute values are defined by this International Standard: the value “ISO 19115:2003”
refers to ISO 19115:2003; the value “FGDC:1998” refers to FGDC-STD-001-1998 [1]. An information community
may define meanings for other “type” attribute values

On OWSLib side, the situation is unclear:
Some lines of code mention some values:

# wfs110.py
                    if metadataUrl["type"] == "FGDC":
                        mdelem = doc.find(".//metadata")
                        if mdelem is not None:
                            metadataUrl["metadata"] = Metadata(mdelem)
                        else:
                            metadataUrl["metadata"] = None
                    elif metadataUrl["type"] in ["TC211", "19115", "19139"]:

# wms111.py
                    if metadataUrl['type'] == 'FGDC':
                        mdelem = doc.find('.//metadata')
                        if mdelem is not None:
                            metadataUrl['metadata'] = Metadata(mdelem)
                            continue

                    if metadataUrl['type'] == 'TC211':

None of these values can be found in the WMS 1.3.0 spec: “ISO 19115:2003” and “FGDC:1998”.

For WMS 1.3, OWSLib doest not seem to take care of the type attribute.

[landryb]

cf geosolutions-it/MapStore2#7865 for mapstore 'requirements' that i had relaxed from what they were originally

[bchartier]

cf geosolutions-it/MapStore2#7865 for mapstore 'requirements' that i had relaxed from what they were originally

Thank you!

[zulf10]

Thanks to all !

Based on the feedback, it seems that OWSlib is not correctly handling type 19139 (not sure !).
We change type on each layer on GeoServer