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

OWS Service / give higher priority to layer name than metadata/id when looking up layer #4362

Merged
merged 1 commit into from Jan 14, 2020

Conversation

jahow
Copy link
Contributor

@jahow jahow commented Jan 14, 2020

Sometimes in a GetCapabilities response several Layer objects can be pointed to the same metadata record, such breaking right after the first metadata UUID and/or identifier match would mean we might be at the wrong Layer object.

This can be tested with the following record:
https://sextant.ifremer.fr/geonetwork/srv/api/records/f8ed7346-94ae-4a86-b38e-3b07f7e5bf6a/formatters/xml

Without this PR, the second WMS layer of this record ("Chenaux de la baie de Saint Brieuc") cannot be added to the map because the layer lookup always finds the first layer ("Habitats benthiques...").

The behaviour should not be changed other than that.

@fxprunayre apparently you're the last one to have modified this logic, please let me know if you think that fix is acceptable! thanks

Sometimes several Layer objects can be pointed to the same metadata record,
as such breaking right after a Metadata URL match would mean we might be
looking at the wrong Layer object.
@fxprunayre fxprunayre added this to the 3.10.0 milestone Jan 14, 2020
@fxprunayre fxprunayre merged commit e2e0a21 into geonetwork:master Jan 14, 2020
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

Successfully merging this pull request may close these issues.

None yet

2 participants