Feature Catalogue'INSPIRE application schemas'

Definition:

-- Name --

activity complex

-- Definition --

A "single unit", both technically and economically, under the management control of the same legal entity (operator), covering activities as those listed in the Eurostat NACE classification, products and services. Activity Complex includes all infrastructure, equipment and materials. It must represent the whole area, at the same or different geographical location, managed by a "single unit".

-- Description --

NOTE 1 This class describes the minimal set of elements necessary to describe and identify geographically a legal entity and the activities taken place on it under the context of a Environmental purposes.

NOTE 2 "Activity Complex" could be assimilated to terms described on the legislation as Facility, Establishment, Plant, Holding, Organization ,Farm, Extractive Industries or Aquaculture Production Business among others

EXAMPLE i.e. an Agro-business that is legally registered under the Emissions Directive.

Type:

Spatial Object Type

Name:

beginLifespanVersion

Definition:

-- Name --

begin lifespan version

-- Definition --

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

-- Description --

NOTE This date is recorded to enable the generation of change only update files.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

endLifespanVersion

Definition:

-- Name --

end lifespan version

-- Definition --

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

-- Description --

NOTE This date is recorded primarily for those systems which "close" an entry in the spatial data set in the event of an attribute change.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Name:

function

Definition:

-- Name --

function

-- Definition --

Activities performed by the activity complex. Function is described by the activity and potentially complemented with information about inputs and outputs as result of it.

-- Description --

NOTE The Activity described as part of the Function “Activity Complex” should be recorded using a controlled vocabulary where a particular controlled vocabulary is in use within a given context, such as SIC codes in the UK, it is acceptable to use these, however, the preferred choice for European interoperability is whenever possible NACE [NACE].

Voidable:

false

Multiplicity:

1..*

Value type:

Function (data type)

Name:

geometry

Definition:

-- Name --

geometry

-- Definition --

The geometry used to define the extent or position of the “Activity Complex”.

-- Description --

NOTE 1 Based on the provided description, different geometries could be used to represent the Activity Complex as a one legal whole.

EXAMPLE 1 E-prtr geometry is given by a single point based on Geographical Coordinates (see below). In other levels of detail or depending on the Data Provider this could be represented [e.g.] by a Multi-poligon.

EXAMPLE 2 PRTR - Legal act example: “ … the latitude and longitude coordinates within an arc of 5 minutes that avoid the direct identification of an individual holding….”.

Voidable:

false

Multiplicity:

1

Value type:

GM_Object

Name:

inspireId

Definition:

-- Name --

INSPIRE identifier

-- Definition --

External object identifier of the “Activity Complex”.

-- 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.

Voidable:

false

Multiplicity:

1

Value type:

Identifier (data type)

Name:

name

Definition:

-- Name --

name

-- Definition --

Descriptive name of the “Activity Complex”.

-- Description --

NOTE 1 Several names in different languages may be expressed.

NOTE 2 It is recommended that the language of the name (part of the Geographical/Name data type) be filled whenever possible.

Voidable:

true

Multiplicity:

0..1

Value type:

CharacterString

Name:

thematicId

Definition:

-- Name --

thematic identifier

-- Definition --

Thematic Activity Complex identifier.

-- Description --

NOTE It may be the identification code provided or maintained by the Member States public authority to identify the object in the context of specific or general thematic scopes.

EXAMPLE Assigned National PRTR Code.

Voidable:

false

Multiplicity:

0..*

Value type:

ThematicIdentifier (data type)

Name:

validFrom

Definition:

-- Name --

valid from

-- Definition --

The time when the activity complex started to exist in the real world.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

validTo

Definition:

-- Name --

valid to

-- Definition --

The time when the activity complex no longer exists in the real world.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Definition:

-- Name --

activity complex description

-- Definition --

Additional information about an activity complex, including its description, address, contact and related parties.

Type:

Data type

Name:

address

Definition:

-- Name --

address

-- Definition --

An address for the activity complex, i.e., an address where the activities occur.

Voidable:

true

Multiplicity:

0..1

Value type:

AddressRepresentation (data type)

Name:

contact

Definition:

-- Name --

contact

-- Definition --

Contact information for the activity complex.

Voidable:

true

Multiplicity:

0..1

Value type:

Contact (data type)

Name:

description

Definition:

-- Name --

description

-- Definition --

A complementary definition of the “Activity Complex” and its characteristics.

-- Description --

NOTE Free text to include or refer any complementary information about the Activity Complex or its characteristics.

Voidable:

true

Multiplicity:

0..1

Value type:

PT_FreeText

Name:

relatedParty

Definition:

-- Name --

related party

-- Definition --

Information on Parties related to the Activity Complex. It is open to many different roles, such as owners, operators or Competent Authorities.

-- Description --

NOTE 1 The term covers concepts described on the legislation such as Operator, Company, Port Authority, Agent, Holder, Collector, Producer, Competent Authority or Keeper.

Voidable:

true

Multiplicity:

0..*

Value type:

RelatedParty (data type)

Definition:

-- Name --

capacity

-- Definition --

A quantification of an actual or potential ability to perform an activity, that typically does not change, does not change often, or does not change to a significant degree.

-- Description --

NOTE Capacity could refer depending of the thematic scope to different concepts included on the legislation as “emission limits”, “capacity incineration”, “livestock units”, “nominal capacity”, “objective estimation data”, “rate of desulphurization” or “recycling rate”.

Type:

Data type

Name:

activity

Definition:

-- Name --

activity

-- Definition --

Categorized description of individual or organized set of technically related processes that are carried out by a economical unit, private or public, profit or non profit character.

-- Description --

NOTE The Activity described as part of the Function for “Activity Complex” should be recorded using a controlled vocabulary where a particular controlled vocabulary is in use within a given context, such as SIC codes in the UK, it is acceptable to use these, however, the preferred choice for European interoperability is whenever possible NACE [NACE].

Voidable:

false

Multiplicity:

1..*

Value type:

EconomicActivityValue (code list)

Tagged Values:

Name:

description

Definition:

-- Name --

description

-- Definition --

A description of the capacity.

Voidable:

true

Multiplicity:

0..1

Value type:

PT_FreeText

Name:

input

Definition:

-- Name --

input

-- Definition --

Measurable information about parameters related with the inputs related with the activity carried out by the Activity Complex.

-- Description --

NOTE Depending on the thematic scope it can contain different values including terms as Registered Pollutants, Waste, Processed Products, leakage, etc.

Voidable:

false

Multiplicity:

0..*

Value type:

InputOutputAmount (data type)

Name:

output

Definition:

-- Name --

output

-- Definition --

Measurable information about parameters related with the outputs derived from the activity carried out by the “Activity Complex”.

-- Description --

NOTE Depending on the thematic scope it can contain different values including terms as Registered Pollutants, Waste, Processed Products, leakage, etc.

Voidable:

false

Multiplicity:

0..*

Value type:

InputOutputAmount (data type)

Name:

time

Definition:

-- Name --

time

-- Definition --

The duration of time to which the specified capacity refers, such as 1 year for an annual capacity.

-- Description --

NOTE Total capacities are specified without duration of time.

Voidable:

false

Multiplicity:

0..1

Value type:

Time

Definition:

-- Name --

function

-- Definition --

The function of something expressed as an activity and optional input and/or output.

-- Description --

NOTE Depending on the scope it can refer to different activities (co-incineration, Collection, exploration, incineration, interim disposal, management, recycling, primary production, primary treatment, recovery , recycling, release, storage, use, waste management, etc) and Inputs and Outputs (sludge, substance, tailings, technical products, urban waste water, volatile organic compound, waste, WEEE from private households, etc).

Type:

Data type

Name:

activity

Definition:

-- Name --

activity

-- Definition --

Categorized description of individual or organized set of technically related processes that are carried out by a economical unit, private or public, profit or non profit character.

-- Description --

NOTE The Activity described as part of the Function for “Activity Complex” should be recorded using a controlled vocabulary where a particular controlled vocabulary is in use within a given context, such as SIC codes in the UK, it is acceptable to use these, however, the preferred choice for European interoperability is whenever possible NACE [NACE].

Voidable:

false

Multiplicity:

1..*

Value type:

EconomicActivityValue (code list)

Tagged Values:

Name:

description

Definition:

-- Name --

description

-- Definition --

A more detailed description of the function.

Voidable:

true

Multiplicity:

0..1

Value type:

PT_FreeText

Name:

input

Definition:

-- Name --

input

-- Definition --

A classified or registered type of material or something immaterial, that enters a technical and economical unit according to its function.

-- Description --

NOTE Depending on the thematic scope it can contain different values including terms as Biomass, Bio-Waste, Fuel, Organic Solvents, Waste Water, Waste for disposal or recovery, Primary Materials, ..

Voidable:

true

Multiplicity:

0..*

Value type:

InputOutputValue (code list)

Tagged Values:

Name:

output

Definition:

-- Name --

output

-- Definition --

A classified or registered type of material or something immaterial, that leaves a technical and economical unit according to its function, ".

-- Description --

NOTE Depending on the thematic scope it can contain different values including terms as Registered Pollutants, Waste, Processed Products, leakage, etc.

Voidable:

true

Multiplicity:

0..*

Value type:

InputOutputValue (code list)

Tagged Values:

Definition:

-- Name --

amount of input or output

-- Definition --

Type and, where available, measurable amount of a classified or registered material that enters or leaves a technical and economical unit.

-- Description --

NOTE Depending on the thematic scope it can refer to different terms as Biomass, Bio-Waste, Fuel, Organic Solvents, Waste Water, Waste for disposal or recovery, Primary Materials, etc.

Type:

Data type

Name:

amount

Definition:

-- Name --

amount

-- Definition --

The amount (such as a volume or mass) of the classified or registered material that enters or leaves a technical and economical unit.

Voidable:

true

Multiplicity:

1

Value type:

Measure

Name:

inputOutput

Definition:

-- Name --

input/output

-- Definition --

A classified or registered type of material or something immaterial, that enters a technical and economical unit according to its function.

-- Description --

NOTE Depending on the thematic scope it can contain different values including terms as Biomass, Bio-Waste, Fuel, Organic Solvents, Waste Water, Waste for disposal or recovery, Primary Materials, etc.

Voidable:

false

Multiplicity:

1

Value type:

InputOutputValue (code list)

Tagged Values:

Definition:

-- Name --

permission

-- Definition --

Official Decision (formal consent) granting authorization to operate all or part of an Activity Complex, subject to certain conditions which guarantee that the installations or parts of installations on the same site operated by the same operator comply with the requirements fixed by a competent authority. A permit may cover one or more functions and fix parameters of capacity. The term could be extended to other kind of certificates or documents of special relevance depending of the scope (e.g. ISO, EMAS, National Quality Standards, etc).

The term may be extended to other kind of certificates or documents of special relevance depending of the scope (e.g. ISO, EMAS, National Quality Standards, etc).

-- Description --

NOTE This terms is referred in several legislative acts as “permit” , “authorization”, “development consent” or “exploration permit” among others.

EXAMPLE 1 “…a [written] decision by which the competent authority grants permission to operate all or part of an installation” ;

EXAMPLE 2 “.. the decision of the competent authority or authorities which entitles the developer to proceed with the project..”.

Type:

Data type

Name:

Id

Definition:

-- Name --

identifier

-- Definition --

Identifying reference to the permission.

Voidable:

false

Multiplicity:

0..*

Value type:

ThematicIdentifier (data type)

Name:

dateFrom

Definition:

-- Name --

date from

-- Definition --

A date starting from which the permission applies and is valid.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

dateTo

Definition:

-- Name --

date to

-- Definition --

A date up to which the permission applies and is valid.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Name:

decisionDate

Definition:

-- Name --

decision date

-- Definition --

Temporal reference that complement the definition of the permission.

-- Description --

NOTE For permissions that become effective immediately, the decision date and the start of the validity period coincide. It may however be a duration of years or decades that separates a decision date from the validity period. For example, a permission decided in 2012 may allow the recovery of waste at a particular site starting from the year

EXAMPLE Legal resolutions used to refer to a specific day from which the referred resolution and the emitted permission starts to be valid.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

description

Definition:

-- Name --

description

-- Definition --

A description of the permission.

Voidable:

true

Multiplicity:

0..1

Value type:

PT_FreeText

Name:

permittedCapacity

Definition:

-- Name --

permitted capacity

-- Definition --

Maximum amounts of activity input and/or output according to the permission,

-- Description --

NOTE The physical capacities of a facility may exceed the permitted capacities.

EXAMPLE Incineration of at most 100000 tons of residual waste per year.

Voidable:

true

Multiplicity:

0..*

Value type:

Capacity (data type)

Name:

permittedFunction

Definition:

-- Name --

permitted function

-- Definition --

Function/s for which the permission is granted. Function is as described by the Activity and potentially complemented by information about the Inputs and Outputs derived from the same.

-- Description --

NOTE Functions permitted according to the permission, such as a permit for a landfill.

Voidable:

true

Multiplicity:

0..*

Value type:

Function (data type)

Name:

relatedParty

Definition:

-- Name --

related party

-- Definition --

Parties related to the permission granted to the activity complex open to many different roles, such as Competent Authorities or Company among others

-- Description --

NOTE Include concepts described on the legislation such as Operator, Company, Port Authority, Agent, Holder, Competent Authority or Keeper.

Voidable:

true

Multiplicity:

0..*

Value type:

RelatedParty (data type)

Definition:

-- Definition --

An identification of the fixed location of property by means of a structured composition of geographic names and identifiers.

-- Description --

NOTE 1 The spatial object, referenced by the address, is defined as the "addressable object". The addressable object is not within the application schema, but it is possible to represent the address' reference to a cadastral parcel or a building through associations. It should, however, be noted that in different countries and regions, different traditions and/or regulations determine which object types should be regarded as addressable objects.

NOTE 2 In most situations the addressable objects are current, real world objects. However, addresses may also reference objects which are planned, under construction or even historical.

NOTE 3 Apart from the identification of the addressable objects (like e.g. buildings), addresses are very often used by a large number of other applications to identify object types e.g. statistics of the citizens living in the building, for taxation of the business entities that occupy the building, and the utility installations.

NOTE 4 For different purposes, the identification of an address can be represented in different ways (see example 3).

EXAMPLE 1 A property can e.g., be a plot of land, building, part of building, way of access or other construction,

EXAMPLE 2 In the Netherlands the primary addressable objects are buildings and dwellings which may include parts of buildings, mooring places or places for the permanent placement of trailers (mobile homes), in the UK it is the lowest level of unit for the delivery of services, in the Czech Republic it is buildings and entrance doors.

EXAMPLE 3 Addresses can be represented differently. In a human readable form an address in Spain and an address in Denmark could be represented like this: "Calle Mayor, 13, Cortijo del Marqués, 41037 Écija, Sevilla, España" or "Wildersgade 60A, st. th, 1408 Copenhagen K., Denmark".

Type:

Spatial Object Type

Name:

alternativeIdentifier

Definition:

-- Definition --

External, thematic identifier of the address spatial object, which enables interoperability with existing legacy systems or applications.

-- Description --

NOTE 1 Compared with the proper identifier of the address, the alternative identifier is not necessarily persistent in the lifetime of the address spatial object. Likewise it is usually not globally unique and in general does not include information on the version of the address spatial object.

NOTE 2 Often alternative address identifiers are composed by a set of codes that, e.g., identify the region and the municipality, the thoroughfare name and the address number. These alternative identifiers will not remain persistent e.g. in the case of the merging of two municipalities.

EXAMPLE In Denmark many legacy systems (e.g. in the Statistics Denmark or the Central Business Register) uses as address identification the three digit municipality code plus the four character street name code plus the address number.

Voidable:

true

Multiplicity:

0..1

Value type:

CharacterString

Name:

beginLifespanVersion

Definition:

-- Definition --

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

-- Description --

NOTE This date is recorded to enable the generation of change only update files.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

building

Definition:

-- Name --

building

-- Definition --

Building that the address is assigned to or associated with.

-- Description --

NOTE An address could potentially have an association to zero, one or several buildings. Also it is possible (but this is not expressed in this application schema) that several addresses are associated to a single building.

EXAMPLE In Praha, The Czech Republic, the address designated "NaPankráci 1690/125" is associated to a specific building in the street, in this case the building with number 1690 in the district (cz: cast obce) "Nusle".

Voidable:

true

Multiplicity:

0..*

Value type:

AbstractConstruction (spatial object type)

Name:

component

Definition:

-- Definition --

Represents that the address component is engaged as a part of the address.

-- Description --

EXAMPLE For the address designated "Calle Mayor 13, Cortijo del Marqués, 41037, Écija, Sevilla, España" the six address components "Calle Mayor", "Cortijo del Marqués", "41037", "Écija", "Sevilla" and "España" are engaged as address components.

Voidable:

false

Multiplicity:

1..*

Value type:

AddressComponent (spatial object type)

Name:

endLifespanVersion

Definition:

-- Definition --

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

-- Description --

NOTE This date is recorded primarily for those systems which "close" an entry in the spatial data set in the event of an attribute change.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Name:

inspireId

Definition:

-- Definition --

External object identifier of the address.

-- 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 addressable object.

NOTE 2 The primary purpose of this identifier is to enable links between various sources and the address components.

EXAMPLE An address spatial object from Denmark could carry this identifier:

Namespace: DK_ADR

Local identifier: 0A3F507B2AB032B8E0440003BA298018

Version identifier: 12-02-2008T10:05:01+01:00

Voidable:

false

Multiplicity:

1

Value type:

Identifier (data type)

Name:

locator

Definition:

-- Definition --

Human readable designator or name.

Voidable:

false

Multiplicity:

1..*

Value type:

AddressLocator (data type)

Name:

parcel

Definition:

-- Definition --

Cadastral parcel that this address is assigned to or associated with.

-- Description --

NOTE An address could potentially have an association to zero, one or several cadastral parcels. Also it is possible (but this is not expressed in this application schema) that several addresses are associated to a single cadastral parcel.

EXAMPLE In the street "Wildersgade" in Copenhagen, Denmark, the address designated as "Wildersgade 66, 1408 København K" is associated to the cadastral parcel identifier "81" in the district of "Christianshavn".

Voidable:

true

Multiplicity:

0..*

Value type:

CadastralParcel (spatial object type)

Name:

parentAddress

Definition:

-- Definition --

The main (parent) address with which this (sub) address is tightly connected.

-- Description --

NOTE 1 The relationship between a set of subaddresses and the main address most often means that the sub addresses use the same locator and address components (for example , thoroughfare name, address area, post code) as the parent address. For each sub address additional address locators are then included for identification, like e.g. flat number, floor identifier, door number.

NOTE 2 In some countries several levels of parent-, sub- and sub-sub-addresses exist. In other countries the concept of parent addresses does not exist; all addresses are thus of the same level.

EXAMPLE 1 In a Spanish city the address "Calle Gran Vía 8" is a parent address where the locator "8" represents the building. In the building, the sub address "Calle Gran Via 8, door 3" represents a sub-address, while the more detailed sub-sub address "Calle Gran Via 8, door 3, staircase A, floor 5, dwelling 1" represents the address of a specific dwelling.

EXAMPLE 2 In Denmark the legislation on addresses define two types of addresses: the parent "access level" and the sub "unit level". In the city of Copenhagen "Wildersgade 60A" is a parent access address that represents a specific entrance to a building. Inside the entrance, subaddresses using floor and door designators identifies the individual dwellings like e.g. "Wildersgade 60A, 1st floor, left door".

EXAMPLE 3 In The Netherlands only one level of addresses exists.

Voidable:

true

Multiplicity:

0..1

Value type:

Address (spatial object type)

Name:

position

Definition:

-- Definition --

Position of a characteristic point which represents the location of the address according to a certain specification, including information on the origin of the position.

Voidable:

false

Multiplicity:

1..*

Value type:

GeographicPosition (data type)

Name:

status

Definition:

-- Definition --

Validity of the address within the life-cycle (version) of the address spatial object.

-- Description --

NOTE This status relates to the address and is not a property of the object to which the address is assigned (the addressable object).

Voidable:

true

Multiplicity:

0..1

Value type:

StatusValue (code list)

Values:

Name:

validFrom

Definition:

-- Definition --

Date and time of which this version of the address was or will be valid in the real world.

-- Description --

NOTE This date and time can be set in the future for situations where an address or a version of an address has been decided by the appropriate authority to take effect for a future date.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

validTo

Definition:

-- Definition --

Date and time at which this version of the address ceased or will cease to exist in the real world.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Name:

AddressCountry

Expression:

/* An address shall have an admin unit address component spatial object whose level is 1 (Country) */ inv: self.component -> forAll (a1 | exists(a1.parent.oclIsTypeOf(AdminUnitName) and a1.parent.level=1))

Name:

AddressPosition

Expression:

/* An address shall have exactly one default geographic position (default attribute of GeographicPosition must be true) */ inv: self.position -> one(a1 | a1.default = true)

Name:

EndLifeSpanVersion

Expression:

/* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */ inv: self.endLifespanVersion.isAfter(self.beginLifespanVersion)

Definition:

-- Definition --

An address component which represents the name of a geographic area or locality that groups a number of addressable objects for addressing purposes, without being an administrative unit.

-- Description --

NOTE 1 In some countries and regions an address area is a true subdivision of an administrative unit (most often a municipality), so that every address area is fully inside the municipality and so that every part of the municipality is within an address area. In other countries, the concept of address area names is less strict and based on local tradition or specific needs.

NOTE 2 In some situations an address area name is not required to obtain unambiguousness; instead the purpose is to make the complete address more informative and descriptive, adding a well known place name (e.g. of a village or community) to the address. This is particularly useful if the municipality or post code covers a large area.

EXAMPLE 1 In Sweden a "Kommundel" (en: Municipal sub division) is a type of address area names that ensures that street names are unique within the sub division.

EXAMPLE 2 In Spain an "Entidad de población" (en: population entity) has the same function. It is the general address area which depending on its characteristics can be classified as "Entidad Singular" (en: singular entity) or "Entidad Colectiva" (en: collective entity). Moreover, according to the population distribution, these areas can contain one or several "Núcleo de población" (en: population core) and/or "Población diseminada" (en: scattered population).

EXAMPLE 3 In Denmark "Supplerende bynavn" (en: Supplementary town name) is sometimes compulsory to ensure uniqueness of street names within the post code, sometimes it is just useful extra information, that makes the address more informative.

Subtype of:

AddressComponent

Type:

Spatial Object Type

Name:

name

Definition:

-- Definition --

Proper noun applied to the address area.

-- Description --

NOTE The data type allows names in different languages and scripts as well as inclusion of alternative name, alternative spellings, historical name and exonyms.

Voidable:

false

Multiplicity:

1..*

Value type:

GeographicalName (data type)

Name:

namedPlace

Definition:

-- Definition --

The named place that this address area name represents.

-- Description --

NOTE In order to populate this association, it is important that the area covered by the identified Named Place is exactly the same as the area covered by the address area name in question; if this is not the case the association would result in an inconsistency.

EXAMPLE The geographical name "Huskvarna", which represents a part of the municipality of Jönköping in Sweden, is the source of the address area name, "Huskvarna".

Voidable:

true

Multiplicity:

0..1

Value type:

NamedPlace (spatial object type)

Name:

EndLifeSpanVersion

Expression:

/* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */ inv: self.endLifespanVersion .isAfter(self.beginLifespanVersion)

Definition:

-- Definition --

Identifier or geographic name of a specific geographic area, location, or other spatial object which defines the scope of an address.

-- Description --

NOTE 1 Four different subclasses of address components are defined:

o Administrative unit name, which may include name of country, name of municipality, name of district

o Address area name like e.g. name of village or settlement

o Thoroughfare name, most often road name

o Postal descriptor

In order to construct an address, these subclasses are often structured hierarchically.

NOTE 2 It is the combination of the address locator and the address components, which makes a specific address spatial object readable and unambiguous for the human user.

EXAMPLE The combination of the locator "13" and the address components "Calle Mayor" (thoroughfare name), "Cortijo del Marqués" (address area name), "41037" (postal descriptor), "Écija", "Sevilla" and "España" (administrative unit names) makes this specific address spatial object readable and unambiguous.

Type:

Spatial Object Type

Abstract:

true

Name:

alternativeIdentifier

Definition:

-- Definition --

External, thematic identifier of the address component spatial object, which enables interoperability with existing legacy systems or applications.

-- Description --

NOTE Compared with a proper identifier of the address component, the alternative identifier is not necessarily persistent in the lifetime of the component spatial object. Likewise it is usually not globally unique and in general does include information on the version of the spatial object.

EXAMPLE 1 National or regional sector-specific identifiers (like e.g. a number- or letter code) for administrative units, address areas (localities, villages, sub-divisions) or thoroughfare names, which are used by a number of existing legacy systems.

EXAMPLE 2 In Denmark the four character municipal "road name code" (0001-9899) is only unique within the present municipality, thus if two municipalities merge, it is necessary to assign new road name codes.

Voidable:

true

Multiplicity:

0..1

Value type:

CharacterString

Name:

beginLifespanVersion

Definition:

-- Definition --

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

-- Description --

NOTE This date is recorded to enable the generation of change only update files.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

endLifespanVersion

Definition:

-- Definition --

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

-- Description --

NOTE This date is recorded primarily for those systems which "close" an entry in the spatial data set in the event of an attribute change.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Name:

inspireId

Definition:

-- Definition --

External object identifier of the address component.

-- 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 The primary purpose of this identifier is to enable links between various sources and the address components.

EXAMPLE An address component spatial object from Denmark could carry this identifier:

Namespace: DK_ADR

Local identifier: 0A3F507B2AB032B8E0440003BA298018

Version identifier: 12-02-2008T10:05:01+01:00

Voidable:

false

Multiplicity:

0..1

Value type:

Identifier (data type)

Name:

situatedWithin

Definition:

-- Definition --

Another address component within which the geographic feature represented by this address component is situated.

-- Description --

NOTE 1 The association enables the application schema to express that the subtypes of address components in the dataset form a hierarchy e.g. like: thoroughfare name within municipality within region within country

NOTE 2 The representation of the hierarchy facilitates queries e.g. for a specific thoroughfare name within a given municipality or postcode. It is also necessary where the application schema is used to create or update, for example , a gazetteer which is based on the hierarchical structure of the address components.

NOTE 3 The multiplicity of the association allows it to express that a thoroughfare name is situated in a certain municipality and in a certain postcode. It is also possible to express, for example, that some thoroughfare names cross borders between municipalities and thus is situated within more than one municipality.

EXAMPLE 1 In Spain many spatial objects of the thoroughfare name "Calle Santiago" exist. The association can express that one of the spatial objects is situated within in the municipality of Albacete. From the same example the municipality name "Albacete" is situated within the administrative name (region) of "Castilla La Mancha".

EXAMPLE 2 In Denmark, several address area names entitled "Strandby" exists. In order to identify a specific spatial object it is necessary to know that the relevant spatial object is situated e.g. in the municipality of "Frederikshavn".

Voidable:

true

Multiplicity:

0..*

Value type:

AddressComponent (spatial object type)

Name:

status

Definition:

-- Definition --

Validity of the address component within the life-cycle (version) of the address component spatial object.

-- Description --

NOTE This status relates to the address component and is not a property of the object to which the address is assigned (the addressable object).

Voidable:

true

Multiplicity:

0..1

Value type:

StatusValue (code list)

Values:

Name:

validFrom

Definition:

-- Definition --

Date and time of which this version of the address component was or will be valid in the real world.

-- Description --

NOTE This date and time can be set in the future for situations where an address component or a version of an address component has been decided by the appropriate authority to take effect for a future date.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

validTo

Definition:

-- Definition --

Date and time at which the address component ceased or will cease to exist in the real world.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Name:

EndLifeSpanVersion

Expression:

/* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */ inv: self.endLifespanVersion .isAfter(self.beginLifespanVersion)

Definition:

-- Definition --

Human readable designator or name that allows a user or application to reference and distinguish the address from neighbour addresses, within the scope of a thoroughfare name, address area name, administrative unit name or postal designator, in which the address is situated.

-- Description --

NOTE 1 The most common locators are designators like an address number, building number or flat identifier as well as the name of the property, complex or building.

NOTE 2 The locator identifier(s) are most often only unambiguous and meaningful within the scope of the adjacent thoroughfare name, address area name or post code.

NOTE 3 The locator could be composed of one or more designators e.g., address number, address number suffix, building number or name, floor number, flat or room identifier. In addition to these common locator types, also narrative or descriptive locators are possible.

NOTE 4 The locators of an address could be composed as a hierarchy, where one level of locators identifies the real property or building while another level of locators identifies the flats or dwellings inside the property.

EXAMPLE 1 In a Spanish city a "site-level" locator could identify a building on the thoroughfare name "Calle Gran Vía using the address number "8". If the building has four entrance doors, the door number "3" could be the "access-level" locator. The 3rd door could, via two staircases "A" and "B", give access to a number of floors, identified by a number "1" to "5" on which a number of dwellings are situated, also identified by numbers "1" to "3"; The "unit level" locator will thus composed of staircase-, floor- and dwelling identification e.g. "staircase A, floor 5, dwelling 1". In total, the three parent-child levels of locators uniquely identify the dwelling.

EXAMPLE 2 In Copenhagen an "access level" locator could identify a specific entrance door in a building on the thoroughfare name "Wildersgade" using the address number "60A" (In Denmark the optional suffix is a part of the address number). The entrance door gives access to a number of floors, e.g, "st", "1", "2", "3", on which two dwellings are situated "tv" and "th". The "unit level" locator will thus be composed by a floor- and a door identifier: "2. th." (2nd floor, door to the right). In total, the two parent-child levels of locators uniquely identify the dwelling.

EXAMPLE 3 In The Netherlands only one level of locators exists. The individual apartment within a large complex, a dwelling, a part of other kinds of buildings (for example an office), a mooring place or a place for the permanent placing of trailers are addressable objects which must have an address. This address is the only level of the locator. This locator could be composed by three attributes the house number, plus optionally an additional house letter, plus optionally an additional housenumber suffix.

EXAMPLE 4 Sometimes the building name is an alternative identifier to the address number e.g. the house located in "Calle Santiago, 15, Elizondo-Baztán, Navarra, Spain" is also identified by the building name "Urtekoetxea"

Type:

Data type

Name:

designator

Definition:

-- Definition --

A number or a sequence of characters that uniquely identifies the locator within the relevant scope(s).

Voidable:

false

Multiplicity:

0..*

Value type:

LocatorDesignator (data type)

Name:

level

Definition:

-- Definition --

The level to which the locator refers.

Voidable:

false

Multiplicity:

1

Value type:

LocatorLevelValue (code list)

Values:

Name:

name

Definition:

-- Definition --

A geographic name or descriptive text associated to a property identified by the locator.

-- Description --

NOTE 1 The locator name could be the name of the property or complex (e.g. an estate, hospital or a shopping mall), of the building or part of the building (e.g. a wing), or it could be the name of a room inside the building.

NOTE 2 As locator name it is also possible to use a description that allows a user to identify the property in question.

NOTE 3 The locator name could be an alternative addition to the locator designator (e.g. the address number) or it could be an independent identifier.

EXAMPLE In the address "Calle Santiago, 15, Elizondo-Baztán, Navarra, Spain" the building name "Urtekoetxea" is an alternative to the building identifier "3".

Voidable:

false

Multiplicity:

0..*

Value type:

LocatorName (data type)

Name:

withinScopeOf

Definition:

-- Definition --

The address component that defines the scope within which the address locator is assigned according to rules ensuring unambiguousness.

-- Description --

NOTE 1 For the assignment of unambiguous locators (e.g. address numbers) different rules exists in different countries and regions. According to the most common rule, an address number should be unique within the scope of the thoroughfare name. In other areas the address number is unique inside an address area name (e.g. the name of the village) or postal designator (e.g. the post code). In some areas even a combination of rules are applied: e.g. addresses with two locators, each of them referencing to a separate address component.

NOTE 2 Locators that has the level of unit (like e.g. floor identifier and door or unit identifiers) are most often assigned so that they are unambiguous within the more narrow scope of the property or building; for these locators the association should therefore not be populated.

EXAMPLE 1 In a typical European address dataset, parts of the addresses have locators which are unambiguous within the scope of the road name (thoroughfare name) while others are unambiguous within the name ogf the village or district (address area name).

EXAMPLE 2 In Lithuania and Estonia a concept of "corner addresses" exists. Corner addresses have two address numbers (designators) each of them referring to a thoroughfare name (primary and secondary street name). E.g. in Vilnius the address designated "A. Stulginskio gatve 4 / A. Smetonos gatve 7" is situated on the corner of the two streets.

EXAMPLE 3 In the Czech Republic in some cities an address has two locator designators: A building number which referres to the address area (district, cz: "cast obce") and a address number that referres to the thoroughfare name. As an example in Praha for address designated "Na Pankráci 1690/125, Nusle" the designator "1690" is a building number unique within the address area (cz cast obce) "Nusle", while the "125" is an address number that has the thoroughfare name as its scope.

Voidable:

true

Multiplicity:

0..1

Value type:

AddressComponent (spatial object type)

Name:

DesignatorEmpty

Description:

If no designator exists, a name is required.

Expression:

inv: self.designator->isEmpty() implies self.name->notEmpty()

Name:

NameEmpty

Description:

If no name exists, a designator is required.

Expression:

inv: self.name->isEmpty() implies self.designator->notEmpty()

Definition:

-- Definition --

Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.

-- Description --

NOTE 1 The data type includes the all necessary readable address components as well as the address locator(s), which allows the identification of the address spatial objects, e.g., country, region, municipality, address area, post code, street name and address number. It also includes an optional reference to the full address spatial object.

NOTE 2 The datatype could be used in application schemas that wish to include address information e.g. in a dataset that registers buildings or properties.

Type:

Data type

Name:

addressArea

Definition:

-- Definition --

The name or names of a geographic area or locality that groups a number of addressable objects for addressing purposes, without being an administrative unit.

Voidable:

true

Multiplicity:

0..*

Value type:

GeographicalName (data type)

Name:

addressFeature

Definition:

-- Definition --

Reference to the address spatial object.

Voidable:

true

Multiplicity:

0..1

Value type:

Address (spatial object type)

Name:

adminUnit

Definition:

-- Definition --

The name or names of a unit of administration where a Member State has and/or exercises jurisdictional rights, for local, regional and national governance.

Voidable:

false

Multiplicity:

1..*

Value type:

GeographicalName (data type)

Name:

locatorDesignator

Definition:

-- Definition --

A number or a sequence of characters which allows a user or an application to interpret, parse and format the locator within the relevant scope. A locator may include more locator designators.

Voidable:

false

Multiplicity:

0..*

Value type:

CharacterString

Name:

locatorName

Definition:

-- Definition --

Proper noun(s) applied to the real world entity identified by the locator.

Voidable:

false

Multiplicity:

0..*

Value type:

GeographicalName (data type)

Name:

postCode

Definition:

-- Definition --

A code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.

Voidable:

true

Multiplicity:

0..1

Value type:

CharacterString

Name:

postName

Definition:

-- Definition --

One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.

Voidable:

true

Multiplicity:

0..*

Value type:

GeographicalName (data type)

Name:

thoroughfare

Definition:

-- Definition --

The name or names of a passage or way through from one location to another like a road or a waterway.

Voidable:

true

Multiplicity:

0..*

Value type:

GeographicalName (data type)

Definition:

-- Definition --

An address component which represents the name of a unit of administration where a Member State has and/or exercises jurisdictional rights, for local, regional and national governance.

Subtype of:

AddressComponent

Type:

Spatial Object Type

Name:

adminUnit

Definition:

-- Definition --

The administrative unit that is the source of the content of the administrative unit name.

-- Description --

EXAMPLE The administrative unit (municipality) "Gävle" in Sweden is the source of the address component administrative unit name, "Gävle".

Voidable:

true

Multiplicity:

1

Value type:

AdministrativeUnit (spatial object type)

Name:

level

Definition:

-- Definition --

The level of administration in the national administrative hierarchy.

Voidable:

false

Multiplicity:

1

Value type:

AdministrativeHierarchyLevel (code list)

Values:

Name:

name

Definition:

-- Definition --

Official, geographical name of the administrative unit, given in different languages where required.

-- Description --

NOTE The data type allows names in different languages and scripts as well as inclusion of alternative name, alternative spellings, historical name and exonyms.

Voidable:

false

Multiplicity:

1..*

Value type:

GeographicalName (data type)

Name:

EndLifeSpanVersion

Expression:

/* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */ inv: self.endLifespanVersion .isAfter(self.beginLifespanVersion)

Definition:

-- Definition --

The position of a characteristic point which represents the location of the address according to a certain specification, including information on the origin of the position.

Type:

Data type

Name:

default

Definition:

-- Definition --

Specifies whether or not this position should be considered as the default.

-- Description --

NOTE As a member state may provide several positions of an address, there is a need to identify the commonly used (main) position. Preferrably, the default position should be the one with best accuracy.

Voidable:

false

Multiplicity:

1

Value type:

Boolean

Name:

geometry

Definition:

-- Definition --

The position of the point expressed in coordinates in the chosen spatial reference system.

Voidable:

false

Multiplicity:

1

Value type:

GM_Point

Name:

method

Definition:

-- Definition --

Description of how and by whom the geographic position of the address was created or derived.

-- Description --

NOTE The geographic position could be created manually by the address authority itself, by an independent party (e.g. by field surveying or digitizing of paper maps) or it could be derived automatically from the addressable object or from other Inspire features.

Voidable:

true

Multiplicity:

1

Value type:

GeometryMethodValue (code list)

Values:

Name:

specification

Definition:

-- Definition --

Information defining the specification used to create or derive this geographic position of the address.

Voidable:

true

Multiplicity:

1

Value type:

GeometrySpecificationValue (code list)

Values:

Definition:

-- Definition --

A number or a sequence of characters that uniquely identifies the locator within the relevant scope(s). The full identification of the locator could include one or more locator designators.

-- Description --

NOTE 1 Locator designators are often assigned according to a set of commonly known rules which enables a user or application to "parse" the information: Address numbers are most often assigned in ascending order with odd and even numbers on each side of the thoroughfare. In a building, the floor identifier represents the level according to the traditions within the area, e.g., 1, 2, 3.

NOTE 2 Several types of locator designators exist, such as: Address number, address number suffix, building identifier, building name. A locator could be composed by an ordered set of these.

EXAMPLE In Paris, France a locator could be composed by two locator designators: address number "18" and address number suffix: "BIS".

Type:

Data type

Name:

designator

Definition:

-- Definition --

The identifying part of the locator designator composed by one or more digits or other characters.

-- Description --

NOTE The value is often a descriptive code assigned according to certain well known rules e.g. like ascending odd and even address numbers along the thoroughfare, or like floor identifiers: 0, 1, 2, 3.

EXAMPLE Address number "2065", Address number suffix "B", Floor identifier "7" door identifier "B707" are all locator attribute values.

Voidable:

false

Multiplicity:

1

Value type:

CharacterString

Name:

type

Definition:

-- Definition --

The type of locator value, which enables an application to interpret, parse or format it according to certain rules.

-- Description --

NOTE The type enables a user or an application to understand if the value "A" is e.g. an identifier of a specific building, door, staircase or dwelling.

Voidable:

false

Multiplicity:

1

Value type:

LocatorDesignatorTypeValue (code list)

Values:

Definition:

-- Definition --

Proper noun applied to the real world entity identified by the locator.

-- Description --

NOTE The locator name could be the name of the property or complex, of the building or part of the building, or it could be the name of a room inside a building.

Type:

Data type

Name:

name

Definition:

-- Definition --

The identifying part of the locator name.

-- Description --

NOTE 1 The data type allows names in different languages and scripts as well as inclusion of alternative name, alternative spellings, historical name and exonyms.

NOTE 2 The locator name could be the name of the property or complex, of the building or part of the building (e.g. a wing), or it could be the name of a room or similar inside the building.

NOTE 3 The locator name sometimes refer to the name of the family or business entity which at present or in the past has owned or occupied the property or building; although this is the case the locator name must not be confused with the name of the addressee(s).

NOTE 4 As locator name it is also possible to use a descriptive text that allows a user to identify the property in question.

EXAMPLE 1 The "Radford Mill Farm" in Timsbury, Bath, UK; The allotment house area "Brumleby" in Copenhagen, Denmark, the university campus "Cité Universitaire", in Paris, France.

EXAMPLE 2 "Millers House" in Stromness, Orkney Isles, UK; "Ulla's Pension" in Niederfell, Rheinland-Pfalz, Germany.

EXAMPLE 3 "Multi-storey car park at Southampton Magistrates Courts" in Southampton, UK.

Voidable:

false

Multiplicity:

1..*

Value type:

GeographicalName (data type)

Name:

type

Definition:

-- Definition --

The type of locator value, which enables an application to interpret, parse or format it according to certain rules.

-- Description --

NOTE The type enables a user or an application to understand if the name "Radford Mill Farm" is for example a name of a specific site or of a building.

Voidable:

false

Multiplicity:

1

Value type:

LocatorNameTypeValue (code list)

Values:

Definition:

-- Definition --

A part of the full name resulting from the subdivision of the thoroughfare name into separate, semantic parts, using the same language and script as the full thoroughfare name.

-- Description --

NOTE Each part of the name must be qualified by using the type attribute.

Type:

Data type

Name:

part

Definition:

-- Definition --

The character string that expresses the separate part of the name using the same language and script as the full thoroughfare name.

Voidable:

false

Multiplicity:

1

Value type:

CharacterString

Name:

type

Definition:

-- Definition --

A classification of the part of name according to its semantics (meaning) in the complete thoroughfare name.

Voidable:

false

Multiplicity:

1

Value type:

PartTypeValue (code list)

Values:

Definition:

-- Definition --

An address component which represents the identification of a subdivision of addresses and postal delivery points in a country, region or city for postal purposes.

-- Description --

NOTE 1 The postal descriptor is specified by means of a post code and/or names of the associated post office, town or area.

NOTE 2 In some countries post codes are seen as a proper geographic subdivision of the country, in other countries the post code is regarded only as an attribute that characterizes a (usually small) number of adjacent postal delivery points and addresses.

NOTE 3 The postal descriptors are created and developed on the basis of postal requirements (e.g. efficient sorting, logistics, transport and distribution). Consequently, there is not often a tight relationship between the postal areas and administrative units in the same area.

NOTE 4 The structure schema and formats of national postal descriptor systems are different. Sometimes (for example in the UK) the post code itself is the only information required for a valid address; in other situations both the post code and the associated name of post office or town is required. Sometimes there is a simple relationship between the code and the name; in other situations a set of postcodes are associated with a single post office or town.

NOTE 5 In some countries like e.g. The Republic of Ireland, no post code system currently exists, therefore the postal descriptor is only represented by the name of the post town.

EXAMPLE 1 In the UK the post code "EC4M 7DR" is sufficient, as a postal descriptor, while the related town name "London" is informative, but not necessary in the postal address.

EXAMPLE 2 In Sweden all postcodes starting with "80" is related to the postal name "Gävle". Therefore in the postal descriptor "802 74 Gävle", the postcode "802 74" bears all postal necessary information, while the town name "Gävle" is extra information.

EXAMPLE 3 In Denmark, outside the centre of Copenhagen, each postcode has a 1:1 relationship to one post name only: Postcode "6372" relates to the village "Bylderup-Bov".

EXAMPLE 4 In Germany the lowest level of the Postal descriptor (the 5 digit Postleitzahl) often does not fall within an administrative unit (e.g. municipality). The Postleitzahl is handled completely independent from the hierarchal systematic of the addresses. In addition, some "Postleitzahlen" represent not a delivery area, but institutions with a big amount of post.

Subtype of:

AddressComponent

Type:

Spatial Object Type

Name:

postCode

Definition:

-- Definition --

A code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.

-- Description --

NOTE 1 The structure, schema and formats of post codes are different in different countries. Often the components of the post code are hierarchical, e.g. when the first character(s) identifies the region covered by the post code and the next characters define the subdivision.

NOTE 2 In some countries, e.g., The Republic of Ireland, no post codes exists therefore the postal descriptor is only represented by the post name (e.g. town name).

EXAMPLE In the UK postcodes starting with W covers the Western (W1) and Paddington (W2-14) districts of the London postal district. In Sweden all postcodes starting with "80" is related to the postal name "Gävle".

Voidable:

false

Multiplicity:

0..1

Value type:

CharacterString

Name:

postName

Definition:

-- Definition --

One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.

-- Description --

NOTE 1 Often the post name (or names) is a supplementary identification of the post office to which the associated post code belongs. For example it may be the name of the town in which the office is situated. In other situations the post name could be an independent descriptor without any post code or it could be a postal subdivision connected to a parent postal descriptor (post code and post name).

NOTE 2 In some countries like e.g. Spain and The Netherlands, no post names exit therefore the postal descriptor is only represented by the post code.

NOTE 3 Even though the post name is the same as the name of an administrative unit or an address area, the area covered are not necessarilythe same.

Voidable:

false

Multiplicity:

0..*

Value type:

GeographicalName (data type)

Name:

EndLifeSpanVersion

Expression:

/* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */ inv: self.endLifespanVersion .isAfter(self.beginLifespanVersion)

Name:

PostCodeEmpty

Description:

If no post code exists, a post name is required.

Expression:

inv: self.postCode->isEmpty() implies self.postName->notEmpty()

Name:

PostNameEmpty

Description:

If no post name exists, a post code is required.

Expression:

inv: self.postName->isEmpty() implies self.postCode->notEmpty()

Definition:

-- Definition --

An address component which represents the name of a passage or way through from one location to another.

-- Description --

NOTE 1 A thoroughfare can, e.g., be a road or a waterway

NOTE 2 Thoroughfare names includes names of squares and of cul de sacs, and they can also represent the network of smaller roads or paths e.g. in a small village or settlement.

Subtype of:

AddressComponent

Type:

Spatial Object Type

Name:

name

Definition:

-- Definition --

Name of the thoroughfare.

-- Description --

NOTE 1 The name can optionally include an often used alternative name, alternative spelling of the name, a historic name or spelling, which is still in use. It may also optionally include a subdivision of the name into parts.

NOTE 2 Most often thoroughfares are roads, in this situation the thoroughfare name is the road name.

NOTE 3 The data type also allows a representation of the thoroughfare name in separate parts e.g. "rue" + "de la" + "Paix"

Voidable:

false

Multiplicity:

1..*

Value type:

GeographicalName (data type)

Name:

transportLink

Definition:

-- Definition --

One or several transport network links to which the spatial object of the thoroughfare name has been designated.

-- Description --

EXAMPLE The thoroughfare name "Na Pankráci" in Praha, The Czech Republic, has been designated as a road name for a number of road links (street segments) in the city.

Voidable:

true

Multiplicity:

0..*

Value type:

TransportLink (spatial object type)

Name:

EndLifeSpanVersion

Expression:

/* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */ inv: self.endLifespanVersion .isAfter(self.beginLifespanVersion)

Definition:

-- Definition --

Proper noun applied to thoroughfare optionally including a subdivision of the name into parts.

-- Description --

NOTE 1 The data type allows names in different languages and scripts as well as inclusion of alternative name, alternative spellings, historical name and exonyms.

NOTE 2 The data type allows optionally a representation of the thoroughfare name subdivided into separate, semantic parts e.g. "Avenue" + "de la" + "Poste".

Type:

Data type

Name:

name

Definition:

-- Definition --

Proper noun applied to the thoroughfare.

-- Description --

NOTE 1 The complete name of the thoroughfare must be applied in this attribute, including type, prefix or qualifier, like for example "Avenue de la Poste", "Calle del Christo Canneregio" or "Untere Quai". The name part attribute enables a representation of the name subdivided into separate semantic parts.

NOTE 2 The data type allows names in different languages as well as inclusion of exonyms.

Voidable:

false

Multiplicity:

1

Value type:

GeographicalName (data type)

Name:

nameParts

Definition:

-- Definition --

One or several parts into which the thoroughfare name can be subdivided.

-- Description --

NOTE 1 This is a definition which is consistent with that adopted by the UPU

NOTE 2 A subdivision of a thoroughfare name into semantic parts could improve parsing (e.g. of abbreviated or misspelled names) and for sorting of address data for example for postal delivery purposes. It could also improve the creation of alphabetically sorted street gazetteers.

NOTE 3 The data type requires that each part of the subdivided thoroughfare name is qualified with information on the semantics e.g. if it is a thoroughfare type (e.g., Rua, Place, Calle, Street), a prefix (e.g., da, de la, del), a qualifier (e.g., Unterer, Little) or if it is the core of the name, which would normally be used for sorting or indexing.

NOTE 4 In some countries or regions and for some thoroughfare names it is not feasible or it does not add value to subdivide the thoroughfare name into parts.

EXAMPLE In France the thoroughfare name "Avenue de la Poste" could be subdivided into these parts: "Avenue" + "de la" + "Poste".

Voidable:

true

Multiplicity:

0..*

Value type:

PartOfName (data type)

Definition:

-- Name --

area of responsibility type

-- Definition --

Set of types for the description of spatial responsibility.

Type:

Union type

Name:

areaOfResponsibilityByAdministrativeUnit

Definition:

-- Name --

area of responsibility by administrative unit

-- Definition --

Administrative unit describing the geographic extent of the responsibility of a service.

Voidable:

false

Multiplicity:

1..*

Value type:

AdministrativeUnit (spatial object type)

Name:

areaOfResponsibilityByNamedPlace

Definition:

-- Name --

area of responsibility by named place

-- Definition --

Geographical object describing the geographic extent of the responsibility of a service.

Voidable:

false

Multiplicity:

1..*

Value type:

NamedPlace (spatial object type)

Name:

areaOfResponsibilityByNetwork

Definition:

-- Name --

area of responsibility by network

-- Definition --

Part of a network describing the geographic extent of the competence of a service.

Voidable:

false

Multiplicity:

1..*

Value type:

NetworkReference (data type)

Name:

areaOfResponsibilityByPolygon

Definition:

-- Name --

area of responsibility by polygon

-- Definition --

Polygon describing the geographic extent of the responsibility of a service.

Voidable:

false

Multiplicity:

1

Value type:

GM_MultiSurface

Definition:

-- Name --

governmental service

-- Definition --

Administrative and social governmental services such as public administrations, civil protection sites, schools and hospitals provided by Public Administrative Bodies or by private institutions as far as they are covered by the scope of the INSPIRE directive. This scope is mapped to the values of the corresponding code list serviceType Value.

-- Description --

The accordant sites are commonly presented in governmental and municipal portals and map systems as "point of interest"-data, and may be point-based locations of a variety of categories of municipal and governmental services and social infrastructure. The spatial object type itself is generic in terms of the modelling approach, that the concrete type of a GovernmentalService is determined by the value of the attribute serviceType.

Type:

Spatial Object Type

Name:

areaOfResponsibility

Definition:

-- Name --

area of responsibility

-- Definition --

The spatial responsibility of a service instance.

-- Description --

EXAMPLE 1: An administration is responsible for a municipality;

EXEMPLE 2: A specialized hospital is responsible for a region.

Voidable:

true

Multiplicity:

0..1

Value type:

AreaOfResponsibilityType (union data type)

Name:

beginLifespanVersion

Definition:

-- Name --

begin lifespan version

-- Definition --

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

-- Description --

Related to the life-cycle of the spatial object in the data set.

Voidable:

true

Multiplicity:

1

Value type:

DateTime

Name:

endLifespanVersion

Definition:

-- Name --

end lifespan version

-- Definition --

Date and time at which this version of the spatial object was superseded or retired in the spatial data set.

-- Description --

Related to the life-cycle of the spatial object in the data set.

Voidable:

true

Multiplicity:

0..1

Value type:

DateTime

Name:

inspireId

Definition:

-- Name --

INSPIRE identifier

-- Definition --

External object identifier of the governmental service.

-- 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.

Voidable:

false

Multiplicity:

1

Value type:

Identifier (data type)

Name:

pointOfContact

Definition:

-- Name --

point of contact

-- Definition --

Contains necessary information to get access to a service and/or initial information regarding a service.

-- Description --

In some cases this information will coincide with the contact information of the service authority, owner or operator (i.e. specific position or role of the responsible party, described in the relatedParty attribute of the GovernmentalServiceExtended in the extended profile).

Voidable:

true

Multiplicity:

1..*

Value type:

Contact (data type)

Name:

serviceLocation

Definition:

-- Name --

service location

-- Definition --

Location where the service is offered.

Voidable:

false

Multiplicity:

1

Value type:

ServiceLocationType (union data type)

Name:

serviceType

Definition:

-- Name --

service type value

-- Definition --

Type of an administrative and governmental service.

Voidable:

false

Multiplicity:

1

Value type:

ServiceTypeValue (code list)

Tagged Values:

Name:

endLifespanVersion

Expression:

/* If set, the date endLifespanVersion shall be later than beginLifespanVersion. */ inv: self.endLifespanVersion .isAfter(self.beginLifespanVersion)

Definition:

-- Name --

service location type

-- Definition --

Set of types of references to locate a service.

Type:

Union type

Name:

serviceLocationByActivityComplex

Definition:

-- Name --

service location by activity complex

-- Definition --

Location of the service by referring to an activity complex.

Voidable:

false

Multiplicity:

1

Value type:

ActivityComplex (spatial object type)

Name:

serviceLocationByAddress

Definition:

-- Name --

service location by address

-- Definition --

Location of the service by referring to an address.

Voidable:

false

Multiplicity:

1

Value type:

Address (spatial object type)

Name:

serviceLocationByBuilding

Definition:

-- Name --

service location by building

-- Definition --

Location of the service by referring to a building.

Voidable:

false

Multiplicity:

1..*

Value type:

Building (spatial object type)

Name:

serviceLocationByGeometry

Definition:

-- Name --

service location by geometry

-- Definition --

Location of the service by referring to a geometry.

Voidable:

false

Multiplicity:

1

Value type:

GM_Object

Name:

serviceLocationByUtilityNode

Definition:

-- Name --

location service by utility node

-- Definition --

Location of the service by referring to a node related to a utility network (water, telecommunication, etc.), e.g. hydrant or emergency call point.

Voidable:

false

Multiplicity:

1

Value type:

UtilityNode (spatial object type)

Definition:

-- Name --

administrative boundary

-- Definition --

A line of demarcation between administrative units.

Type:

Spatial Object Type

Name:

admUnit

Definition:

-- Name --

adm unit

-- Definition --

The administrative units separated by this administrative boundary.

-- Description --

NOTE In case of a national boundary (i.e. nationalLevel='1st order') only one national administrative unit (i.e. country) is provided.

Voidable:

true

Multiplicity:

1..*

Value type:

AdministrativeUnit (spatial object type)

Name:

beginLifespanVersion

Definition:

-- Name --

begin lifespan version

-- Definition --

Date and time at which this version of the spatial object was inserted or changed in the spatial data set.

Voidable:

true

Multiplicity:

1

Value type:

DateTime