| Created: | 11/04/2008 10:30:00 |
| Modified: | 22/02/2013 11:03:03 |
Project: |
|
Advanced: |
|
| Attribute | ||
|
Public CharacterString alternativeIdentifier |
||
Details:
|
||
|
Public DateTime beginLifespanVersion |
||
Details:
|
||
|
Public DateTime endLifespanVersion |
||
Details:
|
||
|
Public Identifier inspireId |
||
Details:
|
||
|
Public AddressLocator locator |
||
Details:
|
||
|
Public GeographicPosition position |
||
Details:
|
||
|
Public StatusValue status |
||
Details:
|
||
|
Public DateTime validFrom |
||
Details:
|
||
|
Public DateTime validTo |
||
Details:
|
| Element | Source Role | Target Role |
|
«featureType» Address Class |
Name: |
Name: parentAddress -- 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. |
Details:
|
||
|
«featureType» Building Class |
Name: |
Name: building -- 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". |
Details:
|
||
|
«featureType» CadastralParcel Class |
Name: |
Name: parcel -- 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". |
Details:
|
||
| Element | Source Role | Target Role |
|
«dataType» AddressRepresentation Class |
Name: |
Name: addressFeature -- Definition -- Reference to the address spatial object. |
Details:
|
||
|
«featureType» AddressComponent Class |
Name: component -- 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. |
Name: |
Details:
|
||
|
«featureType» Address Class |
Name: |
Name: parentAddress -- 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. |
Details:
|
||
| Tag | Value |
| byValuePropertyType | false |
Details:
|
|
| isCollection | false |
Details:
|
|
| noPropertyType | false |
Details:
|
|
| xsdEncodingRule | iso19136_2007_INSPIRE_Extensions |
Details:
|
|
| Constraint | Type | Status |
| AddressPosition | OCL | Approved |
Details:
/* An address shall have exactly one default geographic position (default attribute of GeographicPosition must be true) */<br/>inv: self.position -#gt; one(a1 | a1.default = true)<br/><br/>
|
||
| AddressCountry | OCL | Approved |
Details:
/* An address shall have an admin unit address component spatial object whose level is 1 (Country) */<br/>inv: self.component -#gt; forAll (a1 | exists(a1.parent.oclIsTypeOf(AdminUnitName) and a1.parent.level=1))<br/><br/>
|
||
| EndLifeSpanVersion | OCL | Approved |
Details:
/* If date set endLifespanVersion must be later than beginLifespanVersion (if set) */<br/>inv: self.endLifespanVersion.isAfter(self.beginLifespanVersion)<br/>
|
||
| Object | Type | Connection | Direction | Notes |
| «featureType» AddressComponent | Class | Weak | From |