This historic document provides information about the lineage of some Landonline cadastral data. The information is as published prior to the creation of Landonline.

4.1. Introduction to the Attribute Data Schema

Attribute data are stored in two dimensional user defined tables. Each attribute is represented by a column. Each column is divided into rows. A row is made up of fields, each field contains value data stored where a column and row intersect.

Within the DCDB, tables are maintained in a relational database management system (Oracle). Information can be retrieved through a Geographic Query Language (GQL), an extended version of the industry standard Structured Query Language (SQL).

The DCDB database schema allows data to be organised in a logical manner, which helps simplify and clarify data relationships, and facilitate the users understanding and analysis of the data. The schema definition refers to the format and organisation of the user attribute tables, as well as the specification of any topological structures such as layers and networks.

4.2. Definition of Tables

Two types of user defined tables exist, primary and indirect tables. Click here for a definition of both the primary and indirect tables.

4.3. Static and Unique Feature Identifiers

Static and Unique Feature Identifiers, (SUFIs), are an integral part of the DCDB. They have been introduced to make it possible for clients to link their data with the DCDB and to incrementally update their databases. This means that clients do not have to receive updates in the form of complete new dumps of the data, but only need to receive those records which have changed. The client's database can then be updated with just the changed records.

As the name suggests these identifiers will never change once allocated to a feature. Thus once the link has been made it will not need to be maintained. In this way, clients can be assured that updates are received for precisely those features which have changed. They are also unique across all Land Information NZ databases so there can never be any ambiguity as to what feature from what database is being referred to. The SUFI is a 14 digit number. The leading 4 digits are the database identifier, and the trailing 10 digits are the feature number within the database.

4.4. Easement and Walkway Centreline Attributes

This table provides for the entry of values associated to the features easement_cl, and walkway_cl. Note that parcel_sufi is not populated.

Statutory easements only are captured. These are easements defined by statute which can be maintained, eg. transmission line corridors, pipeline easements. It does not include easements in gross as defined on Land Transfer plans.

Table name: COVENANT

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NOYESNO
4NameVARCHAR2(60)YESNONO
5PURPOSEVARCHAR2(60)YESNONO
6LEGALITYVARCHAR2(60)YESNONO
7PLAN_SUFINUMBER(15,1)YESNONO
8PARCEL_SUFINUMBER(15,1)YESNONO

Feature code ranges for 'COVENANT':

StartEnd
easement_cleasement_cl
walkway_clwalkway_cl

4.5. Hydrographic Attributes

This table provides for the entry of values associated to the feature hyd_segment.

Hydrographic names are entered for Rivers, Lakes, Sea, eg. Waikato River, Lake Taupo.

A feature h_line has been used to close off sections of river, ie. enable topology to be formed. Examples of where this feature is used are;

  • where two or more rivers meet
  • where a hydrographic definition extends a long way

Table name: HYD_SEGMENT

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4HYDRO_NAMEVARCHAR2(60)NONONO
5PURPOSEVARCHAR2(60)YESNONO
6LEGALITYVARCHAR2(60)YESNONO

Feature code ranges for 'HYD_SEGMENT':

StartEnd
hyd_segmenthyd_segment

4.6. Parcel Attributes

4.6.1. Appellation

The parcel appellation is divided into four fields. Each of these fields define a specific part of the appellation. The fields are Pt Indicator, Parcel Type, Parcel Digit, and Supp Digit.

The following table identifies examples of how appellations are split up.

Pt IndicatorParcel TypeParcel DigitSupp Digit 
Sec Sec1 
Lot Lot2 
MaoriPt 3D4C2F 
Sec of a BlockPtSec2ASbdn 12 Blk XIV
Closed Road ClosedRoad 

Table - Valid Appellation Entry

Where an appellation is Part of a Block of a Registration District, Survey District, or plan, the block reference will append to the end of the Supp Digit field. Where no appellation is available Appellation Unknown is entered.

Appellations are entered in terms of the simplified appellation formats contained in the Land Appellation Database (LAD).

4.6.2. Registration Fields

These fields describe the district or plan that the parcel is from.

Index Type P (prefix)
This field holds the type of district, or the plan index, eg. DP, SO, TOWN OF
Name / Number
This field holds the name of the district or the number of the plan
Name Maori
This field holds the name of the maori block, eg. PATEA
Index Type S (suffix)
This field holds anything following the name of the district, eg. SURVEY DISTRICT, TOWNSHIP

A combination of these fields are populated for every parcel. Following are examples of how the fields are populated.

Index Type PName/NumberName MaoriIndex Type S
DP12345  
  PATEA 
 PATEA TOWNSHIP
TOWN OFPATEA  
 PATEA DISTRICT
SQUARE123  
 PATERSON SURVEY DISTRICT

Table - Valid Registration Entry

Block information for Survey Districts is appended to any information in the Supp Digit field.

4.6.3. Parcel Area

The parcel area is entered in this field. Areas are entered in metric format for areas shown on metric record maps. From imperial record maps the imperial area has been entered in preference to the converted metric area where the imperial area is current, ie. not affected by subsequent subdivision. This enabled software to convert the area correctly, rounded off to the nearest fourth decimal place of a hectare. Where an imperial area was not current, ie. part of the original parcel has been subdivided and a metric balance area derived, or where a metric area was shown on the record map for subdivision under the Survey Regulations 1973, the metric area shown on the record map has been entered.

NULL values are allowed.

Total areas for severed parcels are not shown within this field. Refer also Section 4.6.11.1

The storage unit is hectares with four decimal places displayed.

Example:

12.6541, 1200.0000, 0.0317

4.6.4. Plan Supporting Appellation

The Plan Supporting Appellation is the plan that supports the original subdivision for a parcel, and is made up of three parts.

Type references the type of plan, eg. DP, SO, DEEDS, A

Number references the number of the plan including any suffix.

Suffix references the suffix to the number if it exists.

4.6.5. Plan Supporting Area

The Plan Supporting Area fields are the same as the Plan Supporting Appellation fields but are used to show a supplementary plan which supports the area of the parcel.

Example:

If Pt Lot 5 DP 1234 is taken for River Control Purposes as defined on SO 5678, DP 1234 is entered in the Index Type P and Name / Number fields and SO 5678 is entered in the Plan Supporting Area Type and Number fields. As is inferred by the name of the fields, the plan shows the area of the parcel.

These fields are not used to show Unit, or Cross Lease, as these don't support surveyed area. It is used to show Strata plans over the parcel, if these are not shown in the Plan Supporting Appellation field.

The Plan Supporting Appellation fields are not a plan index. Redefinition plans are not shown in these fields as title issues in terms of the appellation and definition as shown on the plan. Other plan types, such as underlying subdivisional, easement, topological, control plans, or mining application plans are also not shown within these fields.

4.6.6. Document

This field is provided to reference the transfer or document number supporting a diagram on transfer subdivision, or Maori Land Court records supporting unsurveyed Maori partitions.

Example:

T 12345.6, Doc 54321, CT 3D/1452

References entered are as were shown on the record map. Transfer or document references are preferred as these seldom change. However, due to the considerable time involved in searching DLR's records and search costs, Certificate of Title references are permitted.

This field is not used to show CT references shown on record maps except where they may assist in identifying parcels with the same appellation and area. CT references are not shown for balance parcels or where parcel areas are amalgamated into one title. The DCDB is not a repository for CT references. Source and point of entry for this information will be from Land Title Office records, future enquiry on appellation will be able to provide references from that source.

4.6.7. Total Area

This field is provided to show the total surveyed area where two or more polygons exist for one parcel, or the area for the transfer or document reference above where individual parcel areas are not known.

4.6.10. Legal Status

A block of fields are provided for the entry of legal attribute data to support land taken by gazette or statutes. Fields provided include Name, Purpose, and Legality. As more than one legal status may affect a parcel, there are four Purpose and Legality fields provided.

Only reserved or gazetted areas that require subsequent notification in the NZ Gazette to revoke actions, or a statutory requirement to notify the Chief Surveyor of acquisition and revocation are included in these fields. Lands acquired by transfer, private trusts and conservation covenants, etc. are not included when they may be disposed of, or cancelled, without notification to this department.

Similarly, with the creation of SOE's and corporatisation of former government departments, property holdings are being defined by survey, order in councils authorising title and freehold titles issued in the name of the SOE or corporation. Railway land is an example of this, where ownership has been assumed, the land subdivided by survey and freehold title issued. In these situations the land is treated as normal freehold land without reference in the legal status fields.

Secondary usages within reserved or gazetted areas are shown where sufficient information is available to define them. Examples of secondary usages include Wilderness Areas within National Parks and Forest Parks (or Conservation Parks), Recreation, Open Indigenous State Forest, Forest Sanctuary, and Ecological Areas within State Forests, and secondary usages created under Section 191 PW Act 1981.

4.6.10.2. Purpose

The purpose of the reserved or gazetted area is entered in this field as capital and lower case characters. Reserve is entered in full rather than the standard abbreviation of Res.

Example:

Local Purpose Reserve (Service Lane)

Crown Land Reserved from Sale

Sounds Foreshore Reserve

4.6.10.3. Legality

The legality by which the reserved or gazetted area was taken is entered in this field.

Example:

Gaz 1987 p 144 or GN 54387.2

Sec 12 ROLD Act 1986

Sec 58 Land Act 1948

Where a reserve has been reclassified under the Reserves Act 1977, only the reclassification gazette reference is shown.

Where reserves are automatically vested on deposit of the survey plan, the legality is entered as Vested DP....

Situations may arise where numerous parcels with numerous gazette references are amalgamated into one parcel for convenience. In these situations a string of gazette references are placed in the Legality field separated by a comma or separating pages of a common year by a comma and space. However, where more references are required than the length of field available, the most prominent legalities are shown or alternatively, if these are listed on a plan, the plan reference is shown.

Example:

Refer DP 42294

Refer SO I234

4.6.11. Specific Attribute Entry

4.6.11.1. Severed Parcels

Centroids are placed for each portion of a severed parcel so that topology may be formed for every parcel polygon. Full attribute data, including area, is shown for each centroid for enquiry purposes. Where described as a whole appellation each portion is entered as a whole appellation. Whether individual areas are, or are not, known for each severed parcel the total of the portions is shown in the Total Area field.

4.6.11.2. Marginal Strips

These notices are recorded in the fourth Purpose and Legality fields of the DCDB Parcel table. The reason for this is by nominating a field that would not be otherwise used the selection could be specific when queries are made on the database. If the next available field was used, selections would be lengthy as all Purpose and Legality fields would need to be included.

The wording of the purpose notices and legalities will vary.

4.6.11.3. Endowment Revesting Act 1991

Where known, the Purpose and Legality fields are populated for land affected under Section 5 of the Foreshore and Seabed Endowment Revesting Act 1991, or Harbour Boards Dry Land Endowment Revesting Act 1991.

4.6.11.4. Maori Roadway

A "Maori Roadway" effectively is the same as a private road or private way as laid out under the Local Government Act 1974. The major differences being:

  • It is "created" by a Court order of the Maori Land Court and
  • It is only applicable to Maori Land and does not affect the ownership of the land.

The following appellation is entered into the parcel table where a closed parcel polygon is defined as Maori Land and a Maori Roadway.

Pt IndicatorPt
Parcel DigitA3E2C3B3C2C2B1B
Supp Parcel Digit(Roadway)

Table - Valid Maori Roadway Entry

4.6.11.5. Crown Forest Land

Crown Forest Land is one of the three possible outcomes that has occurred to unrestricted State Forest land.

4.6.11.6. Esplanade Strips (Section 232 Resource Management Act 1991)

There is no spatial (graphical) capture to define the extent of these strips, only an entry in the parcel table to identify that such a strip exists.

The parcel centroid feature has the following attributes;

Purpose_4Subject to the provision of Esplanade Strips
Legality_4Sec 232 Resource Management Act 1991

This is not the best solution but will have to do for now. Reason - there is no process in place to maintain this information, ie. the Esplanade Strips could be cancelled without Land Information NZ being notified.

Note the fact that this information was correct at time of entry, and that the title needs to be searched.

4.6.11.7. Section 237A Resource Management Act 1991

Section 237A is a new reference in terms of the 1993 Amendments to the Resource Management Act, it was previously known as Section 235.

Land vested remains as a polygon, the boundaries to be coded *.hyd. Where there is a series of such parcels, or where they join hydro segments, the abutting boundaries of each polygon should be coded parcel_bdy, giving one cadastral hydrographic polygon if a *.hyd was made.

The centroid feature code shall be parcel with the following attributes;

Table name: PARCEL

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4PT_INDICATORVARCHAR2( 3)YESNONO
5PARCEL_TYPEVARCHAR2(54)YESYESNO
6PARCEL_DIGITVARCHAR2(60)YESYESNO
7SUPP_PARCEL_DIGITVARCHAR2(60)YESNONO
8INDEX_TYPE_PVARCHAR2(35)YESYESNO
9NAME_NUMBERVARCHAR2(54)YESYESNO
10PLAN_SUFINUMBER(15,1)YESYESNO
11NAME_MAORIVARCHAR2(54)YESNONO
12INDEX_TYPE_SVARCHAR2(35)YESNONO
13PARCEL_AREANUMBER(10,4)YESNONO
14PARENT_PLAN_SUFINUMBER(15,1)YESYESNO
15PARENT_PLAN_REFVARCHAR2( 28)YESNONO
16SUPP_PLAN_SUFINUMBER(15,1)YESYESNO
17SUPP_PLAN_REFVARCHAR2( 28)YESNONO
18DOCUMENTVARCHAR2(32)YESNONO
19TOT_AREANUMBER(10,4)YESNONO
20RESERVE_NAMEVARCHAR2(60)YESNONO
21PURPOSE_1VARCHAR2(60)YESNONO
22LEGALITY_1VARCHAR2(60)YESNONO
23PURPOSE_2VARCHAR2(60)YESNONO
24LEGALITY_2VARCHAR2(60)YESNONO
25PURPOSE_3VARCHAR2(60)YESNONO
26LEGALITY_3VARCHAR2(60)YESNONO
27PURPOSE_4VARCHAR2(60)YESNONO
28LEGALITY_4VARCHAR2(60)YESNONO

Feature code ranges for 'PARCEL':

StartEnd
parcelparcel
parcel02parcel02
parcel1008parcel1008
parcel20parcel20
parcel32parcel32

 

4.7. Plan / Provisional Plan Reference Attributes

The surv_plan table stores the plan_sufi which comes from the plan_lookup table.

The plan_lookup table holds the attributes:

Plan_type, Plan_no, Plan_suffix, Datum, Plan_description

The Datum field identifies the origin of coordinates. Capture of this information started mid 1995, ie. retrospective capture of datum information has not been undertaken at this point in time. The table below shows valid entries.

DatumIn Full
GD 49Geodetic Datum 1949
GD 71Geodetic Datum 1971
MAGNETICMagnetic Datum
OCDOld Cadastral Datum
CompiledCompiled
ComputedComputed

Table - Valid Plan Datum Entries

The Plan Description field indicates the type of plan. The table below shows valid entries.

Where the plan is not covered by one of those listed, eg. Easement, then one of NULL, Compiled or Computed is used to distinguish the type of survey data on that plan. This includes redefinition and proclamation plans, which do not have a separate description.

Stat Bdy is used to represent all Electoral District, Fire District, Territorial Authority and other plan that define a statutory boundary.

Unit, Xlease and Strata are used to capture the letters U, C and S that are written next to the plan number for Land Transfer plans.

CT Diag is used for plans that have been prepared to enable an appellation to be assigned to balance sections of a subdivision and there is no survey basis for the boundary definition (not surveyed or compiled).

Plan DescriptionIn Full
CT DiagCT Diagram
Covenant 
Easement 
MiningMining Licence
MarineMarine Farm Licence
NSDNo Survey Data
No PlanPhysical plan lost or destroyed
Not UsedPlan number not allocated, renumbered or withdrawn
Photo 
ControlStandard Control or Trig Control
Stat BdyStatutory Boundary
StrataStrata
Topo 
TrnmsnTransmission
UnitUnit
XleaseCross Lease

Table name: SURV_PLAN

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4PLAN_SUFINUMBER(15,1)NOYESNO

Feature code ranges for 'SURV_PLAN':

StartEnd
planplan
plan_provplan_prov

4.8. P_sufi Attributes

The p_sufi table is used to store information for features that do not have their own attribute table. These are usually linear features with no "real attributes" as such. The p_sufi table allows for each of these features to have their own sufi and hold the created_date and modified_date fields.

Table name: P_SUFI

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO

Feature code ranges for 'P_SUFI':

StartEnd
client_bdyclient_bdy
constit_bdyconstit_bdy
general_bdygeneral_bdy
h_lineh_line
ld_bdyld_bdy
m_part_bdym_part_bdy
maint_bdymaint_bdy
maori_bdymaori_bdy
mesh_bdymesh_bdy
mesh_cadmesh_cad
mesh_topomesh_topo
mesh_othermesh_other
no_lic_bdyno_lic_bdy
parcel_arcparcel_arc
parcel_arc02parcel_arc02
parcel_arc20parcel_arc20
parcel_bdyparcel_bdy
parcel_bdy02parcel_bdy02
parcel_bdy20parcel_bdy20
parcel_hydparcel_hyd
parcel_hyd02parcel_hyd02
proc_bdyproc_bdy
r_r_arcr_r_arc
r_r_arc02r_r_arc02
r_r_arc20r_r_arc20
r_r_bdyr_r_bdy
r_r_bdy02r_r_bdy02
r_r_bdy20r_r_bdy20
r_r_hydr_r_hyd
r_legal_arcr_legal_arc
r_legal_bdyr_legal_bdy
r_liner_line
r_line20r_line20
region_bdyregion_bdy
ta_bdyta_bdy
temp_linetemp_line
ward_bdyward_bdy

4.9. Railway Centreline / Segment Attributes

The railway table stores attributes associated to the features railway_cl and rail_segment.

Railway names are stored as approved by Tranzrail, the NZ Geographic Board, and listed in Section 1 of the Cartographic Manual of Instruction, eg.

NORTH ISLAND MAIN TRUNK

Where the Railway name is hyphenated, it is entered without spaces separating the parts of the name and the hyphen.

Unnamed rail_segment features have the Railway Name populated as RAILWAY.

Table name: RAILWAY

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4RAILWAY_NAMEVARCHAR2(50)NONONO

Feature code ranges for 'RAILWAY':

StartEnd
railway_clrailway_cl
rail_segmentrail_segment
rail_seg20rail_seg20

4.10. Road Centreline Attributes

The road_cl table stores attributes associated to the features road_cl, pte_road_cl, pte_route_cl, and access_cl.

4.10.1. Road Name

The Road_cl table contains one road_lookup_sufi from the indirect table road_lookup. There is also an entry in the rd_name_cl table. Where there is more than one name associated with a centreline, multiple entries exist in the rd_name_cl table, as well as the full_road_name being populated with a combination of all the names eg HIGH STREET (SH 1).

The road_lookup table has been set out with the fields; Road Name, Road Type, Road Suffix, Unofficial_flag and ASP_location. Street names, type, and suffix are entered without abbreviation, ie. ROAD is not entered as RD. The Unofficial_flag is used to record entries that have not been confirmed by the Territorial Authority as being a valid name. The ASP_location holds either the Territorial Authority name, or where there are two or more distinct roads with the same name within a Territorial Authority a location to distinguish each road.

The Road Status field in the road_cl table contains a status where necessary, ie. Private Route, Private Road, Forestry, Accessway, Service Lane or Roadway.

Values within the Road Name, Road Type and Road Suffix of the road_lookup table fields are entered in upper case.

Examples of valid entries include;

Road NameRoad TypeRoad Suffix
MT FYFFEROAD 
WAIPUNASTREET 
PENNYLANE 
QUEEN CARLOTTEDRIVE 
MAINROADD'URVILLE ISLAND
MILL AND FORDROADEAST
SH 1  
THE ANCHORAGE  
MAINROAD 
WILLIAMGROVE 

Abbreviations have only been shown when sufficient characters are not available within the field, and then standard abbreviations as shown in Appendix One, and used within the Authoritative Streets and Places (ASP) database, have been used. Where the Road Name is hyphenated, the record has been entered without spaces separating the parts of the name and the hyphen. Where the Road Name is like MC IVOR no spaces separate parts of the name, eg. MCIVOR.

Where a Motorway is formed but has not been legalised, the feature code pte_route_cl is used, and the Road Status entered as Private Route. Only when the majority of the land over which the motorway construction runs, has been designated as motorway is the centreline feature code changed to road_cl with no Road Status.

4.10.2. Road Status

Private roads, private routes, accessways and service lanes require the description or status of road to be entered in the Road Status field. Entry is in upper and lower case.

For example;

Service Lane, Private Road

Named Local Purpose Reserves for the purpose of Accessway or Service Lane are considered private roads and named with the annotation `Private Road' as outlined above.

Note the following -

Where a legal road polygon is broken by a rail_segment or hydro_segment, the feature code of the centreline of the road is not changed to pte_route_cl for that portion of the centreline that passes over the rail_segment or hydro_segment.

Where a "Motorway" is formed but has not been legalised, the feature code is pte_route_cl and the status is (Private Route). Only when the majority of the land over which the motorway construction runs, has been designated as motorway is the centreline feature code changed to road_cl with no status.

The investigation of access_cl centrelines in terms of whether they are vehicular or pedestrian has NOT been undertaken by way of field checks.

4.10.3. Roads Without a Name

There are cases where a road centreline is captured when there is no road name. Valid entries in these cases are:

ROADWAY, Service Lane, Accessway

In the case of `ROADWAY' the Road Status field will show `Private Road' as well.

Table name: ROAD_CL

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NOYESNO
4ROAD_LOOKUP_SUFINUMBER(15,1)NOYESNO
5FULL_ROAD_NAMEVARCHAR2(90)YESNONO
6ROAD_STATUSVARCHAR2(13)YESNONO

Feature code ranges for 'ROAD':

StartEnd
access_claccess_cl
pte_road_clpte_road_cl
pte_route_clpte_route_cl
road_clroad_cl

4.12. Road Legality Attributes

The feature code is road_legal.

This feature is provided for the entry of road legality attributes.

4.12.1. Road Legalities

Land Information NZ are of the understanding that a number of terminologies are being used in respect to road legalities without a true understanding of what those terminologies mean. The following list identifies some of the more common terms, with a definition as to what they mean.

  1. Legal Road / Public Road - both of these terms are accepted to relate to "road" that has been legalised. That is to say some formal action has taken place and is recorded to the effect that it is road. (NB: The definition of road as per Section 315 Local Government Act 1974 includes Street, Accessway and Service lane but does not include Motorway).
  2. Road Purposes - A term used for land that is held as a public work which may be declared road at a later date. (NB: It is not legal road until some formal follow-up action has occurred.)
  3. Purposes of a Road - This term has similar meaning to road purposes. While it is in some quarters considered to be land held as a public work and therefore not road, others, such as Wellington DLR's, have ruled land taken or transferred for the purposes of a road is a public road. NB: In the instances of (b) and (c), above, districts if in doubt should consult their local DLR / ALR for a ruling.
  4. Set apart for Road - This term is used when lands of the Crown are made road, i.e. the land automatically becomes legal road on the appearance of the Gazette Notice. (Re Sec 52(1) PW Act).
  5. Acquired for Road - This term relates to where land is acquired for road through an agreement with the owner. As with (d) above, land automatically becomes legal road on publication of notice. (Re Sec 20 PW Act.)
  6. Declared Road - This term relates to the declaring of private or public land to be road by the Minister by notice in Gazette. Occurs when a written consent is obtained from the owners, lessees or licenses. (Re Sec 114 PW Act).
  7. Taken for Road - This term denotes the compulsory taking of land for road by proclamation under the hand of the Governor-General. (Re Sec 23-26 PW Act.)

Table name: ROAD_LEGAL

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NOYESNO
4LEGALITYVARCHAR2(60)NONONO

Feature code ranges for 'ROAD_LEGAL':

StartEnd
road_legalroad_legal
road_legal08road_legal08

 

4.13. Road Segment Attributes

The feature code is road_segment, road_inter.

These features are linked to the road_lookup table by the indirect table rd_name_segment

The rd_name_segment table holds the road_lookup_sufi and the road_segment_sufi for each name associated with a given road_segment or road_inter feature.

Table name: ROAD_SEGMENT

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO

Feature code ranges for 'ROAD_SEGMENT':

StartEnd
road_interroad_inter
road_inter20road_inter20
road_segmentroad_segment
road_seg20road_seg20

4.14. Street Address Attributes

Feature code is address.

This feature is provided for the entry of street address attributes. The Flat / Unit field will only be populated if the Flat / Unit has its own distinct address, eg. Flat 1B 14 BELFORD ROAD, if the flat is shown on the plan simply as 'Flat 1' it is not recorded as an address.

The House Number Low field must always be populated. This field holds the street address number whether it is involved in a range or not.

The House Number High field will only be populated if the address is involved in a range, eg. 103-115 Thorndon Quay, where 103 is the House Number Low and 115 is the House Number High.

The Road_lookup_sufi holds the SUFI from the Road_lookup table for the road name for this address feature. The Road_cl_sufi holds the SUFI for the nearest road centreline with the same road name.

Where an address has been identified, but has not been confirmed by the Territorial Authority the Unofficial_flag is used.

An entry is populated in the Address_relations table for each parcel that a given address is related to.

Table name: ADDRESS

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4HOUSE_LOWNUMBER(10,0)NONONO
5HOUSE_LOW_SUFFIXVARCHAR2( 2)YESNONO
6HOUSE_HIGHNUMBER(10,0)YESNONO
7HOUSE_HIGH_SUFFIXVARCHAR2( 2)YESNONO
8FLAT_UNITVARCHAR2( 6)YESNONO
9FLAT_UNIT_SUFFIXVARCHAR2( 6)YESNONO
10ROAD_LOOKUP_SUFINUMBER(15,1)NOYESNO
11ROAD_CL_SUFINUMBER(15,1)NOYESNO
12UNOFFICIAL_FLAGVARCHAR2(1)YESNONO

Feature code ranges for 'ADDRESS':

StartEnd
addressaddress

 

4.16. Meshblock Attributes

This table provides for the entry of meshblock identifier attributes, associated to the feature meshblock.

In some cases there are multiple polygons for a given meshblock identifier.

Table name: MESHBLOCK

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESNO
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4MESHBLOCK_IDVARCHAR2( 7)NOYESNO

Feature code ranges for 'MESHBLOCK':

StartEnd
meshblockmeshblock

4.17. General Electorate Attributes

This table provides for the entry of general electorate attributes, associated to the feature general.

Table name: GENERAL

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4GENERALVARCHAR2(30)NONONO
5GENERAL_IDVARCHAR2( 3)NONONO

Feature code ranges for 'GENERAL':

StartEnd
generalgeneral

4.18. Maori Electorate Attributes

This table provides for the entry of maori electorate attributes, associated to the feature maori.

Table name: MAORI

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4MAORIVARCHAR2(30)NONONO
5MAORI_IDVARCHAR2( 1)NONONO

Feature code ranges for 'MAORI':

StartEnd
maorimaori

4.19. Alcohol No Licence District Attributes

This table provides for the entry of alcohol no licence district attributes, associated to the feature no_licence.

Table name: NO_LICENCE

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4NO_LICENCEVARCHAR2(40)NONONO
5NO_LICENCE_IDVARCHAR2( 1)NONONO

Feature code ranges for 'NO_LICENCE':

StartEnd
no_licenceno_licence

4.20. Regional Council Attributes

This table provides for the entry of regional council attributes, associated to the feature region.

Table name: REGION

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4REGIONVARCHAR2(40)NONONO
5REGION_IDVARCHAR2( 2)NONONO

Feature code ranges for 'REGION':

StartEnd
regionregion

4.21. Regional Constituency Attributes

This table provides for the entry of regional constituency attributes, associated to the feature constituency.

Table name: CONSTITUENCY

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4CONSTITUENCYVARCHAR2(40)NONONO
5CONSTIT_IDVARCHAR2( 4)NONONO

Feature code ranges for 'CONSTITUENCY':

StartEnd
constituencyconstituency

4.22. Territorial Authority Attributes

This table provides for the entry of territorial authority district attributes, associated to the feature ta.

Table name: TA

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4TAVARCHAR2(40)NONONO
5TA_IDVARCHAR2( 3)NONONO

Feature code ranges for 'TA':

StartEnd
tata

4.23. Ward Attributes

This table provides for the entry of territorial authority ward attributes, associated to the feature ward.

Table name: WARD

#NameTypeSizeNullsIndexUnique
1SUFINUMBER(15,1)NOYESYES
2CREATED_DATEDATE(22)NONONO
3MODIFIED_DATEDATE(22)NONONO
4WARDVARCHAR2(40)NONONO
5WARD_IDVARCHAR2( 5)NONONO

Feature code ranges for 'WARD':

StartEnd
wardward

Back to DCDB Data Characteristics menu