World Roads and Addresses Data - Page 5

Please read: This is the look-up table for Road Section Lifecycle Stage and is part of the set of NZ Roads tables.

The Road Section Lifecycle Stage look-up table is used by the following tables; NZ Roads: Road Section.

The NZ Roads dataset includes eight data tables and eleven lookup tables. The dataset has been sourced from LINZ’s NZ Roads database, a database for the management of national roads, including those managed for addressing purposes. This set of normalised tables replaces the Landonline: Road Centre Line layer and the Landonline: Road Name and Landonline: Road Name Association tables currently published on LDS.

These centrelines are required to indicate the presence of an authoritative road name. Named centrelines are not intended to represent the exact location of a road formation. Named centrelines do not indicate the presence of legal access.

For a simplified version of the data contained within these tables see NZ Roads (Addressing), which aggregates geometries based on road name, and NZ Roads Subsections (Addressing), which holds the individual geometries.

Please refer to the NZ Roads Data Dictionary for detailed metadata and information about this layer.

Please read: This is the Route Name table, which is part of the set of NZ Roads tables. The Route Name table contains the components of the Local Route, Road Designation and Tourist Route classes of Road Name.

The NZ Roads dataset includes eight data tables and eleven lookup tables. The dataset has been sourced from LINZ’s NZ Roads database, a database for the management of national roads, including those managed for addressing purposes. This set of normalised tables replaces the Landonline: Road Centre Line layer and the Landonline: Road Name and Landonline: Road Name Association tables currently published on LDS.

These centrelines are required to indicate the presence of an authoritative road name. Named centrelines are not intended to represent the exact location of a road formation. Named centrelines do not indicate the presence of legal access.

For a simplified version of the data contained within these tables see NZ Roads (Addressing), which aggregates geometries based on road name, and NZ Roads Subsections (Addressing), which holds the individual geometries.

Please refer to the NZ Roads Data Dictionary for detailed metadata and information about this layer.

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

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

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