jescriu
commented
2 years ago Dear @hallinpihlatie, Thank you for spotting this issue.
In principle, NS4.* indicators are based on self-declaration of conformity (of services). Taking the specific example you provided based on your discovery service, if you declare in the service metadata that the service is conformant the INSPIRE Geoportal should maintain the value that you self-declared.
I will check with our IT Team if the INSPIRE Geoportal is performing any additional validation on top of the discovery service (guess not), and if this not the case we will analyse if there is any issue in reading the value of the self-declared conformity. Therefore, I will come back to you on this.
Having this said, I took the chance to:
- Validate your discovery service metadata: with positive result - i.e. metadata is compliant according to the INSPIRE Reference Validator, as you can (temporarily) see in this validation report.
- Validate your discovery service: with negative result - i.e. the service is not compliant according to the INSPIRE Reference Validator, as you can (temporarily) see in this validation report.
Bearing in mind these results, let me clarify that self-declaration of conformity shall be based on the result obtained from the applicable tests in the INSPIRE Reference Validator (which is the reference tool to be utilised when facing this task), which in this case refers to the discovery service, not to its metadata record.
jrc-inspire
A question related to the calculation of the NS4.* indicators with an example of the NS4.1 indicator (conformity of discovery services), where the INSPIRE Geoportal plays a role, but the indicators are based on "self-declaration".
The metadata of the Finnish discovery service passes the metadata validation test for Network services, but indicator NS4.1 is 0%.
What else is the Geoportal/Monitoring checking in the calculation of the NS4.* indicators? How can we check these indicators in advance before the 2022 December deadline?