DescribeSensor includes the two outputs with the same phenomenon

[ridoo]

Phenomenon/observedProperty http://dd.eionet.europa.eu/vocabulary/aq/pollutant/8 should not be listed twice. Keep the UOM as clients will need that information!

Output Section:

<outputs>
  <OutputList>
     <output name="http://dd.eionet.europa.eu/vocabulary/aq/pollutant/8">
        <swe:Quantity definition="http://dd.eionet.europa.eu/vocabulary/aq/pollutant/8"></swe:Quantity>
     </output>
     <output name="http://dd.eionet.europa.eu/vocabulary/aq/pollutant/8">
        <swe:Quantity definition="http://dd.eionet.europa.eu/vocabulary/aq/pollutant/8">
           <swe:uom code="ug.m-3"/>
        </swe:Quantity>
     </output>
  </OutputList>
</outputs>

Example:
DescribeSensor for http://cdr.eionet.europa.eu/gb/eu/aqd/e2a/colutn32a/envuvlxkq/D_GB_StationProcess.xml#GB_StationProcess_1

[ridoo]

Clients have problems in displaying timeseries data and metadata, since it is not possible to reference observations to a corresponding UOM.

The UOM can either be put in the SensorML file which is used to link timeseries parameters or be put into a GO reponse. However, the current outputs section of a SensorML file references the same phenomenon multiple times. This is caused by the 1:n-relationship of a timeseries with the UOM which has been used to measure a value. Even the GO response does not contain a UOM.

That inconsistency within the data model has to be fixed so that just one unit is available for a whole timeseries and can be declared in the metadata unambigously.