1. Abstract
-This document specifies how addresses should be assigned and maintained to support Australia’s addressing infrastructure. It intends to help addressing authorities to fulfil custodial responsibilities and enable a consistent national approach to ongoing maintenance, accuracy and quality of addresses.
-It is intended for use by agencies responsible for addressing, particularly Local Government in Australia. It should also be adhered to by developers where addressing authorities enable address numbering and road naming proposals.
-This standard should be used in collaboration with national guidelines held by the Intergovernmental Committee on Surveying and Mapping (ICSM).
-2. Metadata
-IRI |
-
|
-
Name |
-Address Creation & Maintenance Standard |
-
Description |
-How addresses should be assigned and maintained to support Australia’s addressing infrastructure |
-
Created |
-2024-09-01 |
-
Modified |
-2024-09-13 |
-
Issued |
-0000-00-00 |
-
Creator |
-- |
Publisher |
-Intergovernmental Committee on Surveying & Mapping (ICSM) (ICSM@ga.gov.au) |
-
Provenance |
-This standard was created in 2024 by the ICSM Addressing Working Group after the publication of ISO’s publication in 2023 of ISO19160-2 Assigning and maintaining addresses for objects in the physical world and in 2024 of ICSM’s publication of its Address Model. This standard is a profile of the former and instructions in the production of data conformant to the latter. |
-
Status |
-Draft |
-
Version |
-0.0.1 |
-
Code Repository |
-https://github.com/Spatial-Information-QLD/addr-creation-maintenance |
-
License |
-- |
Copyright |
-© Intergovernmental Committee on Surveying & Mapping, 2024 |
-
3. Preamble
-3.1. Scope
-This document is a Profile of ISO 19160-2:2023, Addressing – Part 2: Assigning and maintaining addresses for objects in the physical world.
-In the Australian context, this standard applies to thoroughfare-based addressing i.e. street and water, as well as landmark addressing. It is designed as a replacement for <<ANZ4819, ANZ4819 Rural and urban addressing>>. This standard does not apply to other address classes such as postal or landmark at this time. Postal addressing is expected to adhere to AS/NZS ISO 19160.4:2023 International postal address components and template language.
-This document focuses on assigning and maintaining addresses that allow the unambiguous determination of an object in the physical world for purposes of identification and location in the context of public administration and public service delivery.
-This standard provides requirements for addressing authorities to assign addresses, record the related information, and signage related to addressing components.
-3.2. Normative References
-The following standard is needed for the application of this Australian Profile:
-The following documents inform aspects of this standard for Australia:
--
-
-
-
<<ANZ4819, ANZ4819 Rural and urban addressing>>
-
- -
-
AS 4590.1:2017 Interchange of client information
-
- -
-
AS/NZS ISO 19160.1:2018 Addressing – Part 1: Conceptual model
-
- -
-
ICSM Addressing 2035 Strategy and Supporting Addendum1
-
-
The following document defines the addressing model used for address records:
--
-
- - - -
3.3. Terms & Definitions
--
-
- access point -
-
-
The position along a throughfare (road or water feature) where the public would normally access an address site. SOURCE: this standard
-
- - address -
-
-
An address is structured information that allows the unambiguous determination of an object for purposes of identification and location (SOURCE ISO 19160-1:2015). The objects exist in the physical world (i.e. virtual objects are excluded) and can be outdoor (e.g. a building) or indoor (e.g. an office inside a building). SOURCE: this standard
-
- - addressable object -
-
-
Object that may be assigned an address. SOURCE: ISO19160-2
-
- - address assignment method -
-
-
The way in which addresses are assigned according to the rules of an address reference system. SOURCE: ISO19160-2
-
- - address authority -
-
-
Agency responsible for assigning addresses. Usually a local government. SOURCE: ANZ4819
-
- - address class -
-
-
description of a set of addresses that share the same address components, operations, methods, relationships, and semantics. SOURCE: ISO19160-2
-
- - address component -
-
-
constituent part of the address. These may reference another object such as a spatial object including and administrative boundary or land parcel, or a non-spatial entity. SOURCE: ISO19160-2
-
- - address reference system -
-
-
A defined set of address components and the rules for their combination into addresses. SOURCE: ISO19160-2
-
- - address site -
-
-
a site for which an address is being assigned. SOURCE: ANZ4819
-
- - alternative name -
-
-
a name that is an alternative name to another name for the same feature. SOURCE: ANZ4819
-
- - dual name -
-
-
a name that consists of two official names that must be used together, usually one indigenous and one European (e.g. ‘Aoraki/Mount Cook’). SOURCE: ANZ4819
-
- - formed -
-
-
in relation to a road, means that it is physically constructed or prepared for passage by vehicles or pedestrians. SOURCE: ANZ4819
-
- - geocode -
-
-
a point feature for an address indicating a geometry. SOURCE: this standard
-
- - locality -
-
-
a named geographical area defining a community or area of interest, which may be rural or urban in character, and is usually a suburb in the latter case. SOURCE: ANZ4819
-
- - IRI -
-
-
Internationalized Resource Identifiers, IRIs, are a sequence of characters from the -Universal Character Set. SOURCE: ISO10646
-
- - primary address site -
-
-
an address site that is not contained within another address site. It may contain a sub-address site. SOURCE: ANZ4819
-
- - profile -
-
-
set of one or more base standards or subsets of base standards, and, where applicable, the identification of chosen clauses, classes, options and parameters of those base standards, that are necessary for accomplishing a particular function. SOURCE: ISO19160-2
-
- - sub-address -
-
-
TODO: complete me. SOURCE: ANZ4819
-
- - sub-address site -
-
-
an address site that is contained within a primary address site e.g. an apartment within a building SOURCE: ANZ4819. Sometimes referred to as a secondary address site. SOURCE: this standard
-
- - thoroughfare address -
-
-
an address that is assigned with reference to the thoroughfare it is accessed from, for example a road or water feature. SOURCE: this standard
-
-
3.4. Conformance
-Keywords used to signify requirements in this document are those defined by RFC2119 and they are:
--
-
-
-
MUST
-
- -
-
MUST NOT
-
- -
-
REQUIRED
-
- -
-
SHALL
-
- -
-
SHALL NOT
-
- -
-
SHOULD
-
- -
-
SHOULD NOT
-
- -
-
RECOMMENDED
-
- -
-
MAY
-
-
For process and information to be conformant with this standard, the imperatives of those keywords MUST be followed as per their RFC2119 definitions.
-Address information created following processes outlined in this standard MUST conform to the ICSM Address Model with conformance to it tested as per it’s Annex B: Validation section.
-3.5. Namespaces
-Namespaces, in this document’s context, are managed IRIs which allow further IRIs to be created within their scope. Namespaces are allocated to macro data objects and provide IRIs for all the micro data objects within that object.
-For example, the IRI for the Address Model is https://linked.data.gov.au/def/addr and the namespace of https://linked.data.gov.au/def/addr/ (the Address Model’s IRI + /) allows for IRIs to be created for elements within the model such as one for the AddressableObject class which is https://linked.data.gov.au/def/addr/AddressableObject.
When used in some forms of data and human-readable text, IRIs can either be written in full or in a shortened form using prefixes for known namespace. For example, the Addresable Object mentioned above can be written in full like this:
https://linked.data.gov.au/def/addr/AddressableObject
or in prefixed form with the prefix addr for the namespace https://linked.data.gov.au/def/addr/ like this:
addr:AddressableObject
The prefixed namespaces used in this document are:
-| Prefix | -Namespace | -Description | -
|---|---|---|
|
-
|
-- |
|
-
|
-This Document |
-
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-Australian Statistical Geographies Standard Dataset, Release 3 |
-
|
-
|
-- |
|
-
|
-Generic examples |
-
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
|
-
|
-- |
4. Introduction
-This is a placeholder
--
-
-
-
abstract
-
- -
-
purpose
-
- -
-
history
-
- -
-
big picture
-
- -
-
doc structure
-
-
5. Good Practice for assigning and maintaining addresses
-5.1. General
-5.1.1. Objectives
-Requirement 1. /req/goodPractice/general/objectives
-A good practice shall specify one or more objectives for which addresses are assigned and shall be guided by these objectives. -This standard specifies requirements for address assignment in Australia to enable each address to be readily and unambiguously identified and located. -Objectives of the standard are: - Localities can be uniquely and clearly identified - Roads and other access thoroughfares can be uniquely and clearly identified and located - Assigned addressing numbering ensures addresses can be uniquely and clearly identified and located - Signage ensures assigned addresses can be readily identified and located -These objectives are to apply to all addressable locations throughout Australia, including indigenous communities and private communities such as mining towns and retirement villages. -It is noted that addresses previously confirming to AS/NZS 2819:2011 should meet this standard. Addresses created prior to AS/NZS 2819:2011 may not adhere to requirements as AS/NZS 4819:2011 explicitly noted that the standard was not to be applied retrospectively.
-Recommendation 1. /rec/goodPractice/general/objectivesforPublicGood
-An objective should specify that the assignment and maintenance of addresses is done with the purpose of benefitting governance and society and thereby achieving public good. -Making address assignment and maintenance data open benefits governance and society by enhancing transparency, facilitating efficient urban planning, infrastructure development, emergency response, and ensuring equitable access to essential services, ultimately contributing to the public good.
-5.1.2. Context
-Requirement 2. /req/goodPractice/general/context
-A good practice shall specify the context in which the address assignment and maintenance takes place and shall be guided by this context. -When new housing, business complexes, or other types of development occur, local government are responsible for assigning and maintaining addresses for their jurisdiction. However, for Australian Capital Territory (ACT) and Northern Territory, the role is fulfilled by the territory government. -State and territory governments aggregate these addresses into authoritative jurisdictional datasets. Data products and services are then distributed through various channels, including to the national data provider. PSMA Australia Limited (a public company owned by the nine governments of Australia; trading as Geoscape Australia) collate data at the national level.
-5.1.3. Conceptual Model
-Requirement 3. /req/goodPractice/general/conceptualModel
-A good practice shall specify the conceptual model for the classes (types) of addresses assigned and maintained through the good practice. This includes a description of the address reference system, i.e., a set of address components and the rules for their combination into addresses. -Australia is currently developing a national addressing model. Review is being taken of use of the Queensland conceptual model as a national model: https://linked.data.gov.au/def/addr -• Address Model: Address Model -• Roads model: Roads Model -• Geographical Names model: Geographical Names Model -• Compound naming model: Compound Naming Model -• Cadastral model: Cadastral Model -• Lifecycle model: Lifecycle Model
-Recommendation 2. /rec/goodPractice/general/ISO19160-1Profile
-The conceptual model that describes classes (types) of addresses assigned and maintained through the good practice should conform to ISO 19160-1:2015. -NOTE 1 Amongst others, ISO 19160-1:2015 requires that a conformant address model clearly specifies how the position of an address is represented in the model. ISO 19160-1:2015 provides two ways for doing this: 1) an address has coordinates to specify its position; 2) the position of the address is inferred from the addressed object. [SOURCE: ISO 19160-1:2015, 6.1] -NOTE 2 Postal addresses are defined and described in ISO 19160-4:2017, a profile of ISO 19160-1:2015. -EXAMPLE 14 The draft NZ profile of ISO 19160-1:2015 describes its conformance to ISO 19160-1:2015. The NZ profile defines six address classes: Thoroughfare, Water, Service Delivery, Rural Post Delivery, Thoroughfare4819, and Water4819. New addresses (excluding NZ Post addresses for service delivery and rural post delivery) quality assured by the LINZ address team are assessed against the Thoroughfare4819 and Water4819 classes, and these classes align with the requirements in AS/NZS 4819:2011.
-Recommendation 3. /rec/goodPractice/general/intellectualPropertyRights
-A good practice should specify to whom the intellectual property rights of the address assignment method and the address data belong. At the least, government organizations should have free access to the address data for services to ensure the health, safety and welfare of the public. -TBC
-5.1.4. License
-Requirement 4. /req/goodPractice/general/license
-A good practice shall specify the licences under which the address data is available and the terms and conditions for their use. Different licenses may apply for different users.
-National
-Australia – The national address dataset is released quarterly under a modified Creative Commons Attribution 4.0 International license (CC BY 4.0), which adds a restriction relating to the use of the open G-NAF for the sending of mail .
-Jurisdictions
- - -Northern Territory
-Northern Territory - Addresses are managed by the Survey Branch of the Department of Infrastructure, Planning and Logistics. [Cannot find data on https://data.nt.gov.au/]
-Queensland
-Queensland – Addresses are available as open data through QSpatial, licensed under a Creative Commons - Attribution 4.0 International licence. https://creativecommons.org/licenses/by/4.0/
-South Australia
-South Australia - [Cannot find data other than rural address locations in LocationSAMapViewer]
-Tasmania
-Tasmania – Addresses are available through theList, licensed under a Creative Commons licence. https://creativecommons.org/licenses/by/3.0/au/deed.en
-Victoria
-Victoria – Addresses are available as open data through VicMap, licensed under a Creative Commons - Attribution 4.0 International licence. https://creativecommons.org/licenses/by/4.0/
-Recommendation 4. /rec/goodPractice/general/facilitateAssignment
-A good practice should specify a method for assigning values to address components that could be automated to speed up or facilitate address assignment and maintenance. -EXAMPLE 19 AS/NZS 4819:2011, Rural and urban addressing, contains a clause for addressing rural properties based on the measured distance along the road, from a defined datum point, the accessway of the property is, with odd numbers on the left side of the road and even numbers on the right. -Use of vocabularies -• Address alias types: https://linked.data.gov.au/def/address-alias-type -• Address classes: https://linked.data.gov.au/def/address-classes -• Address status types: https://linked.data.gov.au/def/address-status-type -• Geocode types: https://linked.data.gov.au/def/geocode-types -• Level types: https://linked.data.gov.au/def/level-types -• Record access: https://linked.data.gov.au/def/record-access -• Sub-address types: https://linked.data.gov.au/def/subaddress-types -• Information source: https://linked.data.gov.au/def/source -• Ground relationship: https://linked.data.gov.au/def/ground-relationship -• LRRS indicator: https://linked.data.gov.au/def/lrrs-indicator -• Population zone: https://linked.data.gov.au/def/population-zone -• Positional accuracy: https://linked.data.gov.au/def/positional-accuracy -• Record access: https://linked.data.gov.au/def/record-access -• Road cadastral relationship: https://linked.data.gov.au/def/road-cadastral-relationship -• Road classifications: https://linked.data.gov.au/def/road-classifications -• Road geometry notes: https://linked.data.gov.au/def/road-geometry-notes -• Road lane count: https://linked.data.gov.au/def/road-lane-count -• Road maintainer: https://linked.data.gov.au/def/road-maintainer -• Road name part types: https://linked.data.gov.au/def/road-name-part-types -• Road operational statuses: https://linked.data.gov.au/def/road-operational-statuses -• Road owner: https://linked.data.gov.au/def/road-owner -• Road seasonality: https://linked.data.gov.au/def/road-seasonality -• Road sub-classes: https://linked.data.gov.au/def/road-sub-classes -• Road suffixes: https://linked.data.gov.au/def/road-suffixes -• Road surfaces: https://linked.data.gov.au/def/road-surfaces -• Road trafficability: https://linked.data.gov.au/def/road-trafficability -• Road travel direction: https://linked.data.gov.au/def/road-travel-direction -• Road types: https://linked.data.gov.au/def/road-types -• Road user access: https://linked.data.gov.au/def/road-user-access -• Spatial capture method: https://linked.data.gov.au/def/spatial-capture-method -• State controlled road indicator: https://linked.data.gov.au/def/scr-indicator -• Surface capture method: https://linked.data.gov.au/def/surface-capture-method -• Information source: https://linked.data.gov.au/def/source -• Geographical names part types: https://linked.data.gov.au/def/gn-part-types -• Geographical name statuses: https://linked.data.gov.au/def/gn-statuses -• Geographical objects categories vocabulary: https://linked.data.gov.au/def/go-categories
-5.1.5. Communication Through Physical Identifiers
-Requirement 5. /req/goodPractice/general/communicationThroughPhysicalIdentifiers
-A good practice shall specify how addresses will be communicated through physical identifiers. -EXAMPLE 26 Addresses are communicated by street name signs on street corners and number signs on buildings. -EXAMPLE 27 AS/NZS 4819:2011, Rural and urban addressing, specifies that “it is desirable that the possible range and direction of numbers be included on the road name sign”. -To support emergency services, street numbers shall be visible from the access point to the address site.
-5.2. Principles
-5.2.1. Addressing principles
-Recommendation 6. /rec/goodPractice/principles/addressing/unambiguity
-An address shall be assigned to an addressable object in the physical world so that it allows the unambiguous determination of the object for purposes of identification and location (ISO 19160-1:2015). -NOTE 1 The position of an address can be represented in two ways: 1) The position is specified by coordinates in the ‘position’ attribute. 2) The position is inferred from the addressed object. See 6.1 in ISO 19160-1:2015. -A thoroughfare address shall be assigned that conforms to the list of mandatory components to enable unambiguity, and enable it to be readily located.
-Requirement 6. /req/goodPractice/principles/addressing/sustainableAssignmentMethod
-Addressing shall be sustainable in the sense that additional addresses can be added without breaking the consistency of the address assignment method of existing addresses. -EXAMPLE 4 Leaving spaces between numbers when addresses are initially assigned makes it possible to assign additional addresses later when densification takes place. Alternatively, a number can be assigned based on the distance from an intersection of origin of the street.
-Requirement 7. /req/goodPractice/principles/addressing/pilotingAssignmentMethod
-The assignment method shall be piloted or tested before rolling it out on a larger scale. -TBC
-Requirement 8. /req/goodPractice/principles/addressing/deviceIndependence
-Unambiguous location of the object shall be possible without requiring the use of a digital device. -This requirement is necessitated, for example, in the case of an emergency when an object needs to be identified and located in the absence of connectivity (e.g., through signage when standing in front of it). -EXAMPLE 5 During the 2019-20 Australian wildfires there was widespread loss of connectivity due to direct fire damage to telecommunications infrastructure. This resulted in a prolonged loss of internet access to location information [e.g., address] which hampered firefighters who had to rely on radio (verbal) communication.
-Address elements in reverse allow gradually pinpointing of address -State à Locality à Road / Waterway à Number
-An address shall be unique -A sub address number shall be unique regardless of subaddress (unit) type or building level -An address shall be assigned a unique number in relation to the access throughfare -An address shall not contain two road names -Each address shall be assigned at least one geocode with coordinates
-Requirement 9. /req/goodPractice/principles/addressing/noPersonalInformation
-An address shall not include information about an individual or organization, owning the object to which it is assigned, or living and/or working at the object to which the address is assigned. -An address shall not include personal information related to a person or organisation that owns or occupies the address site (or object) to which the address is assigned.
-Requirement 10. /req/goodPractice/principles/addressing/dimensionsCongruentWithObjectives
-Addresses shall be of an address class with dimensions congruent with the context in which they are assigned and maintained, and with the objectives for which they are assigned and maintained. -TBC
-Requirement 11. /req/goodPractice/principles/addressing/suitableComponents
-The address components of an address class shall be suitable to meet the objectives for which that class is designed. -Each address shall be assigned a class as in https://linked.data.gov.au/def/address-classes, which use the components as laid out below. All addresses will be associated with an addressable object that has associated geometry, with, at a minimum, a geocode. Geocodes will be associated with a geocode type from https://linked.data.gov.au/def/geocode-types. All address components will be stored with lifecycle and provenance information. -Any address assigned to an object shall have a digital equivalent address record in the authoritative state and national address datasets . This record shall be updated whenever an address is assigned or changed .
-Thoroughfare
-Addresses in the Thoroughfare class specify a location by reference to a thoroughfare i.e. a road or water feature name. -All throughfare addresses shall comprise at a minimum the following components: -(a) Address number elements -(b) Thoroughfare name (road or water feature name ) and type elements -(c) Locality name -(d) State or territory name -The combination of these four components shall create a unique address, which reflects the point of access to the address site. -An address may also include the following additional components: -(a) Address site name -(b) Building name -(c) Landmark name -(d) Sub-address type -(e) Level type and number -(f) Postcode -(g) Country -(h) Indigenous country -An address shall be assigned to an addressable object. -In instances where an address site has more than one point of access, alternative addresses may be created to reflect the additional access points. These additional addresses shall be stored against the same addressable object. -An addressable object shall have at least one spatial geometry stored against it.
-======= Address number
-The designation and form of an address number is crucial in enabling an address site to be readily located by emergency service responders and service delivery providers. -An address number shall be assigned to each separately owned or occupied area of land, and each separately owned or occupied building or part of a building. The address number assignation method relates to the address class. For throughfare addresses, address numbers follow general and specific address class principles.
-======= General address numbering principles
-Address numbers shall be assigned prior to occupation and as early as practicable in the development process. -Address numbers shall be assigned according to the location of the point of access to the address site from the throughfare (road or water feature). -Address number allocation shall ensure clear, logical and unambiguous numbering: - Address numbers shall be sequential positive integers from lowest to highest, and continue for the entire length of the named road even when it continues across administrative boundaries. - The datum point for address numbering should be at the commencement of the road from where access to that road is most common, or is planned to occur, at the point of naming. This shall take into account assignation of reserved numbering requirements in a staged development. - A number range shall not be assigned as an address number. And existing ranges phased out. - A primary address number shall not be prefixed by alphabetical characters. - Primary address sites shall be numbered using odd numbers on the left of the throughfare and even numbers on the right . - Where there are no addresses numbers available for an address site due to existing allocations, alpha suffixes shall be assigned to the base number; with the exception that address sites that share access should be treated as sub-address sites. - Alpha suffixes shall start at A, be assigned incrementally in the same direction as the numbering of addresses on the throughfare, and not extend beyond E. - Renumbering of the road is required where there are more than five additional address sites requiring numbering in this way. - In instances where an existing address site uses the base number, this may be retained (i.e. not have a suffix) provided it is in order. - A lot number shall not be used in place of an address number. - Where a road is renamed as a result of redesign or development, address sites shall be renumbered if required to ensure adherence to this standard. - Where an area of rural numbering is reclassified as urban, previously assigned rural numbers should be retained if urban numbering requirements can be met for the infill addressing.
-======= Urban address numbering
-For addresses designated part of the urban address class, address numbers shall be reserved to meet potential future allocation needs, for example where there are unusually wide frontages or potential for infill development. -An address site on a corner shall be assigned both a number indicating the main point of access, and an address number on the other road assigned as an alternative address (if access exists), or be reserved for future development.
-======= Rural address numbering
-For addresses designated part of the rural address class, address numbering shall be determined by dividing the distance in metres from the datum point to the access point by ten, then rounding to the nearest odd number on the left or even number on the right side of the road (rural numbering method). -Address numbers shall not exceed five digits – for roads over 1000km long, address numbering shall be restarted at a different datum point, preferably a town, natural feature or major intersection, with numbering in the same direction. -In the absence of an access point, a rural number within the range determined by the rural numbering method may be assigned. The rural number shall be reassigned if an access point is subsequently created. -In areas with multiple address access points within the minimum step intervals of 20m, the distance criteria may be varied as long as the overall integrity of the rural numbering system is maintained. Alternatively, suffixes may be added in accordance with Section 7.2.1.1.1.1.
-======= Numbering for roads that cross both rural and urban areas
-If a road name continues across rural and urban extents, the rural numbering method should be utilised but may be varied as necessary in urban areas to ensure numbering remains logical and unique. -Where a highway crosses an urban area in which another local name is used, numbering shall relate to each named road, both in assignment methodology and extent. Rural numbering shall encompass distances including the sections with local names.
-======= Water address numbering
-Addresses fall under the class of water if the site cannot be accessed from a road, and is instead accessed from a water feature or island. -For addresses designated part of the inlet address class, inlet or bay address numbering uses the distance in metres from a datum point at one end of the inlet or bay, divided by ten, and rounded to the nearest number. -For addresses designated part of the island address class, numbering uses the distance in metres clockwise from a datum point, divided by ten, and rounded to the nearest number. -For addresses designated part of the river address class, river and creek address numbering uses the distance in metres upstream from a datum point (e.g. river mouth), divided by ten, and rounded to the nearest odd number on the true right and even number on the true left (i.e. to the direction in relation to the flow of the river).
-======= Sub-address numbering
-Sub-address numbering shall be used for address sites contained within other address sites e.g. an apartment block or marina. A sub-address may utilise either the primary or an alternative address for the parent site. -The sub-address number precedes the address for the parent site, and shall be formatted when used with a ‘/’ between the sub-address number and address number. -The sub-address number should be stored with the sub-address type from https://linked.data.gov.au/def/subaddress-types, although this does not have to be provided within an address string.
-======= Thoroughfare name
-======== Roads
-An address shall not include more than one road name. -A road name shall be short, clear and unambiguous, and meet national naming principles. It shall not be offensive, racist, derogatory or demeaning. -All formed roads, including private roads, that are generally open to the public or to services shall be named . -A named road shall include only one section navigable by vehicles (or pedestrians), unless separated by a median strip. -A road shall only have one name, other than part of a highway that is assigned a local name where it passes through a town or city. -An unbroken section of road crossing an administrative boundary shall retain the same name. -A road name shall consist of a name element followed by a road type. The accepted road types are in https://linked.data.gov.au/def/road-types. The road type shall reflect the function and characteristics of the road as described in the vocabulary. -A road named after 2011 should not have a cardinal indicator after the road type. For roads named prior to this, road suffixes should refer to https://linked.data.gov.au/def/road-suffixes. -The name element of a road name, regardless of road type, shall not be the same as, or similar in spelling or sound, to an existing road name in the same locality, an adjoining locality, or in the same local government area. -A road name should be enduring and changed only when necessary. A road name should be changed when redesign or redevelopment breaks the road extent into two or more segments so it is no longer contiguous.
-======== Water features
-For address sites accessed from the water and not accessible from a road, the throughfare component should refer to the water feature name. The name shall be acceptable to the applicable naming authority. -The water throughfare should indicate the type of geographical object from https://linked.data.gov.au/def/go-categories.
-======= Locality
-======== Naming
-A locality name shall be short, unique within the country, and assigned according to national naming principles. It shall not be offensive, racist, derogatory or demeaning. -A locality name should not be similar in spelling or sound to any other locality name with the country. -A dual or alternative name shall not be assigned to a locality. -A locality name should be enduring and changed only when necessary. -A locality name should not be substituted with a promotional name , neighbourhood, or regional name in an address. -A locality shall be assigned the geographical object category of https://linked.data.gov.au/def/go-categorieslocality.
-======== Boundaries
-Locality boundaries shall be clearly defined, not overlap, and be contiguous. A locality should not cross a Local Government boundary, and should be contained within, and not cross, state or territory boundaries. -When defining a locality boundary, the following should be considered: - A locality boundary should define a community of interest - Definite and distinguishable physical features or barriers should be used where appropriate e.g. creeks, rivers, ridgelines, centres of roads, railways. - The boundary should not, where possible, bisect properties in common ownership or land parcels. -A locality boundary should be enduring and changed only when necessary. However, these should be reviewed and amended where appropriate in areas subject to development.
-======= Landmark
-Addresses in the Landmark class specify a location by reference to a named landmark. A landmark is a relatively permanent feature of the manmade landscape that has recognizable identity within a particular cultural context . -All landmark addresses shall comprise the following components: -(a) Landmark Name -(b) Locality (or city/town) name -(c) State or territory name -Landmark addresses shall not include an address number or thoroughfare name, but should be linked to an associated throughfare address.
-Postal
-Addresses in the Postal class specify points of postal delivery which have no definite relation to the location of the recipient, such as post office boxes, overseas military addresses and general delivery offices. Postal addresses will follow the AS/NZS ISO 19160.4:2023 standard and components are not covered in this profile.
-5.2.2. Address Data Principles
- -Requirement 12. /req/goodPractice/principles/addressData/representsAddressInPhysicalWorld
-Address data shall represent the addresses assigned to objects in the physical world. -TBC
-Requirement 13. /req/goodPractice/principles/addressData/interoperability
-Address data shall be interoperable between public administration systems, such as the cadastre, population register or urban information systems. -TBC
-Requirement 14. /req/goodPractice/principles/addressData/dataMaintenance
-Address data shall be maintained through processes and systems that consider general purpose data management principles, as well as specific requirements due to the geospatial nature of address data. -An address shall be recorded with the location coordinates for the point or access from the thoroughfare to which it is addressed. -The recording of an alternative address shall enable it to be readily distinguished from the related primary address. -The recording of a sub-address and the recording of its primary address shall enable them to be readily related to each other. -Road and water feature names shall be recorded in relation to the localities they pass through. -Locality names shall be recorded in relation to the state/territory within which it is located. -Information about address components that are obsolete shall be retained within lifecycle information including dates. -The relationship between a new address and any address(es) that it replaces shall be recorded.
-Requirement 15. /req/goodPractice/principles/addressData/digitalMaintenance
-In the case of digital address data, the data shall be maintained in an address data management system with appropriate software solutions, such as spatial database management systems and/or geographic information systems. -TBC
-Recommendation 9. /rec/goodPractice/principles/addressData/conformsToISO19160-1
-Address data should conform to ISO 19160-1:2015, or a profile thereof. -TBC
-Recommendation 10. /rec/goodPractice/principles/addressData/conformsToISO19160-4
-For postal addressing, address data should conform to ISO 19160-4:2017, or a profile thereof. -TBC
-6. Governance Framework
-6.1. General
-6.1.1. Strategy
-Requirement 16 addrcm-req:strategy
A governance framework shall be guided by a strategy for assigning addresses to objects. The strategy shall be based on policies and guidelines.
-TBC
-6.1.2. Policies
-Requirement 17 addrcm-req:policies
A governance framework shall exercise authority and control over address assignment and maintenance through policies with well defined decision-making structures and procedures.
-TBC
-Recommendation 13 addrcm-req:policiesSupportObjectivesAndContext
The policies should support the objectives and context.
-TBC
-6.2. Addressing Stakeholders
-6.2.1. Identification
-Requirement 19 addrcm-req:identification
A governance framework shall identify the addressing stakeholders involved in the processes and decision-making related to assignment and maintenance of addresses.
-TBC
-6.2.2. Responsibilities
-Requirement 20 addrcm-req:responsibilities
A governance framework shall assign at least one responsibility to each stakeholder in the governance framework, and they shall be accountable for their responsibilities.
-TBC
-6.2.3. Mandates
-Requirement 21 addrcm-req:mandates
Assignment of responsibilities to stakeholders shall consider legal and other mandates. Responsibilities are assigned to each stakeholder in the governance framework based on the extent of the mandate of the respective stakeholders.
-TBC
-6.3. Processes
-6.3.1. Specification
-Requirement 24 addrcm-req:specification
A governance framework shall specify and coordinate the processes for assigning and maintaining addresses, as specified in 8.3.1, and if address data is maintained, it shall specify and coordinate the required processes related to address data, specified in 8.3.2. Each process comprises a series of tasks towards achieving a specified goal.
-TBC
-6.3.2. Tasks
-Requirement 25 addrcm-req:tasks
A governance framework shall assign at least one stakeholder to each task in a process.
-TBC
-6.3.3. Addressing Processes
-Initiation Process
-Requirement 26 addrcm-req:initiationProcess
A governance framework shall specify and coordinate a process for initiating the assignment or maintenance of an address.
-TBC
-Recommendation 14 addrcm-req:consultationProcess
A governance framework should specify and coordinate a process for consultation when new address component values are assigned or changed due to maintenance.
-TBC
-Purpose Values Process
-Requirement 27 addrcm-req:proposeValuesProcess
A governance framework shall specify and coordinate a process for proposing new values or changes to address components values.
-TBC
-Approval Process
-Requirement 28 addrcm-req:approvalProcess
A governance framework shall specify and coordinate a process for approving or rejecting the proposed new address assignment or changes to an address due to maintenance.
-TBC
-Annex B: Identifiers
-This section is normative
-Addressing information created in conformance with this standard MUST use identifiers that meet the following criteria:
--
-
-
-
Interpretable as IRIs, according to RFC3987
----
-
-
-
except where information is wholly nested within another object identified with an IRI, in which case local identifiers may be used
-
-
- -
-
-
-
Issued via a system- and organisation-independent mechanism designed for long-term identifier stability and operation
-
-
Identifiers for addressing information that meet these criteria MAY be used by implementing jurisdictions independently of one another or in a coordinated manner. Advice from the Australian Government Linked Data Working Group SHOULD be sought regarding technical aspects of these sorts of identifiers.
-Identifiers per Class
-Addressing information generated by processes conforming to this standard MUST conform to the Address Model ADDR2024. Information conforming to that model comprises instances of many different classes of object, such as Address, Addressable Object, Geocode, Concept and valid identifiers must be used for all of them.
Local Identifiers for nested objects
-IRIs must be used for all instances of classes and predicates required by the Address Model except for objects wholly nested within other objects identified with an IRI and where the nested object need never be referred to independently of the containing object.
-For example the Compound Name object of type Street First Number with value "72" within the address 72 Yundah St, Shorncliffe, QLD is relevant only to that address, so it MAY be identified with a local identifier.
In RDF data in the Turtle format, the object with value "72" that is nested within an Address with IRI <http://example.com/address/x> may be identified using a Blank Node like this:
<http://example.com/address/x>
- a addr:Address ;
- sdo:hasPart [
- a cn:CompoundName ;
- sdo:additionalType apt:numberFirst ;
- rdf:value 72
- ] ,
- # ... other parts of the address
-.In the example above, the Compound Name object within […] cannot be referenced outside its relation to the Address object.
Multiple identifier sources
-Identifiers for objects in each of the Address Model’s classes need not all come from the same system/owner. For example, a jurisdiction may create an identifier for an Address, individual parts of which are categorised according to the Address Part Types vocabulary which uses https://linked.data.gov.au/-based IRIs issued by the Australian Government Linked Data Working Group.
Bibliography
--
-
- ADDR2024 -
-
-
Intergovernmental Committee on Surveying & Mapping, Address Model (2024). https://linked.data.gov.au/def/addr
-
- - ISO10646 -
-
-
International Organization for Standardization, ISO/IEC 10646: Information technology — Universal coded character set (UCS). https://www.iso.org/standard/76835.html
-
- - ISO19160-1 -
-
-
International Organization for Standardization, ISO 19160-1: Addressing Part 1: Conceptual model (2015). https://www.iso.org/standard/61710.html
-
- - ISO19160-2 -
-
-
International Organization for Standardization, ISO 19160-2: Part 2: Assigning and maintaining addresses for objects in the physical world (2023). https://www.iso.org/standard/81674.html
-
- - RDF3987 -
-
-
Internet Engineering Taskforce, Internationalized Resource Identifiers (IRIs) (2005) https://datatracker.ietf.org/doc/html/rfc3987
-
- - RDF2119 -
-
-
Internet Engineering Taskforce, Key words for use in RFCs to Indicate Requirement Levels (1997) https://datatracker.ietf.org/doc/html/rfc2119
-
- - AS/NZS4819:2011 -
-
-
Standards Australia. AS/NZS 4819:2011 Rural and urban addressing. https://store.standards.org.au/product/as-nzs-4819-2011
-
- - ASNZSISO19160-4 -
-
-
Standards Australia. AS/NZS ISO 19160.4: Addressing, Part 4: International postal address components and template language (2023). https://store.standards.org.au/product/as-nzs-iso-19160-4-2023
-
- - RDF -
-
-
World Wide Web Consortium, RDF 1.1 Concepts and Abstract Syntax, W3C Recommendation (25 February 2014). https://www.w3.org/TR/rdf11-concepts/
-
- - TTL -
-
-
World Wide Web Consortium, RDF 1.1 Turtle Terse RDF Triple Language, W3C Recommendation (25 February 2014). https://www.w3.org/TR/turtle
-
-