Metadata models

A data model defines and analyzes Entry specifications to support a metadata structure corresponding to the business domain of the dataset. this structure is used to

  1. represent the Entry‘s metadata of a dataset in different media types.
  2. identify the values in the metadata according to the query parameters of a opensearch query and filter the dataset accordingly.
  3. structure the Entry properties in the representation

The Base Syndication Model : Atom

This is the base model for all the others. Based on Atom, it is used to describe feeds of information. This is typically used by news web sites, to publish a list a of news articles that are available for reading. Its structure is particulary well designed for catalogue service.

The key issue when indexing metadata is to make sure that we don’t lose any information in the process. Apart from the entry’s content itself, we’re also interested in preserving the fundamental metadata about the entry too, namely:

  • What it is called
  • Who created it
  • When it was created
  • Where it is

Atom is specifically designed to never lose any data. To see this, let’s take a look at this example of an Atom feed:

<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text">Query Result</title>
  <id>https://catalog.terradue.com/sentinel1/search?count=1&amp;format=atom</id>
  <updated>2015-09-10T15:35:50.810201Z</updated>
  <link rel="self" type="application/atom+xml" title="Reference link" href="https://catalog.terradue.com/sentinel1/search?count=1&amp;format=atom" />
  <link rel="search" type="application/opensearchdescription+xml" title="OpenSearch Description link" href="https://catalog.terradue.com/sentinel1/description" />
  <author>
      <name>Terradue</name>
    </author>
  <entry>
    <id>https://catalog.terradue.com/sentinel1/search?format=atom&amp;uid=S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406</id>
    <title type="text">S1A GRD IW_DP L1 VV, VH 15 141205T051621-141205T051633</title>
    <summary type="html">
      <table> <tbody> <table> <tr>  <td><strong>Swath</strong></td><td>IW</td>  </tr><tr> <td><strong>Orbit</strong></td><td>3587 ASCENDING</td>  </tr><tr> <td><strong>Track</strong></td><td>15</td>  </tr><tr> <td><strong>Start</strong></td><td>2014-12-05T16:16:21.5300370Z</td>  </tr><tr> <td><strong>End</strong></td><td>2014-12-05T16:16:33.4265590Z</td>  </tr> </table>  </tbody></table>
    </summary>
    <published>2014-12-05T20:58:38.024Z</published>
    <updated>2014-12-05T20:58:38.024Z</updated>
    <link rel="enclosure" type="application/octet-stream" length="809403257" href="https://scihub.esa.int/dhus/odata/v1/Products('7206812c-d9cf-485c-89b3-f03a214be924')/$value" />
    <link rel="self" type="application/atom+xml" title="Reference link" href="https://catalog.terradue.com/sentinel1/search?format=atom&amp;uid=S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406" />
    <identifier xmlns="http://purl.org/dc/elements/1.1/">S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406</identifier>
  </entry>
  <queryTime xmlns="http://purl.org/dc/elements/1.1/">1</queryTime>
  <totalResults xmlns="http://a9.com/-/spec/opensearch/1.1/">600</totalResults>
  <startIndex xmlns="http://a9.com/-/spec/opensearch/1.1/">1</startIndex>
  <itemsPerPage xmlns="http://a9.com/-/spec/opensearch/1.1/">1</itemsPerPage>
  <os:Query xmlns:os="http://a9.com/-/spec/opensearch/1.1/" xmlns:param="http://a9.com/-/spec/opensearch/extensions/parameters/1.0/" xmlns:geo="http://a9.com/-/opensearch/extensions/geo/1.0/" xmlns:time="http://a9.com/-/opensearch/extensions/time/1.0/" xmlns:eop="http://www.opengis.net/eop/2.0" os:count="1" />
</feed>

An Atom feed is XML and so must follow all the usual well-formedness rules that that implies. It consists of some metadata about the feed, followed by one or more entries. This metadata chunk contains all of the data mandatory in an opensearch result. The id element provides the “where,” giving the feed’s URI. The title provides a “what,” giving the title of the feed. updated gives the “when,” with an obligation to say when the feed was last changed. author says “who” created the feed, and link provides the “how” giving a link to the description of the search and the self link of the resource the feed represents.

The entry section, just like the feed’s main metadata section, has the obligatory id, title, updated, and opensearch links. It wouldn’t be much use without the content, and it’s recommended to have the summary, as “a short summary, abstract, or excerpt of the entry”. In addition to those core features, it should also contain extended elements such as the “identifier” element with another namespace that has a meaning in the domain it was defined and moreover defines the unique identifier in the Index where the entry is catalogued.

Geo & Time model

The Geo & Time model is directly derived from the specification for the OpenSearch Geo and Time extensions. it is intended to provide a very simple way to structure spatial and temporal metadata to a geospatial entry that contains geographic and temporal properties.

In short, an Geo&Time entry is specified by: - a temporal reference - a geographic reference

In atom representation, here is the previous Atom entry example supplemented with the Geo & Time model information

<entry>
  <id>
    https://catalog.terradue.com/sentinel1/search?format=atom&amp;uid=S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406
  </id>
  <title type="text">S1A GRD IW_DP L1 VV, VH 15 141205T051621-141205T051633</title>
  <summary type="html">
    <table> <tbody> <table> <tr>  <td><strong>Swath</strong></td><td>IW</td>  </tr><tr> <td><strong>Orbit</strong></td><td>3587 ASCENDING</td>  </tr><tr> <td><strong>Track</strong></td><td>15</td>  </tr><tr> <td><strong>Start</strong></td><td>2014-12-05T16:16:21.5300370Z</td>  </tr><tr> <td><strong>End</strong></td><td>2014-12-05T16:16:33.4265590Z</td>  </tr> </table>  </tbody></table>
  </summary>
  <published>2014-12-05T20:58:38.024Z</published>
  <updated>2014-12-05T20:58:38.024Z</updated>
  <link rel="enclosure" type="application/octet-stream" length="809403257" href="https://scihub.esa.int/dhus/odata/v1/Products('7206812c-d9cf-485c-89b3-f03a214be924')/$value" />
  <link rel="self" type="application/atom+xml" title="Reference link" href="https://catalog.terradue.com/sentinel1/search?format=atom&amp;uid=S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406" />
  <link rel="alternate" type="application/xml" title="EOP profile" href="https://catalog.terradue.com/eop/sentinel1/profile/xml?uid=S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406" />
  <link rel="search" type="application/opensearchdescription+xml" title="OpenSearch Description link" href="https://catalog.terradue.com/sentinel1/description" />
  <where xmlns="http://www.georss.org/georss">
    <MultiSurface xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.opengis.net/gml/3.2">
      <surfaceMembers>
        <Polygon>
          <exterior>
            <LinearRing>
              <posList srsDimension="2" count="5">51.944363 5.898916 52.340702 9.548466 51.629356 9.728382 51.234165 6.135372 51.944363 5.898916</posList>
            </LinearRing>
          </exterior>
        </Polygon>
      </surfaceMembers>
    </MultiSurface>
  </where>
  <date xmlns="http://purl.org/dc/elements/1.1/">2014-12-05T16:16:21.5300370Z/2014-12-05T16:16:33.4265590Z</date>
  <spatial xmlns="http://purl.org/dc/terms/">
    MULTIPOLYGON(((5.898916 51.944363,9.548466 52.340702,9.728382 51.629356,6.135372 51.234165,5.898916 51.944363)))
  </spatial>
  <identifier xmlns="http://purl.org/dc/elements/1.1/">S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406</identifier>
</entry>

Several elements have been added representing a temporal and geographic reference in different format representation. Some elements are mandatory to fulfill the model such as “date” and the georrss “where”.

A Catalogue implementing the Geo & Time data model shall be able to provide with opensearch GeoTemporal service. The opensearch-client is able to analyse and extract geotemporal specification of the entries of an opensearch results (with the limitation of the capability to read the Content Type in which the result is represented).

Full specification : [10-032r8] OGC® OpenSearch Geo and Time Extensions

Earth Observation Profile Model

Earth Observation Dataset are generally managed within logical collections that are usually structured to contain data items derived from sensors onboard a satellite or series of satellites. The key characteristics differentiating products within the collections are date of acquisition, location as well as characteristics depending on the type of sensor, For example, key characteristics for optical imagery are the possible presence of cloud, haze, smokes or other atmospheric or on ground phenomena obscuring the image. The common metadata used to distinguish EO products types are defined and analysed for generic and thematic EO products (i.e optical, radar, atmospheric, altimetry, limb-looking and synthesis and systematic products).

The base of the EO data model is based on the Earth Observation Metadata profile of Observations & Measurements that is another OGC implementation standard. This profile is intended to provide a standard schema for encoding Earth Observation product metadata to support the description and cataloguing of products from sensors aboard EO satellites.

EO daatset metadata encoded using this profile of Observations and Measurements shall produce XML documents that are fully compliant with the normative XML Schema Documents associated with this standard. Here is an example corresponding to the previous example:

<EarthObservation xmlns="http://www.opengis.net/sar/2.1" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <boundedBy xmlns="http://www.opengis.net/gml/3.2" xsi:nil="true"/>
  <phenomenonTime xmlns="http://www.opengis.net/om/2.0">
    <TimePeriod xmlns="http://www.opengis.net/gml/3.2">
      <beginPosition>2014-12-05T16:16:21.5300370Z</beginPosition>
      <endPosition>2014-12-05T16:16:33.4265590Z</endPosition>
    </TimePeriod>
  </phenomenonTime>
  <observedProperty xmlns="http://www.opengis.net/om/2.0" xsi:nil="true"/>
  <metaDataProperty xmlns="http://www.opengis.net/eop/2.1">
    <EarthObservationMetaData>
      <identifier>S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406</identifier>
      <parentIdentifier>IW_GRDH_1SDV</parentIdentifier>
      <acquisitionType>NOMINAL</acquisitionType>
      <productType>GRD</productType>
      <status>ARCHIVED</status>
      <processing>
        <ProcessingInformation>
          <processingCenter>ESRIN ESRIN headquarters Italy Rome</processingCenter>
          <method>GRD Post Processing</method>
          <processorName>Sentinel-1 IPF</processorName>
          <processorVersion>002.36</processorVersion>
          <processingLevel>L1</processingLevel>
          <nativeProductFormat>Sentinel-1 IW Level-1 GRD Product</nativeProductFormat>
        </ProcessingInformation>
      </processing>
      <processing>
        <ProcessingInformation>
          <processingCenter>ESRIN ESRIN headquarters Italy Rome</processingCenter>
          <method>SLC Processing</method>
          <processorName>Sentinel-1 IPF</processorName>
          <processorVersion>002.36</processorVersion>
          <processingLevel>L1</processingLevel>
          <nativeProductFormat>Level-1 Intermediate SLC Product</nativeProductFormat>
          <auxiliaryDataSetFileName>/data/localWD/468383535//S1A_AUX_PP1_V20141124T090000_G20141124T085940.SAFE</auxiliaryDataSetFileName>
          <auxiliaryDataSetFileName>/data/localWD/468383535//S1A_AUX_CAL_V20140915T100000_G20141003T151141.SAFE</auxiliaryDataSetFileName>
          <auxiliaryDataSetFileName>/data/localWD/468383535//S1A_AUX_INS_V20141204T130000_G20141204T123704.SAFE</auxiliaryDataSetFileName>
          <auxiliaryDataSetFileName>/data/localWD/468383535//S1A_OPER_AUX_RESORB_OPOD_20141205T192704_V20141205T152333_20141205T184103.EOF</auxiliaryDataSetFileName>
        </ProcessingInformation>
      </processing>
      <processing>
        <ProcessingInformation>
          <processingCenter>Airbus DS UPA_ United Kingdom Farnborough</processingCenter>
          <method>Generation of Sentinel-1 L0 SAR Product, dual polarisation</method>
          <processorName/>
          <processorVersion/>
          <processingLevel>L0</processingLevel>
          <nativeProductFormat>Level-0 Product</nativeProductFormat>
        </ProcessingInformation>
      </processing>
      <processing>
        <ProcessingInformation>
          <method>Generation of Sentinel-1 SAR Slice L0 product single polarisation</method>
          <nativeProductFormat>Raw Data</nativeProductFormat>
        </ProcessingInformation>
      </processing>
      <processing>
        <ProcessingInformation>
          <method>Raw Data Downlink Channel1 1</method>
          <nativeProductFormat>Raw Data</nativeProductFormat>
        </ProcessingInformation>
      </processing>
      <processing>
        <ProcessingInformation>
          <method>Generation of Sentinel-1 SAR Slice L0 product single polarisation</method>
          <nativeProductFormat>Raw Data</nativeProductFormat>
        </ProcessingInformation>
      </processing>
      <processing>
        <ProcessingInformation>
          <method>Raw Data Downlink Channel2 2</method>
          <nativeProductFormat>Raw Data</nativeProductFormat>
        </ProcessingInformation>
      </processing>
    </EarthObservationMetaData>
  </metaDataProperty>
  <result xmlns="http://www.opengis.net/om/2.0">
    <EarthObservationResult xmlns="http://www.opengis.net/eop/2.1">
      <boundedBy xmlns="http://www.opengis.net/gml/3.2" xsi:nil="true"/>
      <product>
        <ProductInformation>
          <fileName>
            <d7p1:ServiceReference d7p1:type="simple" d7p2:href="https://scihub.esa.int/dhus/odata/v1/Products(%277206812c-d9cf-485c-89b3-f03a214be924%27)/$value" d7p2:title="simple" xmlns="http://www.opengis.net/ows/2.0" xmlns:d7p1="http://www.opengis.net/ows/2.0" xmlns:d7p2="http://www.w3.org/1999/xlink">
              <d7p1:Identifier>7206812c-d9cf-485c-89b3-f03a214be924</d7p1:Identifier>
              <d7p1:Format>SAFE</d7p1:Format>
            </d7p1:ServiceReference>
          </fileName>
          <size>809403257</size>
        </ProductInformation>
      </product>
    </EarthObservationResult>
  </result>
  <featureOfInterest xmlns="http://www.opengis.net/om/2.0">
    <Footprint xmlns="http://www.opengis.net/eop/2.1">
      <boundedBy xmlns="http://www.opengis.net/gml/3.2" xsi:nil="true"/>
      <multiExtentOf>
        <MultiSurface xmlns="http://www.opengis.net/gml/3.2">
          <surfaceMembers>
            <Polygon>
              <exterior>
                <LinearRing>
                  <posList count="5" srsDimension="2">51.944363 5.898916 52.340702 9.548466 51.629356 9.728382 51.234165 6.135372 51.944363 5.898916</posList>
                </LinearRing>
              </exterior>
            </Polygon>
          </surfaceMembers>
        </MultiSurface>
      </multiExtentOf>
    </Footprint>
  </featureOfInterest>
  <procedure xmlns="http://www.opengis.net/om/2.0">
    <EarthObservationEquipment xmlns="http://www.opengis.net/eop/2.1">
      <boundedBy xmlns="http://www.opengis.net/gml/3.2" xsi:nil="true"/>
      <platform>
        <Platform>
          <shortName>S1A</shortName>
          <serialIdentifier>0000-000A</serialIdentifier>
        </Platform>
      </platform>
      <instrument>
        <Instrument>
          <shortName>SAR</shortName>
          <description>Synthetic Aperture Radar</description>
        </Instrument>
      </instrument>
      <sensor>
        <Sensor>
          <sensorType>RADAR</sensorType>
          <operationalMode codeSpace="urn:eop:SEN1:sensorMode">IW_DP</operationalMode>
          <swathIdentifier codeSpace="urn:eop:SEN1:swathIdentifier">IW</swathIdentifier>
        </Sensor>
      </sensor>
      <acquisitionParameters>
        <Acquisition xmlns="http://www.opengis.net/sar/2.1">
          <orbitNumber xmlns="http://www.opengis.net/eop/2.1">3587</orbitNumber>
          <lastOrbitNumber xmlns="http://www.opengis.net/eop/2.1">0</lastOrbitNumber>
          <wrsLongitudeGrid xmlns="http://www.opengis.net/eop/2.1">15</wrsLongitudeGrid>
          <ascendingNodeDate xmlns="http://www.opengis.net/eop/2.1">0001-01-01T00:00:00</ascendingNodeDate>
          <startTimeFromAscendingNode xmlns="http://www.opengis.net/eop/2.1">838524.4</startTimeFromAscendingNode>
          <completionTimeFromAscendingNode xmlns="http://www.opengis.net/eop/2.1">850420.9</completionTimeFromAscendingNode>
          <illuminationZenithAngle xmlns="http://www.opengis.net/eop/2.1">39.078511453185818</illuminationZenithAngle>
          <illuminationElevationAngle xmlns="http://www.opengis.net/eop/2.1">34.526525608108237</illuminationElevationAngle>
          <incidenceAngle xmlns="http://www.opengis.net/eop/2.1">38.682110388777183</incidenceAngle>
          <pitch xmlns="http://www.opengis.net/eop/2.1">-33.272595454981371</pitch>
          <roll xmlns="http://www.opengis.net/eop/2.1">-45.76005650153126</roll>
          <yaw xmlns="http://www.opengis.net/eop/2.1">-96.84402418069287</yaw>
          <polarisationMode>D</polarisationMode>
          <polarisationChannels>VV, VH</polarisationChannels>
          <antennaLookDirection>RIGHT</antennaLookDirection>
          <minimumIncidenceAngle>36.32666</minimumIncidenceAngle>
          <maximumIncidenceAngle>45.73309</maximumIncidenceAngle>
          <dopplerFrequency>5405000454.33435</dopplerFrequency>
        </Acquisition>
      </acquisitionParameters>
    </EarthObservationEquipment>
  </procedure>
</EarthObservation>

The model allows exhaustive specifications of an EarthObservation dataset.

Combined with Atom, it is possible to include the EOP metadata in the Entry either litterally or by reference. the representation is further developed in the media types section.