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

INSPIRE layer register #28

Open
ArvidsO opened this issue Feb 1, 2022 · 6 comments
Open

INSPIRE layer register #28

ArvidsO opened this issue Feb 1, 2022 · 6 comments
Assignees
Labels
for INSPIRE MIG-T The change proposal is to be assessed by the INSPIRE MIG-T.
Milestone

Comments

@ArvidsO
Copy link

ArvidsO commented Feb 1, 2022

In the Layer Register Natural risk zones contain only one layer: NZ.ExposedElement.
The Layer Register miss (see in TG):

  • NZ.RiskZone;
  • NZ.RiskZoneCoverage;
  • NZ. Example: NZ.Landslide (Spatial object type(s): HazardArea, HazardAreaCoverage (typeOfHazard: NaturalHazardCategoryValue));
  • NZ. Example: NZ.Flood (Spatial object type(s): ObservedEvent, ObservedEventCoverage (typeOfHazard: NaturalHazardCategoryValue));
  • NZ.ExposedElementCoverage .
@arantzaetxebarria arantzaetxebarria added the under analysis A first analysis is being performed label Oct 18, 2022
@arantzaetxebarria arantzaetxebarria added this to the 2023.2 milestone Jun 20, 2023
@arantzaetxebarria arantzaetxebarria added the change proposal This is a change proposal to the content of the INSPIRE registry label Jun 20, 2023
@arantzaetxebarria arantzaetxebarria self-assigned this Jun 20, 2023
@valdisbb
Copy link

ArvidsO proposal is supported by the submitting organisation LGIA

@arantzaetxebarria
Copy link
Collaborator

Dear @ArvidsO, @valdisbb

In order to present this change proposal for approval in the next sub-group meeting, we would like to inform you about the details that will be carried out.
On the basis of the document, the following layers would be added:

image

By qualifying points (1) and (2), a layer will be added for each NaturalHazardCategory codelist item and in the attribute “SpatialObjectType” all the four relevant feature types (HazardArea, HazardAreaCoverage, ObservedEvent and ObservedEventCoverage) will be mentioned.

Regards

@ArvidsO
Copy link
Author

ArvidsO commented Oct 20, 2023 via email

@arantzaetxebarria arantzaetxebarria added for Sub-group and removed under analysis A first analysis is being performed labels Oct 24, 2023
@arantzaetxebarria arantzaetxebarria removed this from the 2024.1 milestone Nov 13, 2023
@arantzaetxebarria
Copy link
Collaborator

arantzaetxebarria commented Nov 13, 2023

In the MIWP Action 2.3.1 MIG-T Sub-group Meeting on 10/11/2023, it was decided to put this proposal on hold.
Further changes to the NZ Technical Guidelines will be proposed by Istituto Superiore per la Protezione
e la Ricerca Ambientale (ISPRA)
by the end of 2023 which may affect / contribute to the layers proposed in this document. Therefore, it was agreed to wait for these technical guidelines changes before processing the current change proposal.

@arantzaetxebarria
Copy link
Collaborator

Hello everyone!
It's fine!
I would like to stress your attention to the INSPIRE layer register. It
includes only one Natural Hazard layer type - ExposedElement. It meen that
we have no legal choices to show in services different hazard types!!!

[image: image.png]

Best regards,

Arvids

Dear @ArvidsO

I would like to comment that even though this proposal has been put on hold, it is possible to add different layers that you need, as the INSPIRE Validator is relaxed in the test related to layer name (is manual) https://github.com/inspire-eu-validation/view-service/blob/master/iso-19128/at39bis-getcapabilities-harmonised-layer-name.md

Regards

@arantzaetxebarria arantzaetxebarria modified the milestones: 2024.2, 2025.1 May 20, 2024
@arantzaetxebarria arantzaetxebarria added for INSPIRE MIG-T The change proposal is to be assessed by the INSPIRE MIG-T. and removed change proposal This is a change proposal to the content of the INSPIRE registry for Sub-group labels Nov 12, 2024
@arantzaetxebarria
Copy link
Collaborator

In the MIWP Action 2.3.1 MIG-T Sub-group Meeting on 11/11/2024, it was agreed to bring this proposal for endorsement in the 80 MIG-T Meeting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for INSPIRE MIG-T The change proposal is to be assessed by the INSPIRE MIG-T.
Projects
None yet
Development

No branches or pull requests

4 participants