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

https://linked.data.gov.au/def/addr-cm
(proposed)

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-11-05

Issued

0000-00-00

Creator

ICSM’s Addressing Working Group

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/icsm-au/addr-creation-maintenance

License

Creative Commons Attribution 4.0 International (CC BY 4.0)

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 AS/NZS 4819:2011 Rural and urban addressing. This standard does not apply to other address classes such as postal 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:

The following document defines the addressing model used for address records:

3.3. Terms & Definitions

access point

The position along a thoroughfare (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 address

an assigned address that refers to an alternative access point to an address site. Requires a preferred address to have been assigned. SOURCE: this standard

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

preferred address

the assigned address that is preferred for usage and refers to the main access point to an address site. SOURCE: this standard

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

an address number element that refers to a sub-address site. SOURCE: This standard>>

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

a road or named water feature from which an address site can be accessed. 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

addr

+https://linked.data.gov.au/def/addr/+

ICSM’s Address Model

addrcm

+https://linked.data.gov.au/def/addrcm/+

This Document

addreq

https://linked.data.gov.au/def/addrcm-req/

Address Creation & Maintenance Requirements Vocabulary

als

https://linked.data.gov.au/def/address-lifecycle-stage-type/

Address Lifecycle Stage Types vocabulary

apt

https://linked.data.gov.au/def/address-part-type/

Address Part Types vocabulary

asgsed3

https://linked.data.gov.au/dataset/asgsed3/

Australian Statistical Geographies Standard Dataset, Release 3

cn

https://linked.data.gov.au/def/cn/

Compound Naming Model

ex

http://example.com/

Generic examples

geo

http://www.opengis.net/ont/geosparql#

OGC GeoSPARQL

gt

http://www.opengis.net/ont/geocode-types/

Geocode types vocabulary

ls

https://linked.data.gov.au/def/lifecycle/

Lifecycle Model

owl

http://www.w3.org/2002/07/owl#

Web Ontology Language ontology

rdf

http://www.w3.org/1999/02/22-rdf-syntax-ns#

The RDF Concepts Vocabulary

rdfs

http://www.w3.org/2000/01/rdf-schema#

RDF Schema ontology

sdo

https://schema.org/

schema.org model

skos

http://www.w3.org/2004/02/skos/core#

Simple Knowledge Organization System (SKOS) ontology

time

http://www.w3.org/2006/time#

Time Ontology in OWL

xsd

http://www.w3.org/2001/XMLSchema#

XML Schema Definitions ontology

4. Introduction

This is a placeholder

  • abstract

  • purpose

  • history

  • big picture

  • doc structure

5. Usage Personas

People and organisations in Australia perform different roles with respect to address information. This section of this standard lists known personas - these people and organisation roles - and the next section lists common tasks that people and organisations with those roles play. Section X then describes how those tasks can be carried out to meet the requirements given in Annex A.

5.1. About Personas

5.2. Personas

5.2.1. Creator

Those with a role in creating addresses. This including assigning street numbers and approving road and locality names.

5.2.2. Aggregator

Those with a role in aggregating addresses and associated information. This may including collating addresses, assigning geocodes or other geometries, and running validation processes.

5.2.3. Distributor

Those with a role in distributing products and services centred around address data.

5.2.4. User

Those with a role in utilising address data, including address validation.

5.3. Agents with Personas

5.3.1. Creator

Agents who have a role as a creator of addresses in Australia include:

  • Local Government agencies

    • Address numbering in New South Wales, Queensland, South Australia, Tasmania, Western Australia

    • Road naming approval in Queensland (local government owned roads), South Australia, Tasmania, Western Australia

  • State / Territory Government agencies

    • Full address creation in Australian Capital Territory and Northern Territory

    • Locality naming in Queensland, Victoria, Western Australia

    • State controlled road naming in Queensland

    • Road name approval in New South Wales, Victoria

  • Developers (limited role)

    • Sub address numbering suggestions

    • Road name suggestions

5.3.2. Aggregator

Agents who have a role as an aggregator of addresses in Australia include:

5.3.3. Distributor

Agents who have a role as a distributor of addresses in Australia include:

5.3.4. User

Agents who have a role as a user of addresses in Australia include:

  • Government

  • Emergency services

  • Postal and delivery service providers

  • Utility providers

  • Location service providers

  • Insurers

  • The public

6. Common Tasks

This section describes the specific address information-related tasks that the personas listed in Usage Personas frequently carry out.

6.1. Creator Tasks

6.1.1. Creating a new address

6.1.1.1. General address principles

Addresses SHALL adhere to the Australian address model, which in turn conforms with ISO19160-1:2015.

An address SHALL be unique.

All addresses and address components SHALL be stored with lifecycle and provenance information, according to the lifecycle model.

Address creators SHALL allocate a class to each address, and assign the relevant address components according to that class.

Address creators SHALL use concepts from the relevant vocabularies to ensure data interoperability.

The relationship between a new address and any address(es) that it replaces SHALL be recorded.

6.1.1.2. Thoroughfare class addresses

Addresses in the thoroughfare class specify a location by reference to a thoroughfare i.e. a road or water feature name. An address SHALL NOT include more than one thoroughfare name.

All thoroughfare addresses SHALL comprise at a minimum the following components:

  1. Address number elements (which MAY include sub-adddress elements)

  2. Thoroughfare name (road or water feature name) and type elements

  3. Locality name

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

  1. Address site name

  2. Building name

  3. Landmark name

  4. Sub-address type

  5. Level type and number

  6. Postcode

  7. Country

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

Address number

An address SHALL be assigned a unique number in relation to the access thoroughfare.

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 class. For thoroughfare addresses, address numbers follow general and specific 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 thoroughfare (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 thoroughfare even when it continues across administrative boundaries.

  • A number range SHALL NOT be assigned as an address number. Any existing ranges SHOULD be phased out.

  • An address number SHALL NOT be prefixed by alphabetical characters.

  • Address sites SHALL be numbered using odd numbers on the left of the thoroughfare and even numbers on the right.

  • A lot number SHALL NOT be used in place of an address number.

  • For addresses that refer to a road:

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

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

Use of alpha suffixes:

  • 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 (see sub-address numbering).

    • Alpha suffixes SHALL start at A, be assigned incrementally in the same direction as the numbering of addresses on the thoroughfare, and SHALL 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.

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 use of alpha suffixes.

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 (sub-address sites).

Sub-address numbers SHALL be sequential positive integers from lowest to highest, expect when alpha characters are used according to the multi-level sub-address numbering method. A number range SHALL not be assigned as a sub-address number.

A sub-address number within a primary address site SHALL be unique regardless of sub-address type or building level.

The sub-address number SHOULD be stored with the sub-address type, although this does not have to be provided within a formatted address string.

The full address assigned to a sub-address site SHALL refer to the common thoroughfare access and may utilise either the preferred or an alternative address for the primary address site.

Within a formatted address string, the sub-address number precedes the address for the primary address site, and SHALL be formatted when used with a ‘/’ between the sub-address number and address number.

Multi-level sub-address numbering

Table 1. Level type codes
Code Level Type

B

Basement level

G

Ground level

LG

Lower-ground level

M

Mezzanine level

OD

Observation deck level

P

Parking level

PD

Podium level

RT

Rooftop level

UG

Upper-ground level

For multi-level buildings where sub-addresses need to be assigned, the sub-address number SHALL concate two parts:

  1. Alphanumeric characters to represent the level within the building, including a level type code (see code options) and/or level number

    • Where there are multiple levels for a particular building level type, a number MAY be added after the level type code.

    • Level numbers SHALL increase with height for all above ground levels

    • Level numbers SHALL increase with depth for all below ground levels

    • The ground level SHALL be assigned 'G' and SHALL NOT be assigned a '0' or '1'

  2. Two digits to uniquely refer to the address site on that level (between 01 and 99)

    • To be allocated in logical sequence to each address site

    • For address sites 1 to 9, a preceding zero will be added

    • In instances where insufficient numbers are available for all address sites on a level, an alternative method that ensures unique unambiguous numbering may be used.

Some examples include:

Thoroughfare Naming

Road Naming

A road name SHALL be associated with a road object.

A road name SHALL be short, clear and unambiguous, and meet relevant national and state or territory 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. The exception to this is a short private road or cul-de-sac from which five or less address sites can be accessed, and which has no proposal to be extended. In this instance it can be treated as a driveway and address numbers assigned in relation to the named road to which the driveway connects.

A road name should not be applied to an unformed designated section of road.

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 the road types vocabulary. 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 SHALL refer to concepts within the affixes vocabulary.

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 Feature Naming

For address sites accessed from the water and not accessible from a road, the thoroughfare component SHALL refer to the water feature name. The name SHALL be acceptable to the applicable naming authority.

A water feature name SHALL be associated with a geographical name object.

The water thoroughfare SHALL indicate the type of geographical object.

Locality Naming

Naming SHALL first and foremost adhere to the Australian principles for the consistent use of place names.

A locality name SHALL be short, unique within the country, and assigned according to national and state or territory naming principles. It SHALL NOT be offensive, racist, derogatory or demeaning.

A locality name SHALL 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 SHALL NOT be substituted with a promotional name, neighbourhood, or regional name in an address.

A locality SHALL be assigned the geographical object category of Locality.

6.1.1.3. Landmark class addresses

NB. THIS SECTION IS IN DRAFT AND SUBJECT TO CHANGE

Addresses in the landmark class specify a location by reference to a named landmark. A landmark is a relatively permanent feature of the man made landscape that has recognisable identity within a particular cultural context.

All landmark addresses SHALL comprise the following components:

  1. Landmark name

  2. Locality (or city/town) name N.B. What about areas outside of LGAs?

  3. State or territory name

Landmark addresses SHALL NOT include an address number or thoroughfare name, but SHOULD be linked to an associated thoroughfare address.

6.1.1.4. Postal class addresses

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 are covered by the AS/NZS ISO 19160.4:2023 standard and components are not covered in this standard.

6.1.2. Assignation of geometry

6.1.2.1. Address geometry

All addresses SHALL be associated with an addressable object that has associated geometry, with, at a minimum, a geocode. Geocodes SHALL be associated with a geocode type.

The coordinates of a geocode SHALL be accompanied by explanation of their coordinate reference system, such as the relevant EPSG code, and an indication of the positional accuracy.

Each sub-address SHALL preferably be assigned an individual geocode, or if not practicable, share a geocode assigned to the primary address site, preferred address, or alternative address.

Addresses SHOULD be associated with an addressable object that has associated area geometry.

An address SHALL NOT be assigned against non contiguous areas, other than in relation to two areas within the same complex e.g. a unit and an allocated garage or parking space within the same complex.

6.1.2.2. Thoroughfare geometry

A thoroughfare associated with a road object or geographical name object, SHALL have associated geometry.

A road object SHALL have, as a minimum, an approximal centre line geometry. The geometry SHALL be accompanied by explanation of the coordinate reference system, such as the relevant EPSG code.

6.1.2.3. Locality geometry

Each locality will have a defined areal extent and boundary. The geometry SHALL be accompanied by explanation of the coordinate reference system, such as the relevant EPSG code.

Locality boundaries SHALL be clearly defined, not overlap, and be contiguous. A locality SHALL NOT cross a Local Government boundary, and SHALL be contained within, and not cross, state or territory boundaries.

When defining a locality boundary, the following SHALL be considered:

  • A locality boundary SHOULD define a community of interest.

  • Definite and distinguishable physical features or barriers SHALL 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 SHALL be enduring and changed only when necessary. However, these SHOULD be reviewed and amended where appropriate in areas subject to development.

6.1.3. Updating an existing address

When updating an existing address, address creators should adhere to the principles outlined in the section relating to creating a new address.

Any amendments to an address should be recorded according to the address and lifecycle models, including lifecycle and provenance information.

6.1.4. Retiring an address

When an address is retired it SHALL be assigned a lifecycle status of retired, according to the lifecycle model.

Links SHALL be kept between any retired address and any address that replaces it.

6.1.5. Provision of address data

Address creators SHALL make address data available for address aggregators and/or address users.

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.

6.2. Aggregator Tasks

6.2.1. Consolidation of address data

Addresses provided by address creators SHALL be recorded according to the address and lifecycle models, including lifecycle and provenance information.

The address source SHALL be recorded, indicating the relevant address creator authority.

6.2.2. Validation of address components

Address aggregators SHALL validate address components against relevant vocabulary concepts to ensure data consistency.

6.2.3. Digital equivalent address record

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.

The address source SHALL be clearly articulated, indicating the relevant address creator authority.

6.3. Distributor Tasks

6.3.1. Provision of address data and products

Address distributors SHALL ensure attribute values correlate with relevant vocabulary concepts to ensure data consistency.

The address source SHALL be clearly articulated, indicating the relevant address creator authority.

The lifecycle stage of the address SHALL be indicated.

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.

6.3.2. Licence provision

Distributors SHALL specify the licences under which the address data is available and the terms and conditions for their use.

6.3.3. Metadata provision

Distributors SHALL provide relevant metadata.

6.3.4. Address validation services

Validation services SHALL only include addresses provided from authoritative sources.

Validation services SHALL only include results applicable to the relevant address class(es).

6.4. User Tasks

6.4.1. Address validation

Address data users SHALL validate addresses against authoritative address data.

6.4.2. Address signage

Signage enables address users to identify and locate address sites on the ground.

All signage should first and foremost comply with applicable standards, legislation and byelaws.

6.4.2.1. Locality name signs

Signage indicating the full unnabreviated locality name SHOULD be prominently displayed at significant boundary interfaces, particularly common traffic entry points.

6.4.2.2. Thoroughfare name signs

Signage indicating each road name SHALL be placed at each road intersection to clearly identify the road to which the name applies. This includes all named private roads, access ways, tracks and pedestrian-only roads. The sign should be easy to read, including at night.

The road name SHALL be in full with the exception of:

  • The road type MAY be abbreviated using the alternative labels identified in the road types vocabulary.

  • 'Mount' MAY be abbreviated to 'Mt' if required to keep sign length manageable.

Road name signs SHOULD include address number ranges applicable to the segment of road. The sign SHOULD physically indicate the associated road direction. The address numbers on the sign SHALL be aligned with the physical order of the numbering on the ground, from closest to furthest, even if thisreversed the number range.

Signage also SHOULD indicate any access restrictions, and MAY identify if a road is privately owned.

6.4.2.3. Address number signs

Every occupied address site SHALL display address number signage that clearly identifies the associated address site with the official allocated address number, and, if applicable, sub-address. Signage SHALL be unambiguous, and clearly legible from where the address site is normally accessed.

7. Requirements & Recommendations

7.1. Requirements

ID Label Definition

1

Objectives

A good practice shall specify one or more objectives for which addresses are assigned and shall be guided by these objectives

2

Context

A good practice shall specify the context in which the address assignment and maintenance takes place and shall be guided by this context

3

Context

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

4

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

5

Communication Through Physical Identifiers

A good practice shall specify how addresses will be communicated through physical identifiers

6

Sustainable Assignment Method

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

7

Piloting Assignment Method

The assignment method shall be piloted or tested before rolling it out on a larger scale

8

Device Independence

Unambiguous location of the object shall be possible without requiring the use of a digital device

9

No Personal Information

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

10

Dimensions Congruent With Objectives

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

11

Suitable Components

The address components of an address class shall be suitable to meet the objectives for which that class is designed

12

Represents Address In Physical World

Address data shall represent the addresses assigned to objects in the physical world

13

Interoperability

Address data shall be interoperable between public administration systems, such as the cadastre, population register or urban information systems

14

Data Maintenance

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

15

Digital Maintenance

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

16

Strategy

A governance framework shall be guided by a strategy for assigning addresses to objects. The strategy shall be based on policies and guidelines

17

Policies

A governance framework shall exercise authority and control over address assignment and maintenance through policies with well defined decision-making structures and procedures

18

Good Practice

A governance framework shall specify the good practice according to which addresses shall be assigned and maintained (see clause 8)

19

Identification

A governance framework shall identify the addressing stakeholders involved in the processes and decision-making related to assignment and maintenance of addresses

20

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

21

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

22

Resourcing

Stakeholders shall take responsibility for how they are funded, resourced and organized to fulfil their responsibilities in the governance framework

23

Sustainability

Funding and resourcing of stakeholders in a governance framework shall be sustainable, i.e., ongoing and able to be maintained in the long run

24

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

25

Tasks

A governance framework shall assign at least one stakeholder to each task in a process

26

Initiation Process

A governance framework shall specify and coordinate a process for initiating the assignment or maintenance of an address

27

Purpose Values Process

A governance framework shall specify and coordinate a process for proposing new values or changes to address components values

28

Approval Process

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

29

Announcement Process

A governance framework shall specify and coordinate a process for the announcement of a newly assigned address or changes to an address due to maintenance

30

Communication Process

A governance framework shall specify a process for communicating addresses in the physical world, following approval of assignment or maintenance of an address

31

Update Process

A governance framework shall specify and coordinate a process for updating the authoritative dataset after approval of assignment or maintenance of an address

32

Distribution Process

A governance framework shall specify and coordinate a process for making address data available after an update to the authoritative dataset

7.2. Recommendations

ID Label Definition

1

Objectives For Public Good

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

2

ISO 19160-1 Profile

The conceptual model that describes classes (types) of addresses assigned and maintained through the good practice should conform to ISO 19160-1:2015

3

Intellectual Property Rights

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.

4

Facilitate Assignment

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

5

Keeping Address Data In Synch

A good practice should specify a method for keeping addresses in the physical world in synch with address data.

6

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

A thoroughfare address shall be assigned that conforms to the list of mandatory components to enable unambiguity, and enable it to be readily located.

7

Equivalent Digital Record

TODO: add definition

8

Update Address Data

TODO: add definition

9

Conforms To ISO 19160-1

Address data should conform to ISO 19160-1:2015, or a profile thereof

10

Conforms To ISO 19160-4

For postal addressing, address data should conform to ISO 19160-4:2017, or a profile thereof

11

Conforms To ISO 19160-3

The quality of address data should be described conformant to ISO 19160-3:2020, or a profile thereof

12

Sharing

In the case of digital address data, the data should be shared through address retrieval solutions that preserve and maintain data integrity, e.g., through spreadsheets or APIs

13

Policies Support Objectives And Context

The policies should support the objectives and context

14

Consultation Process

A governance framework should specify and coordinate a process for consultation when new address component values are assigned or changed due to maintenance

Annex B: Identifiers

This section is normative

Addressing information created in conformance with this standard MUST use identifiers that meet the following criteria:

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

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

Annex C: Relevant Vocabularies

Vocabularies relevant to addresses

Vocabularies relevant to roads

Vocabularies relevant to geographic names (including locality)

Bibliography

ADDR2024

Intergovernmental Committee on Surveying & Mapping, Address Model (2024). https://linked.data.gov.au/def/addr

Addressing 2035 Strategy

Intergovernmental Committee on Surveying and Mapping. Addressing 2035 Strategy (2021). https://www.icsm.gov.au/publications/addressing-2035-strategy

Addressing 2035 Strategy Technical Addendum

ICSM. Addressing 2035 Strategy Technical Addendum (2021). https://www.icsm.gov.au/publications/addressing-strategy-information-addendum

AS 4590.1:2017

Standards Australia. Interchange of client information, Part 1: Data elements and interchange formats (2017). https://store.standards.org.au/product/as-4590-1-2017

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/NZS 4819: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