Address details data dictionary

Guide for use:

The Address details data dictionary is one of a suite of data dictionaries based on the AS 4590—2006 Interchange of client information standard. This suite of data dictionaries is not limited to a specific data collection. The aim is to enable data developers to select appropriate data elements to use in meeting the needs of their data collection. These data dictionaries are:

• Party identifier details data dictionary
• Electronic contact details data dictionary
• Organisation details data dictionary
• Person details data dictionary

A table has been created to show the mapping between the data elements within the Address details data dictionary and the AS 4590—2006 Interchange of client information standard. See: Address details mapping

The AS 4590—2006 Interchange of client information standard recommends using a number of components for the following address items:

Primary address

Components of the primary address are:
(i) Address site (or Primary Complex) name.
(ii) Address number or number range.
(iii) Road name (name/type/suffix).
(iv) Locality.
(v) State/Territory.
(vi) Postcode (optional).
(vii) Country (if applicable).

Addressing within a complex

Complex addresses provide for the unique identification of secondary address sites within
a larger, primary address site. A complex address requires both parts (secondary and primary) to
provide unique definition.
Components of the secondary address are:
(i) Sub-dwelling (sub-complex) unit type and number or identifier.
(ii) Level type/level number (if applicable).
(iii) Private road number and Private road name or an equivalent identifier (if applicable).
(iv) Secondary Complex (or Utility) name (if applicable).
NOTE: Components (iii) and (iv) may be reversed where the sub-dwelling type/number is an
integral part of the Secondary Complex, e.g. an office within a building, or where the
secondary complex has no addressable sub-complex components and is unique to the private
road in question, e.g. the Sergeants Mess in an army barracks.

Geocode

A geocode describes the coordinates that define the position of an address point. Geocodes
apply to a variety of address sites and features. It caters for the needs of a variety of users,
with a particular focus on the needs of emergency and other essential service providers.
There are a number of elements needed to define a unique address geocode. Geocoded addresses fundamentally consist of coordinates associated with an address site
feature. The geocode component of an address site shall contain—
(a) the datum and coordinate system being used (usually as metadata);
(b) the coordinates; and
(c) the address site feature being referenced (by individual record).
The geocode component should also contain geocode accuracy (by individual record).

Note that users of latitude and longitude metadata may have different requirements. Therefore in addition to the latitude and longitude data elements using the decimal degrees representation, (based on the AS 4590 standard) two additional data elements have been created. These items use the traditional degrees, minutes and seconds representation, and are based on the AS 6709:2008 Standard representation of latitude, longitude and altitude for geographic point locations standard.

Standards Australia 2006. AS 4590—2006 Interchange of client information. Sydney: Standards Australia.

Standards Australia/Standards New Zealand 2008. AS/NZS ISO6709:2008—Standard representation of latitude, longitude and altitude for geographic point locations. Sydney/Wellington: Standards Australia/Standards NZ.

The addressing information interchange section of AS 4590 has been aligned with AS/NZS 4819, Geographic information—Rural and urban addressing. AS/NZS 4819 was compiled to direct authorities required to allocate physical addresses, whether they be to properties, features or facilities. This revision of AS 4590 has been extended to cater for new address provisions noted in AS/NZS 4819 and has been reviewed and amended to minimise ambiguity and maximise understanding in client data interchange.