Roads and Addresses Tables

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 allows the application to check for invalid combinations of TLA, Electorate, Maori & 260 sheet references at the time of data entry. This table is recreated every time a new set of electoral boundaries takes effect, and is subsequently updated if new valid combinations are discovered.

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 'combination' 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 General Electorates.

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 NZ Map Grid 1:10000 sheet references (which are a break down on the NZMG 260 map sheets).

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 'map_id' 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 NZMS 260 sheet references.

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 NZMS260 map series has been replaced by the newer Topo50 map series. If you would like to see the relationship between the NZMS 260 and Topo50 sheet extents see here and here
• 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 'map_id' 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 Maori Electorates.

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

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