How to provide codes for noise in HH? about helpdesk HOT 7 CLOSED

Hi Johanna,
you simply cannot provide the NoiseSourceTypeValue with the current HH schema. As stated in the Forum post you mentioned above, the noise source issue has been addressed in a relevant IR Change Proposal for the ‘EnvHealthDeterminantMeasure’ spatial object type.

Stefania

from helpdesk.

Just one clarification regarding your statement "She is also relating to a change proposal which I guess is described here": the mentioned post relates to the mapping of the Noise Exposure delineation Priority Datasets under the Human Health and Safety data theme using the current schema. More specifically the post provides mapping examples for the measureTime and the validFrom and validTo elements already aligned with the recommendations in the revised END reporting
Hope this helps
Stefania

from helpdesk.

Hi Stefania,

Ok, thanks for the quick reply and the helpful information. I wondered if I had missed that information somehow. Then I will move on without providing the NoiseSourceTypeValue.

All the best

Johanna

from helpdesk.

Hi @sMorrone ,

Do you already have any insights on when it is planned to realize the changes from the accepted Change Proposal in the draft and/or endorsed xsd files?

All the best

Johanna

from helpdesk.

Hi @JohannaOtt ,
the revised IR has not been adopted yet, also waiting for the outcomes of mandatory evaluation of the INSPIRE Directive by January 2022. Meanwhile, a relevant INSPIRE Good Practice proposal by EEA is being drafted and plan is to submit it to MIG-T by June. The EEA is also drafting a Good Practice proposal for the use of geopackage as alternative encoding for the END spatial data (submission planned by June as well).

Stefania

from helpdesk.

Hi Stefania,

Is there any news here? Was the INSPIRE Good Practice proposal by the EEA submitted? Is it available?

from helpdesk.

Hi Kate,
given the new governance process for the INSPIRE artefacts and the creation of the repository to manage the changes to the INSPIRE XML schemas, it was decided not to create a Good Practice proposal. An issue was instead opened in the above repository (INSPIRE-MIF/application-schemas#6) and it has been directly assigned the "for Comitology" label, meaning that the change proposal was already endorsed by the MIG and is going through the Comitology procedure.

from helpdesk.