| Name |
Type |
English |
Description |
| geographicalName |
GeographicalName
(datatype)
|
|
A geographical name that is used to identify the transport network object in the real world. It provides a 'key' for implicitly associating different representations of the object.
|
| - language |
CharacterString |
|
Language of the name, given as a three letters code, in accordance with either ISO 639-3 or ISO 639-5.
-- Description --
NOTE 1More precisely, this definition refers to the language used by the community that uses the name.
NOTE 2 The code "mul" for "multilingual" should not be used in general. However it can be used in rare cases like official names composed of two names in different languages. For example, "Vitoria-Gasteiz" is such a multilingual official name in Spain.
NOTE 3 Even if this attribute is "voidable" for pragmatic reasons, it is of first importance in several use cases in the multi-language context of Europe.
|
| - nativeness |
NativenessValue
(kodeliste)
|
|
Information enabling to acknowledge if the name is the one that is/was used in the area where the spatial object is situated at the instant when the name is/was in use.
|
| - nameStatus |
NameStatusValue
(kodeliste)
|
|
Qualitative information enabling to discern which credit should be given to the name with respect to its standardisation and/or its topicality.
-- Description --
NOTE The Geographical Names application schema does not explicitly make a preference between different names (e.g. official endonyms) of a specific real world entity. The necessary information for making the preference (e.g. the linguistic status of the administrative or geographic area in question), for a certain use case, must be obtained from other data or information sources. For example, the status of the language of the name may be known through queries on the geometries of named places against the geometry of administrative units recorded in a certain source with the language statuses information. |
| - sourceOfName |
CharacterString |
|
Original data source from which the geographical name is taken from and integrated in the data set providing/publishing it. For some named spatial objects it might refer again to the publishing data set if no other information is available.
-- Description --
EXAMPLES Gazetteer, geographical names data set.
|
| - pronunciation |
PronunciationOfName
(datatype)
|
|
Proper, correct or standard (standard within the linguistic community concerned) pronunciation of the geographical name.
-- Description --
SOURCE Adapted from [UNGEGN Manual 2006].
|
| - spelling |
SpellingOfName
(datatype)
|
|
A proper way of writing the geographical name.
-- Description --
NOTE 1 Different spellings should only be used for names rendered in different scripts. .
NOTE 2 While a particular GeographicalName should only have one spelling in a given script, providing different spellings in the same script should be done through the provision of different geographical names associated with the same named place.
|
| - grammaticalGender |
GrammaticalGenderValue
(kodeliste)
|
|
Class of nouns reflected in the behaviour of associated words.
-- Description --
NOTE the attribute has cardinality [0..1] and is voidable, which means that:
<ul>
<li>in case the concept of grammatical gender has no sense for a given name (i.e. the attribute is not applicable), the attribute should not be provided.</li>
<li>in case the concept of grammatical gender has some sense for the name but is unknown, the attribute should be provided but <i>void</i>. </li>
</ul>
|
| - grammaticalNumber |
GrammaticalNumberValue
(kodeliste)
|
|
Grammatical category of nouns that expresses count distinctions.
-- Description --
NOTE the attribute has cardinality [0..1] and is voidable, which means that:
<ul>
<li>in case the concept of grammatical number has no sense for a given name (i.e. the attribute is not applicable), the attribute should not be provided.</li>
<li>in case the concept of grammatical number has some sense for the name but is unknown, the attribute should be provided but <i>void</i>.</li>
</ul>
|
| beginLifespanVersion |
DateTime |
|
Date and time at which this version of the spatial object was inserted or changed in the spatial data set.
|
| inspireId |
Identifier
(datatype)
|
|
External object identifier of the spatial object.
-- Description --
NOTE 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.
|
| - 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.
|
| endLifespanVersion |
DateTime |
|
Date and time at which this version of the spatial object was superseded or retired in the spatial data set.
|
| geometry |
GM_Point |
|
The location of the transport point. |
| validFrom |
DateTime |
|
The time when the transport point started to exist in the real world. |
| validTo |
DateTime |
|
The time from which the transport point no longer exists in the real world. |