-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
ArvidsO proposal is supported by the submitting organisation LGIA |
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. 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 |
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
…On Thu, 19 Oct 2023 at 10:54, arantzaetxebarria ***@***.***> wrote:
Dear @ArvidsO <https://github.com/ArvidsO>, @valdisbb
<https://github.com/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 <https://eur-lex.europa.eu/eli/reg/2010/1089>,
the following layers would be added:
[image: image]
<https://user-images.githubusercontent.com/64014694/276527813-815344c0-df6a-4960-abfb-8429ab663cc8.png>
By qualifying points (1) and (2), a layer will be added for each NaturalHazardCategory
codelist
<https://inspire.ec.europa.eu/codelist/NaturalHazardCategoryValue> item
and in the attribute “SpatialObjectType” all the four relevant feature
types (HazardArea, HazardAreaCoverage, ObservedEvent and
ObservedEventCoverage) will be mentioned.
Regards
—
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJFWM335BS563EFG4Z7DSMDYADMDDAVCNFSM5NIRDRCKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZXGAZDMMJVGY2Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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. |
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 |
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 |
In the Layer Register Natural risk zones contain only one layer: NZ.ExposedElement.
The Layer Register miss (see in TG):
The text was updated successfully, but these errors were encountered: