.. _metadatamodel: Metadata models ^^^^^^^^^^^^^^^ A data model defines and analyzes :ref:`entry` specifications to support a metadata structure corresponding to the business domain of the dataset. this structure is used to 1. represent the :ref:`entry`'s metadata of a dataset in different :ref:`media types `. 2. identify the values in the metadata according to the query parameters of an :ref:`opensearch-1` query and filter the dataset accordingly. 3. structure the :ref:`entry` properties in the representation .. _syndicationmetadatamodel: 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 catalog 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: .. code-block:: xml Query Result https://catalog.terradue.com/sentinel1/search?count=1&format=atom 2015-09-10T15:35:50.810201Z Terradue https://catalog.terradue.com/sentinel1/search?format=atom&uid=S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406 S1A GRD IW_DP L1 VV, VH 15 141205T051621-141205T051633
SwathIW
Orbit3587 ASCENDING
Track15
Start2014-12-05T16:16:21.5300370Z
End2014-12-05T16:16:33.4265590Z
2014-12-05T20:58:38.024Z 2014-12-05T20:58:38.024Z S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406
1 600 1 1
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 :ref:`opensearch-1` 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 :ref:`opensearch-1` 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 :ref:`index` where the entry is catalogd. .. _geotimemetadatamodel: 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 .. code-block:: xml https://catalog.terradue.com/sentinel1/search?format=atom&uid=S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406 S1A GRD IW_DP L1 VV, VH 15 141205T051621-141205T051633
SwathIW
Orbit3587 ASCENDING
Track15
Start2014-12-05T16:16:21.5300370Z
End2014-12-05T16:16:33.4265590Z
2014-12-05T20:58:38.024Z 2014-12-05T20:58:38.024Z 51.944363 5.898916 52.340702 9.548466 51.629356 9.728382 51.234165 6.135372 51.944363 5.898916 2014-12-05T16:16:21.5300370Z/2014-12-05T16:16:33.4265590Z MULTIPOLYGON(((5.898916 51.944363,9.548466 52.340702,9.728382 51.629356,6.135372 51.234165,5.898916 51.944363))) S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406
Several elements have been added representing a temporal and geographic reference in different format representations. Some elements are mandatory to fulfill the model such as "date" and the georrss "where". A :ref:`catalog` implementing the Geo & Time data model shall be able to provide with :ref:`opensearch-1` GeoTemporal service. The :ref:`opensearch-client-1` is able to analyse and extract geotemporal specification of the entries of an :ref:`opensearch-1` results (with the limitation of the capability to read the :ref:`mediatype` in which the result is represented). Full specification : `[10-032r8] OGC® OpenSearch Geo and Time Extensions `_ Earth Observation Profile Model """"""""""""""""""""""""""""""" Earth Observation :ref:`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 dataset 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: .. code-block:: xml 2014-12-05T16:16:21.5300370Z 2014-12-05T16:16:33.4265590Z S1A_IW_GRDH_1SDV_20141205T171621_20141205T171633_003587_0043C4_3406 IW_GRDH_1SDV NOMINAL GRD ARCHIVED ESRIN ESRIN headquarters Italy Rome GRD Post Processing Sentinel-1 IPF 002.36 L1 Sentinel-1 IW Level-1 GRD Product ESRIN ESRIN headquarters Italy Rome SLC Processing Sentinel-1 IPF 002.36 L1 Level-1 Intermediate SLC Product /data/localWD/468383535//S1A_AUX_PP1_V20141124T090000_G20141124T085940.SAFE /data/localWD/468383535//S1A_AUX_CAL_V20140915T100000_G20141003T151141.SAFE /data/localWD/468383535//S1A_AUX_INS_V20141204T130000_G20141204T123704.SAFE /data/localWD/468383535//S1A_OPER_AUX_RESORB_OPOD_20141205T192704_V20141205T152333_20141205T184103.EOF Airbus DS UPA_ United Kingdom Farnborough Generation of Sentinel-1 L0 SAR Product, dual polarisation L0 Level-0 Product Generation of Sentinel-1 SAR Slice L0 product single polarisation Raw Data Raw Data Downlink Channel1 1 Raw Data Generation of Sentinel-1 SAR Slice L0 product single polarisation Raw Data Raw Data Downlink Channel2 2 Raw Data 7206812c-d9cf-485c-89b3-f03a214be924 SAFE 809403257 51.944363 5.898916 52.340702 9.548466 51.629356 9.728382 51.234165 6.135372 51.944363 5.898916 S1A 0000-000A SAR Synthetic Aperture Radar RADAR IW_DP IW 3587 0 15 0001-01-01T00:00:00 838524.4 850420.9 39.078511453185818 34.526525608108237 38.682110388777183 -33.272595454981371 -45.76005650153126 -96.84402418069287 D VV, VH RIGHT 36.32666 45.73309 5405000454.33435 The model allows exhaustive specifications of an EarthObservation dataset. Combined with Atom, it is possible to include the EOP metadata in the :ref:`entry` either literally or by reference. the representation is further developed in the :ref:`media types ` section.