G-NAF Product Description

Product:

Prepared: February 2016

Data Product Description

Standard

This document is based on the AS/NZS ISO 19131:2008 Geographic information Data product specifications standard. For more information, refer to www.saiglobal.com/online.

Acknowledgements PSMA Australia acknowledges the assistance of CGI Group Inc. & Geometry Pty Ltd in the preparation of this guide.

Disclaimer PSMA Australia believes this publication to be correct at the time of printing and does not accept responsibility for any consequences arising from the use of information herein. Readers should rely on their own skill and judgement to apply information to particular issues. This work is copyright. Apart from any use as permitted under the Copyright Act 1968, no part may be reproduced by any process without prior written permission of PSMA Australia Limited.

PAGE i

Contents 1. Overview ......................................................................................................................................... 1

1.1 Data product specification title .................................................................................................. 1 1.2 Reference date .......................................................................................................................... 1 1.3 Informal description of the data product.................................................................................... 1 1.4 Responsible party ..................................................................................................................... 1 1.5 Language .................................................................................................................................. 1 1.6 Topic category ........................................................................................................................... 1 1.7 Distribution format ..................................................................................................................... 1 1.8 Terms and definitions ................................................................................................................ 1 1.9 Abbreviations and acronyms ..................................................................................................... 4 1.10 Addressing standards ............................................................................................................... 5

2. Specification Scope ........................................................................................................................ 6 2.1 Scope identification ................................................................................................................... 6

3. Data Product Identification .............................................................................................................. 7 3.1 Title............................................................................................................................................ 7 3.2 Alternate titles ........................................................................................................................... 7 3.3 Abstract ..................................................................................................................................... 7 3.4 Purpose ..................................................................................................................................... 7 3.5 Topic category ........................................................................................................................... 7 3.6 Geographic description ............................................................................................................. 8

4. Data Content and Structure .......................................................................................................... 10 4.1 Feature-based data ................................................................................................................. 10 4.2 Feature-based application schema (data model) ................................................................... 10 4.3 Data dictionary ........................................................................................................................ 10 4.4 Feature-based content scope ................................................................................................. 10

5. Reference System ........................................................................................................................ 11 5.1 Spatial reference system ........................................................................................................ 11 5.2 Temporal reference system .................................................................................................... 11 5.3 Reference system scope ........................................................................................................ 11

6. Data Quality .................................................................................................................................. 12 6.1 Positional accuracy ................................................................................................................. 12 6.2 Attribute accuracy ................................................................................................................... 12 6.3 Logical consistency ................................................................................................................. 12 6.4 Completeness ......................................................................................................................... 12

7. Data Capture ................................................................................................................................. 14 7.1 Data capture scope ................................................................................................................. 14

PAGE ii

8. Data Maintenance ......................................................................................................................... 15 8.1 Pre-processing ........................................................................................................................ 15 8.2 G-NAF maintenance software ................................................................................................. 16 8.3 Update frequency .................................................................................................................... 22 8.4 Maintenance scope ................................................................................................................. 22

9. Data Product Delivery ................................................................................................................... 23 9.1 Open Data Delivery format information ............................................................................... 23 9.2 PSMA Partner Network Delivery format information ............................................................ 23 9.3 Organisation responsible for delivery...................................................................................... 24

10. PSMA Data ................................................................................................................................... 25 Appendix A Addressing standards and NAMF relationship ............................................................... 26 Appendix B G-NAF Data Model ......................................................................................................... 28 Appendix C Data Dictionary ............................................................................................................... 30

PAGE iii

Tables Table 1: Relationship between G-NAF, AS4590 and NAMF fields ....................................................... 26 Table 2: ADDRESS_ALIAS ................................................................................................................... 30 Table 3: ADDRESS_ALIAS_TYPE_AUT .............................................................................................. 31 Table 4: ADDRESS_ALIAS_TYPE_AUT .............................................................................................. 31 Table 5: ADDRESS_DETAIL................................................................................................................. 31 Table 6: PRIMARY_SECONDARY ....................................................................................................... 34 Table 7: PS_JOIN_TYPE_AUT ............................................................................................................. 35 Table 8: PS_JOIN_TYPE_AUT Codes ................................................................................................. 35 Table 9: ADDRESS_MESH_BLOCK_2011 .......................................................................................... 35 Table 10: MB_MATCH_CODE_AUT ..................................................................................................... 36 Table 11: MB_MATCH_CODE_AUT Codes ......................................................................................... 36 Table 12: ADDRESS_SITE ................................................................................................................... 36 Table 13: ADDRESS_SITE_GEOCODE ............................................................................................... 37 Table 14: ADDRESS_TYPE_AUT ........................................................................................................ 38 Table 15: ADDRESS_TYPE_AUT Codes ............................................................................................. 38 Table 16: FLAT_TYPE_AUT ................................................................................................................. 39 Table 17: FLAT_TYPE_AUT Codes ...................................................................................................... 39 Table 18: GEOCODE_RELIABILITY_AUT ........................................................................................... 40 Table 19: GEOCODE_RELIABILITY_AUT codes ................................................................................. 41 Table 20: GEOCODE_TYPE_AUT ....................................................................................................... 41 Table 21: GEOCODE_TYPE_AUT Codes ............................................................................................ 41 Table 22: ADDRESS_DEFAULT_GEOCODE ...................................................................................... 42 Table 23: GEOCODED_LEVEL_TYPE_AUT........................................................................................ 43 Table 24: GEOCODED_LEVEL_TYPE_AUT Codes ............................................................................ 43 Table 25: LEVEL_TYPE_AUT ............................................................................................................... 43 Table 26: LEVEL_TYPE_AUT Codes ................................................................................................... 44 Table 27: LOCALITY_CLASS_AUT ...................................................................................................... 44 Table 28: LOCALITY_CLASS_AUT Codes ........................................................................................... 44 Table 29: LOCALITY ............................................................................................................................. 45 Table 30: LOCALITY_ALIAS ................................................................................................................. 46 Table 31: LOCALITY_ALIAS_TYPE_AUT ............................................................................................ 46 Table 32: LOCALITY_ALIAS_TYPE_AUT Codes ................................................................................. 47 Table 33: LOCALITY_NEIGHBOUR ..................................................................................................... 47 Table 34: LOCALITY_POINT ................................................................................................................ 47 Table 35: MB_2011 ............................................................................................................................... 48 Table 36: STREET_CLASS_AUT ......................................................................................................... 48 Table 37: STREET_CLASS_AUT Codes .............................................................................................. 48

PAGE iv

Table 38: STREET_TYPE_AUT ............................................................................................................ 49 Table 39: STREET_TYPE_AUT Codes ................................................................................................ 49 Table 40: STREET_LOCALITY ............................................................................................................. 53 Table 41: STREET_LOCALITY_POINT ................................................................................................ 54 Table 42: STREET_LOCALITY_ALIAS ................................................................................................. 54 Table 43: STREET_LOCALITY_ALIAS_TYPE_AUT ............................................................................ 55 Table 44:STREET_LOCALITY_ALIAS_TYPE_AUT Codes ................................................................. 55 Table 45: STREET_SUFFIX_AUT ........................................................................................................ 55 Table 46: STREET_SUFFIX_AUT Codes ............................................................................................. 56 Table 47: STATE ................................................................................................................................... 56 Table 48: APPLIED GEOCODE PRIORITY ORDER ............................................................................ 57

PAGE v

1. Overview 1.1 Data product specification title G-NAF Product Description

1.2 Reference date February 2016

1.3 Informal description of the data product G-NAF (Geocoded National Address File) is a trusted index of Australian address information. It contains the state, suburb, street, number and coordinate reference (or geocode) for street addresses in Australia. G-NAF does not contain any personal information or details relating to an individual or business. G-NAF uses existing and recognised address sources (referred to as contributors) from the state and territory government land records and Commonwealth government agencies. A rigorous process is used that involves textual address comparison, matching and geospatial validation to provide both national consistency and national coverage.

1.4 Responsible party PSMA Australia Limited (PSMA) Level 2, 113 Canberra Avenue, GRIFFITH ACT 2603 Australia T: +61 2 6260 9000 | F: +61 2 62029001 | E: [email protected] URL: http://www.psma.com.au | ABN: 23 089 912 710

1.5 Language English

1.6 Topic category Address files for urban, rural and locality areas within Australia.

1.7 Distribution format PDF

1.8 Terms and definitions The following table lists the terms and definitions that are used by PSMA. This list defines some of the terms used for G-NAF, but is not necessarily the same definition as used by others.

Term Definition

Address A structured label for any place that could deliver or receive a good or service.

Address Contributor Supplier of address information to G-NAF.

Address Level Geocode An address in G-NAF that has a parcel level geocode (i.e. a geocode reliability code of 2). Also referred to as a parcel level address

Alias Address (or Alternate Address)

Another label for a Principal Address which may differ because of a variation in some or all address components (i.e. numbers, levels, street name, locality name). An Alias Address will share the same location as the Principal Address. Association with Principal Address may be provided by an Address Contributor or determined programmatically.

Building Name A building or property name that is associated with an address. The name is typically free text and is not unique to any address.

PAGE 1

Term Definition

Class Description of a set of objects that share the same attributes, operations, methods, relationships, and semantics [UML]. Note: A class does not always have an associated geometry (e.g. the metadata class).

Confidence Level G-NAF is currently built from three national address datasets. The confidence level of an address indicates the level of usage of each address by the contributor address datasets.

Contributor Data Address datasets held and maintained by organisations external to PSMA that is being made available for the purpose of building and maintaining G-NAF.

Event Characteristic of a feature measured within an object without modifying the associated geometry.

Feature Abstraction of real world phenomena. Feature Attribute Characteristic of a feature (e.g. name of an area). Gap Geocode A geocode created programmatically based on address ranging in the absence of a

geocode being allocated to a specific property. This geocode may not necessarily lie within a property polygon.

Geocode A point feature for an address spatially defined by a coordinate. In G-NAF an address may have multiple geocodes representing various real world features (e.g. parcel, property, building centroid, street centroid, locality centroid etc.) associated with a physical address. The geographic coordinates are expressed as latitude/longitude in decimal degrees.

Geocode Level Type The geocode level type indicates which geocodes have been assigned to an address. Every address within G-NAF must have a locality level geocode. Addresses may also have a street level geocode and a parcel level geocode.

Geocode Priority G-NAF is able to assign multiple geocodes to an address. The geocode priority is a priority order established by PSMA to enable a default geocode to be assigned to each address which represents the geocode of the highest precision currently assigned to an address.

Geocode Reliability Refers to the geocode precision and is linked to how the geocode was generated.

G-NAF Merge Criteria Those components of an address string used by the G-NAF process to uniquely identify an address.

Jurisdiction Reference to a State or Territory Government.

Locality A named geographical area defining a community or area of interest, which may be rural or urban in character. Usually known as a Suburb in an urban area. The localities used in G-NAF are the gazetted localities as provided by the respective jurisdictions.

Locality Alias Another recognised name for a gazetted locality name. Could be misspellings, historic authoritative names or unauthoritative names.

Other Territories Refers to external Territories of Australia included within the PSMA datasets: Christmas Island, Cocos (Keeling) Islands, Norfolk Island and Jervis Bay.

Mesh Blocks Mesh Blocks are the smallest geographic region in the Australian Statistical Geography Standard (ASGS), and the smallest geographical unit for which Census data is available.

Object Entity with a well-defined boundary and identity that encapsulates state and behaviour [UML Semantics] Note: An object is an instance of a class.

Package Grouping of a set of classes, relationships, and even other packages with a view to organising the model into more abstract structures.

Postcodes Postcodes are allocated to geographic areas to facilitate the efficient processing and delivery of mail.

Primary Postcodes Primary postcodes are unique integers based on the postcodes used to differentiate between gazetted localities within a jurisdiction that share the same name. They may not necessarily be coincident with the postcode for any area.

Primary Address A Primary Address is a principal address that contains all the components of an address except flat number information. Where flat number information exists for an address then this forms part of a Secondary Address and a linkage made to the Primary Address. Alternatively a Primary Address can be linked to one or more Secondary Addresses by PSMA where identified by an address contributor (e.g. involves private road in complex development, public housing estates etc.)

Principal Address Accepted label for an Address which may have zero, one or more than one associated Alias Address.

PSMA Online Data Delivery System

A suite of applications to store, quality assure and distribute PSMAs datasets.

Reference Data Each address entering G-NAF is tested for to ensure it can be matched against the geospatial region to which it relates: state, locality and street. The datasets used for this geospatial verification are: National Road Centreline Dataset (PSMA Transport & Topography)

PAGE 2

Term Definition Gazetted Locality Boundaries for Australia (PSMA Administrative Boundaries). These two datasets are commonly referred to as the Reference Data.

Rules Rules are at times applied to contributor addresses as part of the G-NAF processing where errors are identified in the addresses such as the incorrect spelling of street names, incorrect street types or incorrect localities. The application of these rules generates alias street localities or localities depending on the rule applied.

Secondary Address A Secondary Address is any address with flat number information or more literally any address where flat_number_prefix, flat_number or flat_number_suffix is not null. Alternatively, a Secondary Address can be linked to a Primary Address by PSMA where identified by an address contributor (e.g. involves private road in complex development, public housing estates etc.).

Street (or Road) An in-use name for a street name that exists within PSMAs National Road Centreline Dataset (i.e. reference dataset) within PSMAs Transport & Topography.

Street Locality A Street or Road within a particular Locality e.g. Smith St Melbourne VIC 3000. A street is unique to a locality. If it crosses a locality boundary, that segment receives a different street_locality_pid and treated as another street.

Street Locality Alias A Street or Road within a particular Locality that is an alternative name for a Street Locality Address.

Street Alias In use name for a Street name not existing within PSMAs Road centreline dataset (i.e. reference dataset).

Quality Data is of the highest quality reflective at the time and fields provided. Key factors are timeliness, consistency and completeness.

PAGE 3

1.9 Abbreviations and acronyms Term Definition

ABS Australian Bureau of Statistics

ASGC Australian Standard Geographical Classification

ASGS Australian Statistical Geography Standard

AS4590:2006 Data interchange standard

AS/NZS 4819:2011 Rural and urban addressing standard

CD Collection Districts (for Census collection)

DPS Data Product Specification

FOI Features of Interest

GDA94 Geocentric Datum of Australia 1994

GIDB A copy of the IDB for use in Data Maintenance in Radius Studio

G-NAF Geocoded National Address File

GCCSA Greater Capital City Statistical Areas

IARE Indigenous Areas

ILOC Indigenous Localities

IREG Indigenous Regions

ICSM Intergovernmental Committee on Surveying & Mapping

IDB Integrated Database

IUF Incremental Update File

MB Mesh Blocks

NAMF National Address Management Framework

PID Persistent Identifier

SEB State/Territory Electoral Boundaries

SLA Statistical Local Area

UCL Urban Centre Localities

UML Unified Modelling Language

UUID Universal Unique Identifiers

PAGE 4

1.10 Addressing standards Australia has two national standards applicable to addressing:

AS/NZS 4819:2011 Geographic informationRural and urban addressing AS4590:2006 Interchange of Client Information.

About AS/NZ 4819:2011 The standard AS/NZ 4819:2011 is intended for use by agencies that are responsible for addressing. The goal of AS/NZ 4819:2011 is to specify requirements for assigning addresses that can be readily and unambiguously identified and located. In order to achieve this goal, the objectives of the standard are:

Localities are to enable addresses to be uniquely and clearly identified Assigned names for roads or other primary means of access enable addresses to be

readily and uniquely identified Assigned address numbering enables address sites to be readily located Signage enables assigned addresses to be readily identified and located Address information enables sites to be readily located.

About AS4590:2006 The standard AS4590:2006 sets out requirements of data elements for the interchange of client information. There are a number of elements specific to addressing. As G-NAF contains both old and new addresses, it is more closely related to the structure in AS4590:2006.

About the National Address Management Framework In addition, the National Address Management Framework (NAMF) has been developed as a national, coordinated approach to address management. It is a consistent, standards-based framework which will guide the process for verifying addresses and provide a standard for exchange of address data. Appendix A sets out the relationship between G-NAF, AS450:2006 and NAMF fields.

PAGE 5

2. Specification Scope There is a defined scope for Feature Based Content, Reference Systems, Data Quality, Data Capture and Data Maintenance regarding the data accuracy, geometry, metadata and temporal considerations of the data release cycle.

2.1 Scope identification

Level Dataset

Level name G-NAF

Extent Spatial coverage of Australias land mass including External Territories.

PAGE 6

3. Data Product Identification 3.1 Title G-NAF

3.2 Alternate titles G-NAF for Australia Geocoded National Address File Geographic National Address File Open G-NAF

3.3 Abstract The G-NAF Product Description (an ISO 19131 compliant description) provides an optimised quality geometric description and a set of basic attributes of the Address Index for Australia. G-NAF incorporates all addresses included in contributors data that are regarded as complete addresses. G-NAF data is revised on a regular basis.

3.4 Purpose Addresses were once exclusively related to properties (e.g. where a bill should be sent for a utility service or rates notice). In a digital world, the use and purpose of addressing has changed. Addresses are now used to label land parcels and properties as well as for locating assets such as ATMs, tree plantations, reserves and substations. Official addresses may be considered as those that are recognised and recorded by an authoritative body such as a land agency. In addition to official addresses, there are also unofficial or in-use addresses that may exist and be widely used and recognised by the community. Addressing is not always simple and can be extremely challenging and complex.

3.5 Topic category G-NAF: Addresses defined by coordinate spatial data (latitude and longitude) with associated textual metadata.

PAGE 7

3.6 Geographic description The G-NAF dataset covers the addresses within the complete national geography of Australia (AUS). The Bounding Box for this data is as follows;

North bounding latitude: -8

South bounding latitude: -45

East bounding longitude: 168

West bounding longitude: 96

This area covers the land masses of Australia, including External Territories and offshore islands (Christmas Island, Cocos (Keeling) Islands, and Norfolk Island). The spatial domain is described by the polygon:

PAGE 8

Geographic extent name AUSTRALIA INCLUDING EXTERNAL TERRITORIES AUS Australia Australia The States and Territories within Australia are represented by the following:

State or Territory Name Abbreviation Character Code

New South Wales NSW 1 (or 01)

Victoria VIC 2 (or 02)

Queensland QLD 3 (or 03)

South Australia SA 4 (or 04)

West Australia WA 5 (or 05)

Tasmania TAS 6 (or 06)

Northern Territory NT 7 (or 07)

Australian Capital Territory ACT 8 (or 08)

Other Territories OT 9 (or 09)

Note: PSMA has aligned Other Territories (OT) with the Australian Bureau of Statistics (ABS). It includes the Territory of Christmas Island, Territory of Cocos (Keeling) Islands, Jervis Bay Territory and more recently the inclusion of Norfolk Island. OT does not include any other external Territory.

PAGE 9

4. Data Content and Structure G-NAF is a feature-based product. A data model is included (Appendix B) with an associated data dictionary (Appendix C).

4.1 Feature-based data Data types and codes are derived from the address standard where applicable. However, in some cases the codes have been extended to handle exceptional cases. The data model is hierarchical in nature, storing information about streets and localities separate from address sites. Alias addresses are stored in the same way as principal addresses. There is simply a mapping table provided to determine which address is an alias of which principal address.

4.2 Feature-based application schema (data model) The G-NAF data model is set out in Appendix B.

4.3 Data dictionary The G-NAF feature catalogue in support of the application schema is provided in Appendix C. Spatial attributes are added to the feature catalogue in the same manner as other attributes for completeness and conformance to the application schema.

4.4 Feature-based content scope All geometry and metadata for points within G-NAF.

PAGE 10

5. Reference System 5.1 Spatial reference system GDA 94

5.2 Temporal reference system Gregorian calendar

5.3 Reference system scope The spatial objects and temporal collection periods for G-NAF.

PAGE 11

6. Data Quality 6.1 Positional accuracy G-NAF is a concerted effort to deliver the best possible geocoded national address dataset for Australia. The magnitude of this dataset, the complexity of its content, and the multiplicity of its sources, means that there is ongoing requirement to improve the content, quality and coverage of G-NAF. All addresses in G-NAF contain a locality geocode. This geocode will generally be at the centre of the locality. If the name of the street in the address can be matched to one in the locality, then another geocode is added at the centre of the street within that locality. This is generally referred to as the street locality geocode. If the address is provided with coordinates or can be matched to one that already exists, then a third geocode will be added, placing the address inside the relevant property. This is generally referred to as the address site geocode.

6.2 Attribute accuracy Attribute accuracy is determined from rigorous standardisation processes and matching of the contributor datasets together with matching of addresses against the gazetted localities from PSMAs Administrative Boundaries and the roads layer of PSMAs Transport & Topography dataset.

Address mesh block integration G-NAF has a mesh block ID allocated to every address, where available. This includes addresses that have a geocode allocated at a street-locality and locality level where a single mesh block cannot be identified. A coding table (MB_MATCH_CODE_AUT) lists the codes describing the level of matching to mesh blocks. The ABS recommends that G-NAF addresses associated with locality (and street) level geocode locations be associated with SA2 level units (ASGS units built up from SA2s). While there is a strong alignment between gazetted suburb and locality boundaries, there are situations where SA2 boundaries split localities. In these circumstances, an unknown proportion of the addresses associated with the locality centroid will be coded to an incorrect SA2.

Allocation of postcodes Postcodes are included in G-NAF at the address record level (i.e. postcode field in the respective address_detail tables). The postcodes used are derived where possible from contributor data. Where the postcode is not available from a contributor it is validated via a spatial intersection from a PSMA created (and maintained) postcode polygon dataset with boundary information sourced from the Commonwealth. The supplied boundaries has been realigned to be consistent with the PSMA locality boundaries. Postcodes are allocated to geographic areas to facilitate the efficient processing and delivery of mail. There is no mandatory requirement for inclusion of a postcode in an address.

6.3 Logical consistency The dataset data structure has been tested for conformance with the data model.

6.4 Completeness Completeness is an assessment of the extent and range of the dataset with regard to completeness of coverage, completeness of classification and completeness of verification. The Data Maintenance

PAGE 12

section provides more information about the completeness of the dataset based on the processing steps.

Dataset coverage National

Features

Addresses included G-NAF aims to include all physical addresses in circulation by using multiple sources. The physical addresses in G-NAF are used to label land parcels and properties as well as for locating assets such as ATMs, tree plantations, reserves and substations.

Attribute completeness All mandatory attributes for each object are populated. Some attributes are not populated but have been included in the data model to assist with the alignment with relevant standards. The process of collating addresses varies across the contributors supplying data to G-NAF. Therefore, the attributes supplied can vary, but PSMA will attempt to populate attributes based on the available information from the contributors.

Quality scope The attribute accuracy is in scope for all areas in G-NAF.

PAGE 13

7. Data Capture Data is contributed to G-NAF by organisations including the mapping agencies and land registries of each of the state and territory governments, and Commonwealth government agencies.

7.1 Data capture scope Data for changed objects within the current release time period.

PAGE 14

8. Data Maintenance Maintenance activities are triggered by PSMA receiving updated address data from data contributors according to an agreed delivery schedule. At present, this schedule defines a quarterly update process. During the maintenance phase, contributed addresses are analysed and compared to existing records in G-NAF. This analysis and comparison gives rise to new records being inserted and existing records being updated or retired. The following diagram of the G-NAF Maintenance Process provides a high-level view of the G-NAF system including G-NAF maintenance pre-processing, the use of reference data files, G-NAF maintenance software and G-NAF outputs.

G-NAFMaintenance

Pre-ProcessingRule Generation

G-NAFMaintenance

Software see belowLog Files

PSMAGeocoded National Address File

(G-NAF)Database

Data Extraction G-NAF DataReports

ReferenceData FilesReferenceData FilesReferenceData Files

ContributorData FilesContributorData FilesContributorData Files

8.1 Pre-processing The G-NAF maintenance pre-process takes the input files from the PSMA reference datasets and contributor data and performs processing prior to data being processed by the G-NAF maintenance software. Pre-processing is used to describe the following activities:

Mapping from the contributor model to G-NAF model (with parsing as necessary) Application of rules that make corrections to misspellings, abbreviations and erroneous

characters

PAGE 15

Application of updates to suburb data and road names propagating the changes through all affected parts of the data.

Data structure of an address For an address to be included in G-NAF, it must be a complete entry. Complete equals:

Must include a matched locality Must include a street name Must contain either a valid number_first or a lot number.

Reference datasets G-NAF is a dataset which is reliant on other PSMA datasets. Below is a diagram which displays that relationship and order of production cycle for the release of PSMA datasets. PSMAs Administrative Boundaries and PSMAs Transport & Topography datasets need to be completed before G-NAF production can commence.

8.2 G-NAF maintenance software The G-NAF maintenance software receives the data from the pre-process phase. All the contributed addresses from each jurisdiction are cleansed, compared and merged into the normalised G-NAF maintenance model.

Processing The core maintenance processing consists of the following:

Address scrubbing State-Locality validation and geocoding Street validation Street geocoding Address geocoding Merging (merge criteria and confidence levels)

A further series of processing occurs for the following steps: Post merge processing (including validation processes) Primary / Secondary maintenance Alias / Principal maintenance

PAGE 16

Geocode maintenance Update address attributes (update attributes not in core processing) Update address links (i.e. contributor mapping, mesh blocks, default geocode) Verify G-NAF data (i.e. conformance with data model) Data export to integrated maintenance database.

Geocoding Multiple geocodes and multiple types of geocodes can be stored for each address. All geocodes are stored in G-NAF in the GDA94 spatial reference system. While this capability exists in the G-NAF model, addresses with multiple geocodes only exist for some addresses at this stage.

Geocode level type Every address within G-NAF must have a locality level geocode. Iit may also have a street level geocode and a parcel level geocode. The table GEOCODE_LEVEL_TYPE_AUT indicates which of these geocode level types are associated with an address in accordance with the table below:

Geocode_Level_Type Description

0 No Geocode

1 Parcel Level Geocode Only (No Locality or Street Level Geocode)

2 Street Level Geocode Only (No Locality or Parcel Level Geocode)

3 Street and Parcel Level Geocodes (No Locality Geocode)

4 Locality Level Geocode Only (No Street or Parcel Level Geocode) 5 Locality and Parcel level Geocodes (No Street Level Geocode)

6 Locality and Street Level Geocodes (No Parcel Level Geocodes)

7 Locality, Street and Parcel Level Geocodes

Note: LEVEL_GEOCODED_CODE field within the ADDRESS_DETAIL table refers to the CODE field within the GEOCODE_LEVEL_TYPE_AUT.

Geocode reliability Reliability of a geocode refers to the geocode precision and is linked to how the geocode was generated. Every geocode in G-NAF has a reliability level. The levels and their descriptions are stored in the table GEOCODE_RELIABILITY_AUT. These descriptions together with examples are given in the table below.

Reliability Level

Description Example

1 Geocode resolution recorded to appropriate surveying standard

Address level geocode was manually geocoded with a GPS

2 Geocode resolution sufficient to place geocode within address site boundary or access point close to address site boundary

a) Address level geocode was calculated as the geometric centre within the associated cadastral parcel

b) Geocode for access point identified for a rural property c) Calculated geocode based on centre setback from road

within cadastral parcel d) Geocode for approximate centre of building

3 Geocode resolution sufficient to place geocode near (or possibly within) address site boundary

Address level geocode was automatically calculated by determining where on the road the address was likely to appear, based on other bounding geocoded addresses

4 Geocode resolution sufficient to associate address site with a unique road feature

Street level geocode automatically calculated by using the road centreline reference data

5 Geocode resolution sufficient to associate address site with a unique locality or neighbourhood

Locality level geocode automatically calculated to the geometric centre within the gazetted locality for this address

PAGE 17

Reliability Level

Description Example

6 Geocode resolution sufficient to associate address site with a unique region

Locality level geocode derived from topographic feature

Note: RELIABILITY_CODE field within the ADDRESS_SITE_GEOCODE table refers to the CODE field within the GEOCODE_TYPE_AUT.

Every geocode has a reliability level. These levels are stored with the geocodes in the following tables:

LOCALITY_POINT STREET_LOCALITY_POINT ADDRESS_SITE_GEOCODE

Geocode type Provision has also been made for G-NAF to cater for multiple types of geocodes for an address. Where geocode types are nominated by the jurisdiction, these are reflected in the geocode type field. Where a geocode type is not provided, a default value is used that reflects the majority of addresses. Whilst the data model and respective geocode types have been listed, in the vast majority of cases there is no current national data sources identified to populate the additional codes. The full list of allowed geocode types is included of the Data Dictionary in Appendix C (i.e. GEOCODE_TYPE_AUT table).

Geocode priority A priority order has been developed and applied during G-NAF production to provide a single geocode for all G-NAF addresses. The priority order developed places an emphasis on identifying locations associated with emergency management access, buildings on a site and other locations which are associated with the land management process. This order has been developed with a view to assisting users in general and will not be suitable for all user business needs. The priority order applied is included in the relevant table in Appendix C. The priority order has been applied in the ADDRESS_DEFAULT_GEOCODE table.

Confidence levels Every address and geocode can be related to a supplied dataset, which in turn can be related to the contributor who provided it. This feature is essential to being able to supply the information back to the address contributors. However, the address custodian identifier is not available in G-NAF. Instead, address level metadata is available indicating how many source datasets provided each address. Address Usage is reflected in the Confidence field included in the ADDRESS_DETAIL table and is expressed as follows:

n 1 = C (n = number of datasets providing the address, C = confidence level)

Given G-NAF has been built with three contributor datasets, the Address Usage (Confidence Level) possibilities are as follows:

Confidence Level Description

Confidence level = 2 This reflects that all three contributors have supplied an identical address.

Confidence level = 1 This reflects that a match has been achieved between only two contributors.

Confidence level = 0 This reflects that a single contributor holds this address and no match has been achieved with either or the other two contributors.

Confidence level = -1 This reflects that none of the contributors hold this address in their address dataset anymore.

PAGE 18

Where an address is no longer provided by any contributor, the address will be retired. This will be reflected in its confidence level value of -1. Retired addresses are retained in G-NAF for four releases at which time they are archived.

Merge criteria Addresses which share similar characteristics from the different contributors are merged into a single record. These shared characteristics are known as the merge criteria. The fields comprising the G-NAF merge criteria are:

STATE_ABBREVIATION LOCALITY_NAME PRIMARY_POSTCODE STREET_NAME STREET_TYPE STREET_SUFFIX NUMBER_FIRST_PREFIX NUMBER_FIRST NUMBER_FIRST_SUFFIX NUMBER_LAST_PREFIX NUMBER_LAST NUMBER_LAST_SUFFIX FLAT_NUMBER_PREFIX FLAT_NUMBER FLAT_NUMBER_SUFFIX LEVEL_NUMBER

Note: Exception for Addresses without a number_first When a contributed address is supplied without a number_first, consideration is given as to whether the address contains a lot_number. An address without a number_first but with a lot_number will be added to G-NAF.

A G-NAF ID or address_detail_pid relates to a unique combination of these merge criteria fields. This address_detail_pid will persist with the address while it remains in the dataset. Where values in fields which are not included in the merge criteria (from the ADDRESS_DETAIL table) change in consecutive product releases, the address_detail_pid will not change. However the associated date_last_modified field will.

Merge criteria changes When any element of the merge criteria changes, the new record is treated as a new address and inserted into G-NAF as such.

Example This example shows Unit 3 21 Smith Street Burwood (address_detail_pid = GAVIC411711441) being changed to Unit 3 21 Brown Street Burwood by a contributor. The street name change will mean it is no longer possible to match the new incoming record to an existing G-NAF record, so a new G-NAF record (address_detail_pid = GAVIC998999843) is created. As the existing address (i.e. GAVIC411711441) is now only supported by two contributors, its confidence level is be reduced to 1. The new incoming address being only supported by one contributor will get a confidence of 0.

PAGE 19

Existing G-NAF Record GNAF_ PID FLAT

_TYPE FLAT_ NUMBER

BUILDING _NAME NUMBER _FIRST

STREET _NAME

STREET _TYPE LOCALITY _NAME CONFIDENCE

DATE_ CREATED

DATE_ RETIRED

DATE

_LAST_ MODIFIED

GAVIC411711441 UNIT 3 PONDEROSA 21 SMITH STREET BURWOOD 2

29/04/ 2014

Updated G-NAF Records GNAF_ PID FLAT

_TYPE FLAT_ NUMBER

BUILDING _NAME NUMBER _FIRST

STREET _NAME

STREET _TYPE LOCALITY _NAME CONFIDENCE

DATE_ CREATED

DATE_ RETIRED

DATE

_LAST_ MODIFIED

GAVIC411711441 UNIT 3 PONDEROSA 21 SMITH STREET BURWOOD

1*

29/04/ 2014

14/06/ 2014

GAVIC998999843 UNIT 3 PONDEROSA 21

BROWN STREET BURWOOD 0

14/06/ 2014

Address duplication As multiple contributors supply data nominally covering the same area, there is a possibility that there are duplicate addresses which represent the same addressable location. The above example simplistically demonstrates how this could occur. PSMA has developed a sophisticated series of production processes in an effort to counter these issues. The majority of this duplication has occurred as a result of the following:

The use of both ranged and non-ranged addresses for the same site (e.g. 22-28 Sydney Street vs 22 Sydney Street).

The use of a flat number as opposed to a number_first suffix for the same site (e.g. 2/27 Melbourne Street vs 27B Melbourne Street).

Where one contributor supplies a level number as part of an address string and another contributor does not supply the level number for the same site. This tends to occur on properties where hotel style addressing is used (e.g. Level 3, 302/50 Adelaide Street vs 302/50 Adelaide Street).

Where circumstances of this nature have been identified during processing, alias principal relationships have been established to prevent the duplication of addresses.

Alias Management The usability of G-NAF is greatly enhanced by the inclusion of alias information that captures addresses in popular use irrespective of official status. PSMA recognises that G-NAF has a role to play in progressing usage of official gazetted addresses. However, it is also acknowledged that the issue cannot be forced and in some cases, it will take generational change to see alias or incorrect addresses taken out of everyday usage. It is also considered that the benefits of the inclusion of aliases outweigh the costs; particularly in the application of G-NAF by emergency services. There are three levels of aliases in the G-NAF schema:

Alias Address - where an individual address is also known by another name Alias Street/Locality Address - where a street/locality pair does not exist in the reference

data and is the synonym or incorrect spelling of a street/locality pair that does exist. Alias Locality Address - where a locality does not exist in the reference data and is the

synonym or incorrect spelling of a locality that does exist

PAGE 20

Alias address Alias addresses (ADDRESS_ALIAS) are addresses, other than the principal address, that refer to the same physical location as another address record.

An address level alias refers to the same address site which is identified by different address elements. The relationship between addresses at a specific site is modelled through a principal and alias attribute and join table.

Alias street/locality Alias street/locality (STREET_LOCALITY_ALIAS) is used to determine addresses that refer to the same physical location as another address record, where the street/locality is different. Where it is identified that the street/locality in an address from a contributor was incorrect (e.g. spelling error), a rule (see below) is created to manipulate the data during the scrubbing process.

Alias locality Alias localities (LOCALITY_ALIAS) are used to determine those addresses that refer to the same physical location as another address record, but where the locality is different. The example locality "CITY will exist in the LOCALITY table and an entry for CANBERRA CITY will exist in the LOCALITY_ALIAS table.

Using alias datasets When using G-NAF to validate an address, the steps are:

1. Is there a principal address for this address?

2. Is there an alias address for this address?

3. Is there an alias locality for the locality of the address?

This can be determined by checking the locality name of the address against the LOCALITY_NAME field in the LOCALITY_ALIAS table, the locality_pid is then used to determine the correct locality_name from the LOCALITY table. The next step would be to retry steps 1 & 2 with the new locality_name.

4. Is there an alias street/locality for the address?

This can be determined by checking the street name of the address against the street_name, street_type, street_suffix fields in the STREET_LOCALITY_ALIAS table, the

PAGE 21

street_pid is then used to determine the correct street_name from the STREET table. The next step would be to retry steps 1, 2 & 3 with the new street name.

Processing links to other PSMA Data

Administrative Boundaries There are two layers within the Administrative Boundaries product that have linkages to G-NAF:

1. Suburbs/Localities

2. Mesh block 2011 (ABS theme).

Suburbs/Localities is a reference dataset for G-NAF and is the source for identifying the official locality name for an address, where available. The suburbs/localities geometry is also an important part in the allocation of geocodes for locality and street-locality geocodes generated for G-NAF.

Transport & Topography The Roads layer within Transport & Topography is a reference dataset that it used is for the processing of G-NAF. The roads data is a fundamental part of an address and is used as the source for the allocation of road names in the STREET_LOCALITY table. The roads geometry is also used in the allocation of the street-locality level geocodes. Other Transport & Topography layers have no linkage to G-NAF.

CadLite The ADDRESS_DETAIL table contains a field called legal_parcel_id, which is populated with information from the CadLite product. The information is obtained from the previous release of CadLite. For example, for the G-NAF February 2016 release, the CadLite information is obtained from the November 2015 release. The legal_parcel_id is derived from the jurisdiction_id field from CadLite using a point in polygon process. G-NAF addresses are filtered to identify an appropriate point for each address to link with the most appropriate CadLite parcels. The property_pid and gnaf_property_pid fields in G-NAF are not currently populated and have NULL values.

8.3 Update frequency PSMA currently releases G-NAF on a quarterly basis in the months of February, May, August and November.

8.4 Maintenance scope Data for existing objects with changed geometry and/or attributes as well as data for new objects within the release time period are included in the release.

PAGE 22

9. Data Product Delivery 9.1 Open Data Delivery format information The Australian Government releases G-NAF on data.gov.au in PSV format.

PSV files

Format Name: Pipe Separated Value files

Specification: PSV files may be used in relational data base applications and may be viewed in spreadsheets. This format provides files with the following extension *.psv

Language: English

9.2 PSMA Partner Network Delivery format information G-NAF is delivered to PSMAs Partner Network in the following formats:

Pipe Separated Value (PSV) files LYNX Proprietary Binary Files Oracle Dump Oracle Data Pump

PSV files

Format Name: Pipe Separated Value files

Specification: PSV files may be used in relational data base applications and may be viewed in spreadsheets. This format provides files with the following extension *.psv

Language: English

LYNX Proprietary Binary files

Format Name: LYNX binary file format

Specification: This format uses PSMAs Data Importer utility to make loading G-NAF address data into a database a simple process. This format includes files with the following extension: *.lynx

Language: English

PAGE 23

Oracle Dump

Format Name: Oracle 11g Dump Format

Specification:

A binary-format file created by the Oracle Export utility.

Language: English

Oracle Data Pump

Format Name: Oracle 11g Data Pump Format

Specification:

The Data Pump (dump) file set is made up of one or more files that contain table data, database object metadata, and control information. More information is available from Oracle

Language: English

9.3 Organisation responsible for delivery PSMA was formed by the governments of Australia in 1993 to collate, transform and deliver their geospatial data as national datasets. PSMAs establishment reflected the desire of Australian governments to work together to establish a national location information infrastructure to advance the emerging information economy. The organisations first major initiative was to support the 1996 Census through the provision of Australias first digital map at a national street-level. The value of PSMAs datasets is in the richness of the data, which enables a broad range of innovations and applications. To support the use of this data in business-ready formats, PSMA makes our data available to the market through a value-added reseller and integrator network. Our network includes traditional geospatial specialists and data engineers as well as software developers, marketing service providers, systems integrators and consultancies. From February 2016, the Australian Government will make G-NAF available through data.gov.au under open data terms. For further information on accessing PSMA Data, or becoming a value-added reseller contact: PSMA Australia Limited Unit 6, 113 Canberra Avenue, Griffith ACT 2603 T: 02 6260 9000 F: 02 6260 9001 E: [email protected] W: www.psma.com.au

PAGE 24

10. PSMA Data DATASET ACCESS THEME LAYER Administrative Boundaries

Open Data (www.data.gov.au)

ABS Boundaries Mesh Blocks (MB) 2011

PSMA Partner Network Indigenous Location (ILOC) Indigenous Areas (IARE)

Indigenous Region (IREG) Remoteness Areas (RA) Socio-Economic Indexes for Areas (SEIFA) Urban Centre Localities / Section of State Significant Urban Areas (SUA)

Electoral Boundaries Commonwealth Electoral Boundaries State Electoral Boundaries

Local Government Areas (LGAs)

Wards

Suburbs/Localities State Boundaries Town Points

CadLite PSMA Partner Network Cadastre Property

G-NAF Open Data (www.data.gov.au) PSMA Partner Network

Geocoded physical addresses

Land Tenure PSMA Partner Network Land Tenure Features of Interest PSMA Partner Network Features of Interest Postcodes PSMA Partner Network Spatial postcodes Postcode Polygons

Postcode Centroids Transport & Topography

PSMA Partner Network Transport Roads Rail Rail Stations Airports

Hydrology Hydrology Greenspace Greenspace

PAGE 25

Appendix A Addressing standards and NAMF relationship The field names used for G-NAF differ from those used by the address standard AS4590:2006 and the National Address Management Framework (NAMF). PSMA recommends applying the following G-NAF fields to provide the relationship to AS4590 and NAMF fields.

Table 1: Relationship between G-NAF, AS4590 and NAMF fields

NAMF Field AS4590 Field G-NAF Field(s) Description complexLevelType COMPLEX.LEVEL TYPE

CODE LEVEL_TYPE_AUT.DESCRIPTION Full name of level type

complexLevelNumber COMPLEX.LEVEL NUMBER ADDRESS_DETAIL.LEVEL_NUMBER_PREFIX, ADDRESS_DETAIL.LEVEL_NUMBER, ADDRESS_DETAIL.LEVEL_NUMBER_SUFFIX

Level number is a concatenation of the three fields

complexUnitType COMPLEX.SUB DWELLING UNIT TYPE CODE

FLAT_TYPE_AUT.DESCRIPTION Full name of flat type

complexUnitIdentifier COMPLEX.SUB DWELLING UNIT NUMBER

ADDRESS_DETAIL.FLAT_NUMBER_PREFIX, ADDRESS_DETAIL.FLAT_NUMBER, ADDRESS_DETAIL.FLAT_NUMBER_SUFFIX

Flat number is a concatenation of the three fields

complexStreetNumber1

COMPLEX.COMPLEX ROAD NUMBER 1

ADDRESS_DETAIL.NUMBER_FIRST_PREFIX, ADDRESS_DETAIL.NUMBER_FIRST, ADDRESS_DETAIL.NUMBER_FIRST_SUFFIX

Applicable if, and only if, a primary secondary relationship is identified in G-NAF. The first street number of the secondary address is a concatenation of the three fields

complexStreetNumber2

COMPLEX.COMPLEX ROAD NUMBER 2

ADDRESS_DETAIL.NUMBER_LAST_PREFIX, ADDRESS_DETAIL.NUMBER_LAST, ADDRESS_DETAIL.NUMBER_LAST_SUFFIX

Applicable if, and only if, a primary secondary relationship is identified in G-NAF. The last street number of the secondary address is a concatenation of the three fields

complexStreetName COMPLEX.COMPLEX ROAD NAME

STREET_LOCALITY.STREET_NAME Applicable if, and only if, a primary secondary relationship is identified in G-NAF. Street name of the secondary address

complexStreetType COMPLEX.COMPLEX ROAD TYPE CODE

STREET_TYPE_AUT.DESCRIPTION Applicable if, and only if, a primary secondary relationship is identified in G-NAF. Abbreviation of street type of the secondary address

complexStreetSuffix COMPLEX.COMPLEX ROAD SUFFIX CODE

STREET_SUFFIX_AUT.DESCRIPTION Applicable if, and only if, a primary secondary relationship is identified in G-NAF. Full name of street suffix of the secondary address

siteName ADDRESS SITE NAME ADDRESS_DETAIL.BUILDING_NAME Building name. This may require review, as there is also a name in the ADDRESS_SITE table. Perhaps a business rule similar to: 1 CASE 2 WHEN ADDRESS_DETAIL.BUILDING_NAME IS NOT NULL THEN ADDRESS_DETAIL.BUILDING_NAME 3 ELSE ADDRESS_SITE.ADDRESS_SITE_NAME 4 END

lotIdentifier ROAD NUMBER.LOT NUMBER

ADDRESS_DETAIL.LOT_NUMBER_PREFIX, ADDRESS_DETAIL.LOT_NUMBER, ADDRESS_DETAIL.LOT_NUMBER_SUFFIX

Lot number is a concatenation of the three fields

streetNumber1 ROAD NUMBER.ROAD NUMBER 1

ADDRESS_DETAIL.NUMBER_FIRST_PREFIX,

The first street number is a concatenation of the three fields

PAGE 26

NAMF Field AS4590 Field G-NAF Field(s) Description ADDRESS_DETAIL.NUMBER_FIRST, ADDRESS_DETAIL.NUMBER_FIRST_SUFFIX

streetNumber2 ROAD NUMBER.ROAD NUMBER 2

ADDRESS_DETAIL.NUMBER_LAST_PREFIX, ADDRESS_DETAIL.NUMBER_LAST, ADDRESS_DETAIL.NUMBER_LAST_SUFFIX

The last street number is a concatenation of the three fields

streetName ROAD.ROAD NAME STREET_LOCALITY.STREET_NAME Street name streetType ROAD.ROAD TYPE CODE STREET_TYPE_AUT.DESCRIPTION Abbreviation of street type streetSuffix ROAD.ROAD SUFFIX CODE STREET_SUFFIX_AUT.DESCRIPTION Full name of street suffix localityName LOCALITY NAME LOCALITY.LOCALITY_NAME Locality name stateTerritory STATE OR TERRITORY

CODE STATE.STATE_ABBREVIATION State or territory abbreviation

geoNorthSouthCoordinate

GEOCODE.GEOCODE LATITUDE

ADDRESS_SITE_GEOCODE.LATITUDE OR STREET_LOCALITY_POINT.LATITUDE OR LOCALITY_POINT.LATITUDE

Business rule: 1 CASE 2 WHEN ADDRESS_SITE_GEOCODE.LATITUDE IS NOT NULL THEN ADDRESS_SITE_GEOCODE.LATITUDE 3 WHEN STREET_LOCALITY_POINT.LATITUDE IS NOT NULL THEN STREET_LOCALITY_POINT.LATITUDE 4 ELSE LOCALITY_POINT.LATITUDE 5 END

geoEastWestCoordinate

GEOCODE.GEOCODE LONGITUDE

ADDRESS_SITE_GEOCODE.LONGITUDE OR STREET_LOCALITY_POINT.LONGITUDE OR LOCALITY_POINT.LONGITUDE

Business rule: 1 CASE 2 WHEN ADDRESS_SITE_GEOCODE.LONGITUDE IS NOT NULL THEN ADDRESS_SITE_GEOCODE.LONGITUDE 3 WHEN STREET_LOCALITY_POINT.LONGITUDE IS NOT NULL THEN STREET_LOCALITY_POINT.LONGITUDE 4 ELSE LOCALITY_POINT.LONGITUDE 5 END

geoFeature GEOCODE.GEOCODE FEATURE

GEOCODE_TYPE_AUT.NAME OR "STREET LOCALITY CENTROID" OR "LOCALITY CENTROID"

Business rule: 1 CASE 2 WHEN ADDRESS_SITE_GEOCODE.GEOCODE_TYPE_CODE IS NOT NULL THEN GEOCODE_TYPE_AUT.NAME 3 WHEN ADDRESS_SITE_GEOCODE.LONGITUDE IS NOT NULL THEN 'PROPERTY/PARCEL GEOCODE' 4 WHEN STREET_LOCALITY_POINT.LONGITUDE IS NOT NULL THEN 'STREET LOCALITY CENTROID' 5 ELSE 'LOCALITY CENTROID' 6 END

geoDatumCode GEOCODE.GEOCODE GEOGRAPHIC DATUM

"GDA94"

PAGE 27

Appendix B G-NAF Data Model

PAGE 28

Appendix C Data Dictionary The following describes how the various fields should be interpreted in the respective metadata tables in the Feature Catalogue below.

Column Abbreviation Description

Name Name The name of the column in the Integrated Database

Data Type Data type The Oracle data type of the column. Mapinfo TAB files have similar data types.

Description Description A description of the column and what the expected contents are

Primary Key Prim Key If 'Y' then this column must always have a unique value. (has # entry in the data model tables)

Obligation Man Y = mandatory. If 'Y' (mandatory), this column must be populated with data. That is, all ACTIVE records must have values in this column.

Foreign Key Table F K TABLE Represents a column in the 'Foreign Key Table' that this column is referred to by another table. (has * entry in the data model tables)

Foreign Key Column F K Col Represents a table in the Integrated Database that this column is referred to.

10 Character Alias 10 Char Alias An alias for this column name - up to 10 characters maximum. Used to define the name of the column when in ESRI Shapefile format.

Table 2: ADDRESS_ALIAS

Name Data Type Description Prim Key Man F K TABLE F K Col 10 Char Alias

address_ alias_pid

varchar2(15) The Persistent Identifier is unique to the real world feature this record represents.

Y Y - - add_al_pid

date_created Date Date this record was created. N Y - - dt_create

date_retired Date Date this record was retired. N N - - dt_retire

principal_pid varchar2(15) Persistent identifier (i.e. gnaf_pid) of the principal address

N Y ADDRESS_ DETAIL

principal_pid princ_pid

alias_pid varchar2(15) Persistent identifier (i.e. gnaf_pid) of the alias address N Y ADDRESS_ DETAIL

alias_pid alias_pid

PAGE 30


alias_type_code varchar2(10) Alias type (e.g. "Synonym"). N Y ADDRESS_ ALIAS _TYPE _AUT

code altyp_code

alias_comment varchar2(200) Comment about the alias (e.g. Corner address) N N - - alias_cmt

Table 3: ADDRESS_ALIAS_TYPE_AUT


code varchar2(10) Unique abbreviation of address alias type. This is the persistent identifier.

Y Y - - code_aut

name varchar2(50) Name N Y - - name_aut

description varchar2(30) Description of type abbreviation. N N - - dscpn_aut

Table 4: ADDRESS_ALIAS_TYPE_AUT

Alias type Description

SYN Synonym

CD Contributor Defined

AL Alternative Locality

RA Ranged Address

LD Level Duplication

FNNFS Flat Number Number First Suffix

FPS Flat Prefix Suffix De-duplication

Table 5: ADDRESS_DETAIL


address_detail_pid varchar2(15) The Persistent Identifier is unique to the real world feature this record represents.

Y Y - - add_dt_pid

date_created Date Date this record was created. N Y - - dt_create

PAGE 31


date_last_modified Date Date this record was last modified (not retired/recreated in line with ICSM standard)

N N - - dt_lst_mod

date_retired Date Date this record was retired. N N - - dt_retire

building_name varchar2(45) Combines both building/property name fields. Field length: up to 45 alphanumeric characters (AS4590.8.5).

N N - - bldng_ name

lot_number_prefix varchar2(2) Lot number prefix N N - - ltnbr_pref

lot_number varchar2(5) Lot number. Field length: five alphanumeric characters (AS4590.8.7)

N N - - lot_number

lot_number_suffix varchar2(2) Lot number suffix. Field length: two alphanumeric characters (AS4590.8.7)

N N - - lt_nb_suff

flat_type_code varchar2(7) Specification of the type of a separately identifiable portion within a building/complex. Field Length: one to seven upper case alpha characters (AS4590.8.3)

N N FLAT_TYPE_AUT code fttyp_code

flat_number_prefix varchar2(2) Flat/unit number prefix. Field length: two alphanumeric characters (AS4590.8.3)

N N - - fltnb_pref

flat_number number(5) Flat/unit number. Field length: five numeric characters (AS4590.8.3)

N N - - flt_nbr

flat_number_suffix varchar2(2) Flat/unit number suffix Field length: two alphanumeric characters (AS4590.8.3)

N N - - fltnb_suff

level_type_code varchar2(4) Level type. Field length: two alpha characters (AS4590.8.4)

N N LEVEL_TYPE_AUT code lvtyp_code

level_number_prefix varchar2(2) Level number prefix. Field length: two alphanumeric characters (AS4590.8.4)

N N - - lvlnb_pref

level_number number(3) Level number. Field length: three numeric characters (AS4590.8.4)

N N - - lvl_nbr

level_number_suffix varchar2(2) Level number suffix. Field length: two numeric characters (AS4590.8.4)

N N - - lvlnb_suff

number_first_prefix varchar2(3) Prefix for the first (or only) number in range. Field length: two uppercase alphanumeric characters (AS4590.8.6).

N N - - nbfst_pref

number_first number(6) Identifies first (or only) street number in range. Field length: six numeric characters (AS4590.8.6).

N N - - nbr_frst

PAGE 32


number_first_suffix varchar2(2) Suffix for the first (or only) number in range. Field length: two uppercase alphanumeric characters (AS4590.8.6).

N N - - nbfst_suff

number_last_prefix varchar2(3) Prefix for the last number in range. Field length: two uppercase alphanumeric characters (AS4590.8.6).

N N - - nblst_pref

number_last number(6) Identifies last number in range. Field length: six numeric characters (AS4590.8.6).

N N - - nbr_last

number_last _suffix

varchar2(2) Suffix for the last number in range. Field length: two uppercase alphanumeric characters (AS4590.8.6).

N N - - nblst_suff

street_locality_pid varchar2(15) Street/Locality of this address - not mandatory as some records in G-NAF may not require street (e.g. remote rural property).

N N STREET_LOCALITY street_ locality

_pid

st_loc_pid

location_description varchar2(45) A general field to capture various references to address locations alongside another physical location. Field length: up to 45 alphanumeric characters (AS4590.8.14)

N N - - loc_desc

locality_pid varchar2(15) The unique identifier for the locality N Y LOCALITY locality_pid loc_pid

alias_principal char(1) A = Alias record, P = Principal record N N - - als_prncpl

postcode varchar2(4) Postcodes are optional as prescribed by AS4819 and AS4590

N N - - postcode

private_street varchar2(75) Private street information. This is not broken up into name/type/suffix. Field length: up to 75 alphanumeric characters (AS4590.8.5).

N N - - priv_st

legal_parcel_id varchar2(20) Legal parcel id. Generic parcel id field derived from the PSMA Australias CadLite parcel where available.

N N - - lglparc_id

confidence number(1) Reflects how many contributor databases this address appears in (0 = 1 database, 1 = 2 database etc.)

N N - - confidence

address_site_pid varchar2(15) Address site Persistent Identifier N Y ADDRESS_SITE address_site_ pid

add_st_pid

PAGE 33


level_geocoded_code number(2) Binary indicator of the level of geocoding this address has. e.g. 0 = 000 = (No geocode), 1 = 001 = (No Locality geocode, No Street geocode, Address geocode), etc.

N Y GEOCODED_LEVEL_TYPE_AUT

code lvlgc_code

property_pid varchar2(15) Property persistent identifier referenced to relevant cadastral model

N N - - pr_pid

gnaf_property_pid varchar2(15) This field stores the G-NAF property_pid for the address.

N N - - gf_prp_pid

primary_secondary varchar2(1) P (Primary) or S (secondary) N N - - prim_sec

Table 6: PRIMARY_SECONDARY


primary_secondary_pid


Y Y - - prim_s_pid

date_created date Date this record was created. N Y - - dt_create

date_retired date Date this record was retired. N N - - dt_retire

primary_pid varchar2(15) Pid for the Primary address.-Defined as a principal address which does not have a flat number but which matches the Secondary address in all other respects OR is designated as owning Secondary addresses by PSMA (e.g. involves private road in complex development).

N Y ADDRESS _DETAIL

address_detail_pid

prim _pid

secondary_pid varchar2(15) Secondary persistent identifier for the Secondary address - defined as any address with a flat_number or more literally any address where flat_number_prefix, flat_number or flat_number_suffix is not null OR is designated as being linked to a Primary address by PSMA (e.g. involves private road in complex development)

N Y ADDRESS_ DETAIL

address_detail_pid

sec_pid

ps_join_type_code number(2) Code of 1 OR 2 when the root address:- street number, street name (and type) and locality name

components can be matched it is join type 1 Otherwise it is a join type 2.

N Y PS_JOIN_ TYPE_

CODE_AUT

code jntyp_code

ps_join_comment varchar2(500) Details of join type can be given. N N - - ps_jn_cmnt

PAGE 34

Table 7: PS_JOIN_TYPE_AUT


code varchar2(2) Defines the type of join (e.g. "1","2"). Y Y - - code_aut

name varchar2(50) Name. N Y - - name_aut

description varchar2(500) Description of the join type. N N - - dscpn_aut

Table 8: PS_JOIN_TYPE_AUT Codes

Join Type Description Name

1 AUTOMATICALLY MATCHED PRIMARY AND SECONDARY, BOTH PARENT AND CHILD HAVE THE SAME ROOT ADDRESS AUTO

2 MANUALLY GENERATED LINK, MAY OR MAY NOT HAVE THE SAME ROOT ADDRESS MANUAL

Table 9: ADDRESS_MESH_BLOCK_2011

Name Data Type Description Prim Key Man F K TABLE F K Col 10 Char Alias address_mesh_block_2011_pid


Y Y - - a_mb_11pid



address_detail_pid varchar2(15) Persistent identifier (i.e. gnaf_pid) of the principal address

N Y ADDRESS _DETAIL

address_detail_pid

add_dt_pid

mb_match_code Varchar2(15) Code for mesh block match e.g. 1 N Y MB_MATCH _CODE

code mb_matched

MB_2011_pid

varchar2(15) mesh block 2011 Persistent Identifier N Y MB_2011 mb_2011_pid mb_11pid

PAGE 35

Table 10: MB_MATCH_CODE_AUT

Name Data Type Description Prim Key Man F K TABLE F K Col 10 Char Alias code varchar2(15) Code e.g. 1. This is the persistent identifier. Y Y - - code_aut

name varchar2(100) Name of the code. e.g. PARCEL LEVEL MATCH N Y - - name_aut

description varchar2(250) Description of what the code means. N N - - desc_aut

Table 11: MB_MATCH_CODE_AUT Codes

CODE DESCRIPTION NAME

1 PARCEL LEVEL MATCH A parcel level geocode for the address has been applied and clearly within the boundaries of a single mesh block. The mesh block ID allocated to the address in most cases is at a very high level of confidence.

2 GAP GEOCODED ADDRESS LEVEL MATCH A gap geocoded match for the address has been applied and clearly within the boundaries of a single mesh block. The mesh block ID allocated to the address in most cases is at a high level of confidence.

3 STREET LOCALITY LEVEL SINGLE MATCH A street-locality level geocode for the address has been applied and clearly within the boundaries of a single mesh block. The mesh block ID allocated to the address in most cases is at a high level of confidence.

4 STREET LOCALITY LEVEL MULTIPLE MATCH A street-locality level geocode for the address has been applied and is within the boundaries of a multiple mesh blocks. The mesh block ID allocated to the address is at a low level of confidence.

5 LOCALITY LEVEL MULTIPLE MATCH A locality level geocode for the address has been applied and is within the boundaries of a multiple mesh blocks. The mesh block ID allocated to the address is at a very low level of confidence.

Table 12: ADDRESS_SITE


address_site_pid varchar2(15) The Persistent Identifier is unique to the real world feature this record represents.

Y Y - - add_st_pid



address_type varchar2(8) Address type (e.g. "Postal", Physical") N N ADDRESS_TYPE_AUT

code addr_type

PAGE 36


address_site_name varchar2(45) Address site name. Equates Complex name of AS4590.8.5. Field length: forty-five alphanumeric characters (AS4590.8.5)

N N - - name

Table 13: ADDRESS_SITE_GEOCODE


address_site_geocode_pid


Y Y - - as_gcd_pid



address_site_pid varchar2(15) Address site Persistent Identifier N N ADDRESS_ SITE

address_site_pid

add_st_pid

geocode_site_name varchar2(46) An identifier that relates to this specific geocoded site (e.g. "Transformer 75658").

N N - - gc_st_name

geocode_site_description

varchar2(45) Additional textual data e.g. "Warning: Access to water riser is located at rear of building via SMITH LANE"

N N - - gcd_st_des

geocode_type_code varchar2(4) Unique abbreviation for geocode feature. (e.g. "PRCL") (SAWG 7.4.1).

N N GEOCODE_TYPE_AUT

code gctyp_code

reliability_code number(1) Spatial precision of the geocode expressed as number in the range, 1 (unique identification of feature) to 6 (feature associated to region i.e. postcode). AS4590.8.16

N Y GEOCODE_RELIABILITY_AUT

code rlbty_code

boundary_extent number(7) Measurement (metres) of a geocode from other geocodes associated with the same address persistent identifier

N N - - bndry_ext

planimetric_accuracy number(12) Planimetric accuracy N N - - planim_acc

elevation number(7) Elevation N N - - elevation

geometry point Point geometry calculated by the longitude/latitude of record

N Y - - geometry

longitude number(11,8) longitude N N - - longitude

latitude number(10,8) latitude N N - - latitude

PAGE 37

Table 14: ADDRESS_TYPE_AUT


code varchar2(8) Defines the type of address (e.g. "postal", "physical") Y Y - - code_aut


description varchar2(30) Description of address type N N - - dscpn_aut

Table 15: ADDRESS_TYPE_AUT Codes

Address type Description Address type Description

Postal Postal UN/RES Unknown Reserve

Physical Physical UN/RMB Unknown Roadside mail box

R Rural UN/ROOM Unknown Room

UN Unknown UN/RSD Unknown Roadside mail delivery

UR Urban UN/RSM Unknown Roadside mail service

R/BLOCK Rural Block UN/SEC Unknown Section

R/CABIN Rural Cabin UN/SITE Unknown Site

R/FLAT Rural Flat UN/UNIT Unknown Unit

R/HOUSE Rural House UR/BLOCK Urban Block

R/LOT Rural Lot UR/CABIN Urban Cabin

R/RES Rural Reserve UR/FLAT Urban Flat

R/RMB Rural Roadside mail box UR/HOUSE Urban House

R/ROOM Rural Room UR/LOT Urban Lot

R/RSD Rural Roadside mail delivery UR/RES Urban Reserve

R/RSM Rural Roadside mail service UR/RMB Urban Roadside mail box

R/SEC Rural Section UR/ROOM Urban Room

R/SITE Rural Site UR/RSD Urban Roadside mail delivery

PAGE 38

Address type Description Address type Description

R/UNIT Rural Unit UR/RSM Urban Roadside mail service

UN/BLOCK Unknown Block UR/SEC Urban Section

UN/CABIN Unknown Cabin UR/SITE Urban Site

UN/FLAT Unknown Flat UR/UNIT Urban Unit

UN/HOUSE Unknown House UN/RMS Unknown Roadside mail service

UN/LOT Unknown Lot UN/RMS Unknown Roadside mail service

Table 16: FLAT_TYPE_AUT


code varchar2(7) Specification of the type of a separately identifiable portion of a building complex. Field length: one to seven uppercase alpha characters (AS4590.8.3). This is the persistent identifier.

Y Y - - code_aut


description varchar2(30) Description of flat type N N - - dscpn_aut

Table 17: FLAT_TYPE_AUT Codes

Code Description / Name Code Description / Name

ANT ANTENNA OFFC OFFICE

APT APARTMENT PTHS PENTHOUSE

ATM AUTOMATED TELLER MACHINE REAR REAR

BBQ BARBECUE ROOM ROOM

BLCK BLOCK RESV RESERVE

BTSD BOATSHED SE SUITE

BLDG BUILDING SEC SECTION

BNGW BUNGALOW SHED SHED

PAGE 39

Code Description / Name Code Description / Name

CAGE CAGE SHOP SHOP

CARP CARPARK SHRM SHOWROOM

CARS CARSPACE SIGN SIGN

CLUB CLUB SITE SITE

COOL COOLROOM STLL STALL

CTGE COTTAGE STOR STORE

DUPL DUPLEX STU STUDIO

FLAT FLAT STR STRATA UNIT

FCTY FACTORY SUBS SUBSTATION

GRGE GARAGE TNCY TENANCY

HALL HALL TNHS TOWNHOUSE

HSE HOUSE TWR TOWER

KSK KIOSK UNIT UNIT

LBBY LOBBY VLLA VILLA

LOFT LOFT VLT VAULT

LOT LOT WARD WARD

LSE LEASE WHSE WAREHOUSE

MBTH MARINE BERTH WKSH WORKSHOP

MSNT MAISONETTE

Table 18: GEOCODE_RELIABILITY_AUT


code varchar2(1) Geocode reliability code. This is the persistent identifier. Y Y - - code_aut


description varchar2(100) Description N N - - dscpn_aut

PAGE 40

Table 19: GEOCODE_RELIABILITY_AUT codes

Code Description Name

1 Geocode accuracy recorded to appropriate surveying standard Surveying Standard

2 Geocode accuracy sufficient to place geocode within address site boundary Within Address Site Boundary

3 Geocode accuracy sufficient to place geocode near (or possibly within) address site boundary Near (Or Possibly Within) Address Site Boundary

4 Geocode accuracy sufficient to associate address site with a unique road feature Unique Road Feature

5 Geocode accuracy sufficient to associate address site with a unique locality or neighbourhood Unique Locality Or Neighbourhood

6 Geocode accuracy sufficient to associate address site with a unique region Unique Region

Table 20: GEOCODE_TYPE_AUT


code varchar2(4) Stores unique abbreviations for geocode features. (e.g. "BC; Building Centroid). This is the persistent identifier.

Y Y - - code_aut


description varchar2(250) Description of geocode type N N - - dscpn_aut

Table 21: GEOCODE_TYPE_AUT Codes

Geocode Type Description Geocode Type Description

BAP BUILDING ACCESS POINT UCM UNIT CENTROID MANUAL

BC BUILDING CENTROID GG GAP GEOCODE

CDF CENTRE-LINE DROPPED FRONTAGE WCP WATER CONNECTION POINT

DF DRIVEWAY FRONTAGE WM WATER METER

PAGE 41

Geocode Type Description Geocode Type Description

EA EMERGENCY ACCESS SCP SEWERAGE CONNECTION POINT

EAS EMERGENCY ACCESS SECONDARY GCP GAS CONNECTION POINT

FDA FRONT DOOR ACCESS GM GAS METER

FC FRONTAGE CENTRE TCP TELEPHONE CONNECTION POINT

FCS FRONTAGE CENTRE SETBACK ECP ELECTRICITY CONNECTION POINT

LB LETTERBOX EM ELECTRICITY METER

PAP PROPERTY ACCESS POINT ICP INTERNET CONNECTION POINT

PAPS PROPERTY ACCESS POINT SETBACK UNK UNKNOWN

PC PROPERTY CENTROID STL STREET LOCALITY

PCM PROPERTY CENTROID MANUAL LOC LOCALITY

UC UNIT CENTROID

Table 22: ADDRESS_DEFAULT_GEOCODE


address_default_geocode


Y Y - - a_d_g_pid


date_retired date Date this record was retired.

N N - - dt_retire

address_detail_pid varchar2(15) Persistent identifier from the address_detail table N Y ADDRESS_DETAIL address_detail_pid

add_dt_pid

geocode_type_code varchar2(4) Unique abbreviation for geocode N Y GEOCODE_TYPE_AUT

code gctyp_code

geometry point Point geometry corresponding to the identified default geocode type for this address

N Y - - geometry

longitude number(11,8) longitude N N - - longitude

PAGE 42


latitude number(10,8) latitude N N - - latitude Authority Table

Table 23: GEOCODED_LEVEL_TYPE_AUT


code varchar2(2) Stores the level geocoded code for each address (e.g. 1) Y Y - - code_aut


description varchar2(70) Description of geocode type N N - - dscpn_aut

Table 24: GEOCODED_LEVEL_TYPE_AUT Codes

Level Geocoded Description

0 000 = (No geocode)

1 001 = (No Locality geocode, No Street geocode, Address geocode)

2 010 = (No Locality geocode, Street geocode, No Address geocode)

3 011 = (No Locality geocode, Street geocode, Address geocode)

4 100 = (Locality geocode, No Street geocode, No Address geocode)

5 101 = (Locality geocode, No Street geocode, Address geocode)

6 110 = (Locality geocode, Street geocode, No Address geocode)

7 111 = (Locality geocode, Street geocode, Address geocode)

Table 25: LEVEL_TYPE_AUT


code varchar2(4) Level type. Field length: two alpha characters (AS4590.8.4). This is the persistent identifier.

Y Y - - code_aut


PAGE 43


description varchar2(30) Description of level type N N - - dscpn_aut

Table 26: LEVEL_TYPE_AUT Codes

Level Type Description Level Type Description

B BASEMENT P PARKING

FL FLOOR PTHS PENTHOUSE

G GROUND PDM PODIUM

L LEVEL PLF PLATFORM

LB LOBBY RT ROOFTOP

LG LOWER GROUND FLOOR SB SUB-BASEMENT

M MEZZANINE UG UPPER GROUND FLOOR

OD OBSERVATION DECK

Table 27: LOCALITY_CLASS_AUT

Name Data Type Description Prim Key Man F K T F K Col 10 Char Alias

code char(1) Locality class code. This is the persistent Identifier of the record. Y Y - - code_aut


description varchar2(200) Description of what this locality type represents (e.g. Gazetted Locality). N N - - dscpn_aut

Table 28: LOCALITY_CLASS_AUT Codes

Code DESCRIPTION NAME

A ALIAS ONLY LOCALITY ALIAS ONLY LOCALITY

D DISTRICT DISTRICT

PAGE 44

Code DESCRIPTION NAME

G GAZETTED LOCALITY GAZETTED LOCALITY

H HUNDRED HUNDRED

M MANUALLY VALIDATED MANUALLY VALIDATED

T TOPOGRAPHIC LOCALITY TOPOGRAPHIC LOCALITY

U UNOFFICIAL SUBURB UNOFFICIAL SUBURB

V UNOFFICIAL TOPOGRAPHIC FEATURE UNOFFICIAL TOPOGRAPHIC FEATURE

Table 29: LOCALITY


locality_pid varchar2(15) The Persistent Identifier is unique to the real world feature this record represents.

Y Y - - loc_pid



locality_name varchar2(100) name N Y - - name

primary _postcode

varchar2(4) Required to differentiate localities of the same name within a state.

N N - - prim_ pcode

locality_class_code char(1) Describes the class of locality (e.g. Gazetted, topographic feature etc.). Look

G-NAF Product Description

Documents

Transcript of G-NAF Product Description