Inspire revision 4711
Gyldig
-- Name --
single mosaic element
Mosaic element relating to a single input image.
-- Description --
NOTE The geometry of a single mosaic element corresponds exactly to the contributing area, in the mosaic, of the single input image.
| Egenskap |
Stereotype |
Beskrivelse |
Type |
Multiplisitet |
| imageSourceReference |
|
-- Name --
image source reference
|
CharacterString |
0..1 |
| MosaicElement |
| inspireId |
|
-- Name --
inspire identifier
|
Identifier
(datatype)
|
0..1 |
| - localId |
|
|
CharacterString |
1..1 |
| - namespace |
|
|
CharacterString |
1..1 |
| - versionId |
|
|
CharacterString |
0..1 |
| geometry |
|
-- Name --
geometry
|
GM_MultiSurface |
1..1 |
| phenomenonTime |
|
-- Name --
phenomenon time
|
TM_Period |
1..1 |
| Navn |
Type |
Lengde |
Multiplisitet |
|
Identifier
(datatype)
|
|
0..1 |
| - |
CharacterString |
|
1..1 |
| - |
CharacterString |
|
1..1 |
| - |
CharacterString |
|
0..1 |
|
GM_MultiSurface |
|
1..1 |
|
TM_Period |
|
1..1 |
|
CharacterString |
|
0..1 |
| Name |
Type |
English |
Description |
| inspireId |
Identifier
(datatype)
|
|
External object identifier of the spatial object.
-- Description --
NOTE 1 An external object identifier is a unique object identifier published by the responsible body, which may be used by external applications to reference the spatial object. The identifier is an identifier of the spatial object, not an identifier of the real-world phenomenon.
NOTE 2 This property should be used to reference indirect MosaicElement instances from Orthoimage instances unambiguously.
|
| - localId |
CharacterString |
|
A local identifier, assigned by the data provider. The local identifier is unique within the namespace, that is no other spatial object carries the same unique identifier.
-- Description --
NOTE It is the responsibility of the data provider to guarantee uniqueness of the local identifier within the namespace.
|
| - namespace |
CharacterString |
|
Namespace uniquely identifying the data source of the spatial object.
-- Description --
NOTE The namespace value will be owned by the data provider of the spatial object and will be registered in the INSPIRE External Object Identifier Namespaces Register.
|
| - versionId |
CharacterString |
|
The identifier of the particular version of the spatial object, with a maximum length of 25 characters. If the specification of a spatial object type with an external object identifier includes life-cycle information, the version identifier is used to distinguish between the different versions of a spatial object. Within the set of all versions of a spatial object, the version identifier is unique.
-- Description --
NOTE The maximum length has been selected to allow for time stamps based on ISO 8601, for example, "2007-02-12T12:12:12+05:30" as the version identifier.
NOTE 2 The property is void, if the spatial data set does not distinguish between different versions of the spatial object. It is missing, if the spatial object type does not support any life-cycle information.
|
| geometry |
GM_MultiSurface |
|
Geometric representation spatially delineating the date and time of acquisition of the several input images that contribute to the final mosaic.
-- Description --
NOTE The boundaries of the geometries are commonly based on the seamlines used for the mosaicking process.
|
| phenomenonTime |
TM_Period |
|
Description of the observation/acquisition extent in time of the input image(s).
-- Description --
NOTE 1 This temporal extent refers to the interval of time in wich the input image(s) was/were acquired by the sensor.
NOTE 2 When the acquisition is considered as instantaneous, despite the exposure time, the end date and time can be identical to the begin date and time.
EXAMPLE 1 begin: 2011-10-30 end: 2011-10-30
EXAMPLE 2 begin: 2011-06-07T14:31:02Z end: 2011-06-07T16:10:54Z.
|
| imageSourceReference |
CharacterString |
|
Reference to the input image.
-- Description --
NOTE 1 There is no restriction on the nature of the input image. It can be raw or pre-processed or orthorectified, for instance.
NOTE 2 modelling and delivery of input images lie outside the scope of the present specification.
NOTE 3 Identifiers of the input images should be URIs in the “http” scheme (See D2.7) though full national or local codes are allowed.
EXAMPLE: http://land.data.gov.uk/id/imagery/2011-5864726.
|