Digital Climate maps- how to publish

[trodin]

Hello, we have digital climate maps (tempereture, participation), 30 year period ([https://meteo.hr/klima_e.php?section=klima_hrvatska&param=k1_7]) in raster Geo tiff format grayscale for the whole country.

Can you tell me what is the best way to harmonise that kind of maps in inspire meteorological features theme and is it possible to create gml coverage with observation and measurment feature type based on geotiff file? And should geotiff source data be linked from gml file in that case?

Thank you,
Tanja

[KathiSchleidt]

Easiest is to create an Observation as follows as your GML linking to the the TIFF file

<?xml version="1.0" encoding="UTF-8"?>
<om:OM_Observation gml:id="OBS.1" xmlns:om="http://www.opengis.net/om/2.0" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:swe="http://www.opengis.net/swe/2.0" xsi:schemaLocation="
http://www.opengis.net/om/2.0 http://schemas.opengis.net/om/2.0/observation.xsd 
http://www.opengis.net/gml/3.2 http://schemas.opengis.net/gml/3.2.1/gml.xsd 
">
	<om:phenomenonTime>
		<gml:TimePeriod gml:id="TP.1">
			<gml:beginPosition>1971-01-01T00:00:00.000Z</gml:beginPosition>
			<gml:endPosition>2000-01-01T00:00:00.000Z</gml:endPosition>
		</gml:TimePeriod>
	</om:phenomenonTime>
	<om:resultTime>
		<gml:TimeInstant gml:id="TI.1">
			<gml:timePosition>"2024-10-12T00:00:00.000Z"</gml:timePosition>
		</gml:TimeInstant>
	</om:resultTime>
	<om:procedure xlink:href="https://codes.../model_description"/>
	<om:observedProperty xlink:href="https://codes.wmo.int/common/quantity-kind/airTemperature"/>
	<om:featureOfInterest xlink:href="http://.../Polygon_Croatia"/>
	<om:result xlink:href="https://meteo.hr/.../"/>
</om:OM_Observation>

[annat2022]

I already discussed this topic with @trodin. But it's not yet totally clear to me if it is INSPIRE compliant to reference the raster-dataset.

From our perspective, the mentioned climatology map falls under the INSPIRE theme Atmospheric Conditions and Meteorological Features (AC-MF). And from our understanding, INSPIRE regulations require publication of AC-MF data as a vector dataset containing observations. In that case there is no INSPIRE-compliant way to publish this data as a GeoTIFF but it would need to be converted to a GML coverage based on the ISO 19156 standard on Observations and Measurement (O&M). For details, see sec. 5.3.1.1 of the Data Specification on Atmospheric Conditions and Meteorological Geographical Features.

The solution to link the raster-file is only possible for INSPIRE datasets from themes that use RectifiedGridCoverages, such as Elevation, Orthoimagery, and Existing Land Use. For an overview and more in-depth explanation of INSPIRE coverages, see also this article.

Please correct me, if this assumption is wrong.

[KathiSchleidt]

If you look at D2.9 Guidelines for the use of Observations & Measurements and Sensor Web Enablement related
standards in INSPIRE, in Annex J, section 10.11.3.2. Option 2: (out-of-band) XLink the entire om:result, you'll find examples of external results.

In the example there, the result payload is a NetCDF file, but GeoTIFF is just as valid:

<om:result xlink:type="simple" xlink:href="http://web.access.server.org/pre-defined/cv-12345.nc"/>

[sMorrone]

Dear @trodin and @annat2022 , further to what @KathiSchleidt has already pointed out, the D2.9 states on page 94 that ‘’INSPIRE Data Specification themes like Atmospheric Conditions and Meteorological Geographical Features as well as in Oceanographic Geographical Features have come to a conclusion that for large grid coverage type INSPIRE data sets of those themes, it must be possible to link from GML encoded OM_Observation instances to results of those Observations encoded in external resources encoded using binary data formats." There are no restrictions on the type of binary data formats, so linking to a GeoTIFF external resource is fine.

[annat2022]

Hi @KathiSchleidt and @sMorrone,
thanks a lot for the feedback. One last questions: The section you are referring to is Annex K: Discussion paper on Out-Of-Band Results (informative). It's the discussion section. Does it become official somehow in the meantime? Even if it's "only" discussion part it is accepted to link to an external resource?

[sMorrone]

Hi @annat2022
Everything in the 'official' data specification is 'official'. The difference is between the informative and normative sections.
While normative sections contain mandatory rules, requirements or standards that must be followed, informative sections provide guidance, explanations or additional information that is not legally binding but supports implementation, e.g. best practices.
The Annex K is an informative section, meaning that you are not required to follow it, but it is recommended that you do so. Links to external resources are not only allowed, but encouraged.

[annat2022]

@sMorrone All right, thanks a lot for the clarification!