Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

granule_uid is equivalent to the previous index parameter and provides a unique ID for the granule in the service, ie for each line in the epn_core view (index is a reserved word in many database languages and should not have been used in the first place)

granule_gid is related to a type of product: it is identical for all granules containing the same type of information for different observations (e.g., calibrated files)

obs_id is related to an observation: it is identical for all granules related to the same observation, containing different type of data (e.g.: raw and calibrated data, associated geometry, etc). In many EPN-TAP v1 services, such products were described together on the same line with a unique index parameter.

 

As a general rule, different products related to the same observation are no longer described together on a single line of the epn_core view, but on successive lines associated by the same obs_id, each with a different granule_gid (and a specific granule_uid, see Table 2 below).

It is recommended to link only one product per line in the epn_core view (plus a thumbnail wherever relevant). The notion of "main product" (more or less explicit in v1) is therefore deprecated, and the epn_core in v2 includes more lines than in v1. Although less compact that the previous table presentation, this list presentation is much more efficient for machine-handling.

...

The corresponding parameters may be present also in the registry declaration though, to provide a fast description of services.

...