Closed KathiSchleidt closed 5 days ago
Is a feature really metadata, as in:
"metadata": "http://luft.umweltbundesamt.at/inspire/wfs?service=WFS&version=2.0.0&request=GetFeature&typeName=aqd:AQD_SamplingPointProcess"
Perhaps it should point to a description of the feature like:
"metadata": "http://luft.umweltbundesamt.at/inspire/wfs?service=WFS&version=2.0.0&request=DescribeFeatureType&typeName=aqd:AQD_SamplingPointProcess"
@nmtoken this data is originally provided via SOS as part of the Austrian Air Quality Reporting. Within API4INSPIRE, we harvest this and re-provide as STA, keeping the original values.
Not sure why I didn't link to DescribeFeatureType when I set up the original SOS ages ago, probably because the DescribeFeatureType response is strangely unsatisfying:
<xsd:schema elementFormDefault="qualified" targetNamespace="http://dd.eionet.europa.eu/schemaset/id2011850eu-1.0">
<xsd:include schemaLocation="http://dd.eionet.europa.eu/schemas/id2011850eu-1.0/AirQualityReporting.xsd"/>
</xsd:schema>
Goal here is to see how STA aligns with O&M/OMS
See #271
@rob-metalinkage An example, to see if we can align SOSA and STA
Taken from the air quality STA at https://airquality-frost.k8s.ilt-dmz.iosb.fraunhofer.de/v1.1 The @iot.selfLink will resolve to the shown JSON
sosa:Platform ~ STA:Thing:
sosa:HomogeneousObservationCollection ~ STA:Datastream
ObservedProperty
Sensor
Observation
FeatureOfInterest
From: https://datacoveeu.github.io/API4INSPIRE/sensorthingsapi/requestingData/STA-Data-Model.html