: Public <<dataType>> Class
| Created: |
26/06/2008 14:22:00 |
| Modified: |
01/09/2009 17:23:34 |
|
Project: |
|
| Author: |
friisan |
| Version: |
1.0 |
| Phase: |
1.0 |
| Status: |
Proposed |
| Complexity: |
Easy |
| Difficulty: |
|
| Priority: |
|
| Multiplicity: |
|
Advanced: |
|
| UUID: |
{B1BC7F48-3B9C-4717-8D38-B79926A5220D} |
| Appears In: |
Addresses, Data types |
-- Definition --<br/>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.<br/><br/>-- Description --<br/>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.<br/><br/>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. <br/><br/>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.<br/><br/>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. <br/><br/>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. <br/><br/>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. <br/><br/>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.<br/><br/>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"<br/>
- Attributes
- Associations To
- Tagged Values
- Constraints
| Attribute |
Public LocatorDesignator designator
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
Ordered
|
| Range: |
Range:0 to * |
| Transient: |
False |
| Derived: |
False |
| IsID: |
False |
|
Notes:
|
-- Definition --<br/>A number or a sequence of characters that uniquely identifies the locator within the relevant scope(s). <br/>
|
|
Public LocatorLevelValue level
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
| Transient: |
False |
| Derived: |
False |
| IsID: |
False |
|
Notes:
|
-- Definition --<br/>The level to which the locator refers.<br/>
|
|
Public LocatorName name
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
Ordered
|
| Range: |
Range:0 to * |
| Transient: |
False |
| Derived: |
False |
| IsID: |
False |
|
Notes:
|
-- Definition --<br/>A geographic name or descriptive text associated to a property identified by the locator.<br/><br/>-- Description --<br/>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.<br/><br/>NOTE 2 As locator name it is also possible to use a description that allows a user to identify the property in question. <br/><br/>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. <br/><br/>EXAMPLE In the address "Calle Santiago, 15, Elizondo-Baztán, Navarra, Spain" the building name "Urtekoetxea" is an alternative to the building identifier "3".<br/>
|
|
| Element |
Source Role |
Target Role |
«featureType» AddressComponent
Class
|
Name:
|
Name: withinScopeOf
-- 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.
|
 Details:
|
| Tag |
Value |
| isCollection |
false |
 Details:
|
| noPropertyType |
false |
 Details:
|
| xsdEncodingRule |
iso19136_2007_INSPIRE_Extensions |
 Details:
|
| Constraint |
Type |
Status |
| DesignatorEmpty |
OCL |
Approved |
 Details:
/* If no designator exists, a name is required. */<br/>inv: self.designator-#gt;isEmpty() implies self.name-#gt;notEmpty() <br/>
|
| NameEmpty |
OCL |
Approved |
 Details:
/* If no name exists, a designator is required. */<br/>inv: self.name-#gt;isEmpty() implies self.designator-#gt;notEmpty() <br/>
|