Roads and Addresses Data

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table is a lookup table identifying valid states for the unofficial field in the street and place tables. Records are set to Unofficial where it is known that the name is not recognised by the TA, or if a privately named road, or a place name missing necessary macrons.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• This table contains a static unique identifier 'id' column that is not part of the original published ASP database. This column has been added to support incremental changesets on LDS. There is a direct relationship between this column and the original primary key on the 'code' column.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table is a lookup table identifying valid Territorial Authority Districts & Cities.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• This table contains a static unique identifier 'id' column that is not part of the original published ASP database. This column has been added to support incremental changesets on LDS. There is a direct relationship between this column and the original primary key on the 'code' column.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table is used by the application to parse the road name field and warn the editor if it does not contain a valid street type.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• This table contains a static unique identifier 'id' column that is not part of the original published ASP database. This column has been added to support incremental changesets on LDS. There is a direct relationship between this column and the original primary key on the 'std_abb' column.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

A street part record will exist for every electoral subdivision of a road/street, i.e. for every valid combination of territorial authority, general electoral, & maori electoral districts that apply to the road/street name concerned. Some times additional parts may be created for clarity e.g. if the same combination exists for disconnected parts of the same road/street name.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• This table is recreated each time a new set of electoral boundaries takes effect (every 5 years). Prior to its replacement, a copy of the entire database is made and retained off-line to allow a mini Index to Places & Streets to be produced in the event of a by-election (by-elections are conducted on the same boundaries as the previous General election). The archival copy is deleted once the next General election has been held.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table contains the authoritative name assigned to a length of road. A street record will exist for every distinct length of named road. This may be split into several records if the road crosses a Territorial Authority (TA) boundary (because the TA is the naming authority), or if the road has multiple number ranges. Named roads that follow TA boundaries or meander backwards and forwards across a boundary will normally be treated as one record with multiple Street Parts.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• Some reports generated from ASP require the STREET_NAME+ LOCALITY+STATUS combination to be unique, so validation rules have been put in place enforce this.
• The locality names currently used in the STREETS table are not ideal, and are considered a work in progress. The main function of LOCALITY in ASP is to achieve uniqueness, and where 2 streets of the same name exist, to be able to differentiate between them.
• At the time of original conversion form the earlier Oracle database, in late 2004, the locality name was initially populated with the name of the locality in which most of the road centreline resided (based on meshblock to Place relationships held in Landonline), or where there was a relatively even split, to the closest locality. Some longer roads have had “Place to Place” locality names added e.g. “Christchurch-Kaiapoi”. We are aware that some of the names assigned are not ideal,

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table is a lookup table identifying valid record statuses.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• This table contains static unique identifier 'id' column that is not part of the original published ASP database. This column has been added to support incremental changesets on LDS. There is a direct relationship between this column and the original primary key on the 'status' column.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table is a lookup table identifying valid LINZ Processing Centres.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• This table contains a static unique identifier 'id' column that is not part of the original published ASP database. This column has been added to support incremental changesets on LDS. There is a direct relationship between this column and the original primary key on the 'code' column.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table contains place part records for every electoral subdivision of a place, i.e. for every valid combination of territorial authority, general electoral, & maori electoral districts that apply to the place name concerned. Some times additional parts may be created for clarity e.g. if the same combination exists in disconnected areas covered by the same place name.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• This table is recreated each time a new set of electoral boundaries takes effect (every 5 years). Prior to its replacement, a copy of the entire database is made and retained off-line to allow a mini Index to Places & Streets to be produced in the event of a by-election (by-elections are conducted on the same boundaries as the previous General election). The archival copy is deleted once the next General election has been held.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table contains names that refers to a geographic area, and that can be used in lieu of, or to localise or refine, a street address.

A place record will exist for every name that is considered to fit this definition, including any alias or alternative names that also fit this definition.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• Some reports generated from ASP require the PLACE_NAME+ LOCALITY+STATUS combination to be unique, so validation rules have been put in place to enforce this.
• The locality names currently used in the PLACES table are not ideal, and are considered a work in progress. The main function of LOCALITY in ASP is to achieve uniqueness, and where 2 places of the same name exist, to be able to differentiate between them.

In June 2014, LINZ moved the information from the Authoritative Streets and Places database (ASP) into Landonline and the ASP database is no longer maintained.

This table identifies other names for a street or place record by linking to the SUFI of the other name. This allows multiple associations if applicable. Only one record is stored for each name/other_name combination, i.e. there is no reverse entry for any two SUFI’s.

This table is part of the Authoritative Streets and Places (ASP) Database. For more information about the database including the data model see here.

Notes:

• The Alias field was added during the conversion and all records were initially set to N (No). This field will be set if relevant when editing existing records or adding new records. The values for other records will be set when time permits.