Id; Navn; Beskrivelse; Stereotype; Versjon; Status; Pakke; NavPakke; EAID_3DEDA627_3590_4503_AE1A_8EE5CE227F65;Addresses;;diagram;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\AddressesAddresses EAID_1CE04FDD_0B0B_4fa5_A334_ACEC0046F055;Codelists;;diagram;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\AddressesAddresses EAID_A2C0F066_6DB2_4ee8_8E15_FE2C680E5410;Spatial Object Types;;diagram;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\AddressesAddresses EAID_669B639C_EF67_4149_A203_FB83520E40CB;Cross-theme Relationships;;diagram;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\AddressesAddresses EAID_9C2B6369_AD50_461e_A447_201F3FA31203;Data types;;diagram;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\AddressesAddresses EAID_D3C8F94E_5787_4734_8F97_E5E5BC4513BC;Imported types;;diagram;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\AddressesAddresses EAID_0EC11D49_D547_41d1_8B1B_A902E55C5C25;AdminUnitName;-- 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.;objekttype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;AddressComponent;"-- 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.";objekttype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_5868F64B_7310_4535_80EE_FFF2C4C19B99;PostalDescriptor;"-- 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.";objekttype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_88F27422_8339_47d2_BFB1_EC1DA2FE5E8B;ThoroughfareName;-- 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.;objekttype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;Address;"-- 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"".";objekttype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_E682AD35_96DE_455a_9756_B5BDC68C36C2;AddressAreaName;"-- 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.";objekttype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_1D40E7A5_18B6_4fbc_A8F8_5C3272B07365;AddressLocator;"-- 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""";datatype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_62D6E10A_F3AE_44c4_96F4_8A4334ECB287;PartOfName;-- 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.;datatype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_63B533FC_5412_4496_9B04_7907425B18F9;ThoroughfareNameValue;"-- 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"".";datatype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_7E0EBF3E_E821_4773_929A_391CB0D577AD;LocatorDesignator;"-- 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"".";datatype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_A11E320D_ED2F_4b19_9576_BD4F43F660FB;GeographicPosition;-- 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.;datatype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;AddressRepresentation;-- 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.;datatype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_ED5EFBB1_020B_4f7c_B97C_4692E232B154;LocatorName;-- 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.;datatype;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_2924A4C8_1DED_45f5_B812_45D01BCA9E34;LocatorLevelValue;-- Definition -- The level to which the locator refers. -- Description -- NOTE The locator level attribute enables the comparison of locators from different countries. EXAMPLE In The Netherlands a single locator, the address number, identifies a dwelling or business entity unit (unit level locator). In Spain up to four locators could be needed to obtain the same level of detail: Address number, entrance number, stair identifier plus a floor and door identifier. ;kodeliste;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_3293D1A5_DF5B_415f_84BF_C3CDB1878ADD;GeometryMethodValue;-- Definition -- Description of how and by whom this geographic position of the address was created or derived. -- Description -- NOTE Information on what type of spatial feature the geographic position of the address was created or derived from, is represented by the GeometrySpecificationValue.;kodeliste;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_5EE587A8_2C75_4aaf_91EB_7EC478C968C3;LocatorNameTypeValue;-- Definition -- Description of the semantics of the locator name.;kodeliste;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_6472330C_4A73_4aea_806A_7E5236292E96;GeometrySpecificationValue;-- Definition -- Information defining the specification used to create or derive this geographic position of the address. -- Description -- NOTE 1 Multiple address points can be derived from one polygon spatial object. NOTE 2 If the position of an address is derived from a polygon spatial object a number of different approaches is used. EXAMPLE 1 The same point (e.g., centre point of the polygon) is used for each address, thus, multiple address points will be overlapping. EXAMPLE 2 Each point position is unique within the polygon to be able to visually distinguish the representation of each address. ;kodeliste;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_6E5CA92A_37A8_420d_A826_CEF48F9D7BF2;StatusValue;-- Definition -- Current validity of the real world address or address component. -- Description -- NOTE 1 This element enables the application schema to represent a full life-cycle of an address and address component, from proposed to reserved, current and retired, or even alternative. NOTE 2 The status value relates to the real world address or address component and not to the property to which the address or address component is assigned (the addressable object).;kodeliste;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_9AFD5036_E2EC_489d_AA5E_E0023BEC7B44;LocatorDesignatorTypeValue;-- Definition -- Description of the semantics of the locator designator.;kodeliste;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_E0EAAFC6_AC2E_4956_A0E9_434D7510FF55;PartTypeValue;-- Definition -- A classification of the part of name according to its semantics in the complete thoroughfare name.;kodeliste;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses EAID_0EC11D49_D547_41d1_8B1B_A902E55C5C25;name;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AdminUnitName EAID_0EC11D49_D547_41d1_8B1B_A902E55C5C25;level;-- Definition -- The level of administration in the national administrative hierarchy.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AdminUnitName EAID_1D40E7A5_18B6_4fbc_A8F8_5C3272B07365;designator;-- Definition -- A number or a sequence of characters that uniquely identifies the locator within the relevant scope(s). ;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressLocator EAID_1D40E7A5_18B6_4fbc_A8F8_5C3272B07365;name;"-- 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"".";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressLocator EAID_1D40E7A5_18B6_4fbc_A8F8_5C3272B07365;level;-- Definition -- The level to which the locator refers.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressLocator EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;inspireId;-- 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;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressComponent EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;alternativeIdentifier;"-- 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.";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressComponent EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;beginLifespanVersion;-- 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. ;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressComponent EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;endLifespanVersion;"-- 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.";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressComponent EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;status;-- 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).;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressComponent EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;validFrom;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressComponent EAID_487C66E1_2B5C_4c8e_BE76_77560A90E8C1;validTo;-- Definition -- Date and time at which the address component ceased or will cease to exist in the real world.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressComponent EAID_5868F64B_7310_4535_80EE_FFF2C4C19B99;postName;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\PostalDescriptor EAID_5868F64B_7310_4535_80EE_FFF2C4C19B99;postCode;"-- 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"".";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\PostalDescriptor EAID_62D6E10A_F3AE_44c4_96F4_8A4334ECB287;part;-- Definition -- The character string that expresses the separate part of the name using the same language and script as the full thoroughfare name.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\PartOfName EAID_62D6E10A_F3AE_44c4_96F4_8A4334ECB287;type;-- Definition -- A classification of the part of name according to its semantics (meaning) in the complete thoroughfare name. ;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\PartOfName EAID_63B533FC_5412_4496_9B04_7907425B18F9;name;"-- 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. ";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\ThoroughfareNameValue EAID_63B533FC_5412_4496_9B04_7907425B18F9;nameParts;"-- 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"".";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\ThoroughfareNameValue EAID_7E0EBF3E_E821_4773_929A_391CB0D577AD;designator;"-- 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.";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\LocatorDesignator EAID_7E0EBF3E_E821_4773_929A_391CB0D577AD;type;"-- 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.";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\LocatorDesignator EAID_88F27422_8339_47d2_BFB1_EC1DA2FE5E8B;name;"-- 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""";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\ThoroughfareName EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;inspireId;-- 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;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;alternativeIdentifier;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;position;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;status;-- 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).;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;locator;-- Definition -- Human readable designator or name.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;validFrom;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;validTo;-- Definition -- Date and time at which this version of the address ceased or will cease to exist in the real world.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;beginLifespanVersion;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_8C55A62E_93EC_428c_835B_F2BCD1BC1C30;endLifespanVersion;"-- 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.";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\Address EAID_A11E320D_ED2F_4b19_9576_BD4F43F660FB;geometry;-- Definition -- The position of the point expressed in coordinates in the chosen spatial reference system.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\GeographicPosition EAID_A11E320D_ED2F_4b19_9576_BD4F43F660FB;specification;-- Definition -- Information defining the specification used to create or derive this geographic position of the address.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\GeographicPosition EAID_A11E320D_ED2F_4b19_9576_BD4F43F660FB;method;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\GeographicPosition EAID_A11E320D_ED2F_4b19_9576_BD4F43F660FB;default;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\GeographicPosition EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;adminUnit;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressRepresentation EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;locatorDesignator;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressRepresentation EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;locatorName;-- Definition -- Proper noun(s) applied to the real world entity identified by the locator.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressRepresentation EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;addressArea;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressRepresentation EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;postName;-- Definition -- One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points. ;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressRepresentation EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;postCode;-- Definition -- A code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points. ;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressRepresentation EAID_E4C0B875_275B_4707_A272_C4E8EF6CED71;thoroughfare;-- Definition -- The name or names of a passage or way through from one location to another like a road or a waterway. ;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressRepresentation EAID_E682AD35_96DE_455a_9756_B5BDC68C36C2;name;-- 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.;egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\AddressAreaName EAID_ED5EFBB1_020B_4f7c_B97C_4692E232B154;name;"-- 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.";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\LocatorName EAID_ED5EFBB1_020B_4f7c_B97C_4692E232B154;type;"-- 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. ";egenskap;4.0;Gyldig;Addresses;Inspire Consolidated UML Model\Themes\Annex I\Addresses\Addresses\LocatorName