ArcGIS REST Services Directory Login | Get Token
JSON

Layer: Parcel_Boundary (ID: 47)

Name: Parcel_Boundary

Display Field: id

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Updated 14/12/2021__FME</SPAN><SPAN>__</SPAN></P><P><SPAN>This layer provides all cadastral parcel polygons and some associated descriptive data that details the appellation (legal description), purpose, size and a list of titles that have an interest in the parcel. **NOTE**: This layer contains [primary](http://data.linz.govt.nz/layer/772) and [non-primary](http://data.linz.govt.nz/layer/782) approved, current or historic linear parcels (see status flag descriptions for more information). In conjunction with the [Linear Parcels](http://data.linz.govt.nz/layer/1570-nz-linear-parcels), this layer provides the easiest way to create a relationship with associated tables such as [Parcel Title Association List](http://data.linz.govt.nz/table/1569-nz-title-parcel-association-list), [Parcel Statutory Actions List](http://data.linz.govt.nz/table/1565-nz-parcel-statutory-actions-list) and [Survey Affected Parcels List](http://data.linz.govt.nz/table/1568-nz-survey-affected-parcels-list). This layer contains spatial and non-spatial (without geometry) parcels. The Landonline system which manages the data maintains non-spatial parcels for many different reasons. The non-spatial parcels can only be accessed via WFS or as a full layer file download. No layer clips can be used. The most common reasons for non-spatial parcels are: 1. Flats and unit survey plans will create non-spatial parcels for referencing property rights. This is because the Landonline system has not yet been designed to support the spatial definition of these plans. 2. Titles which were not linked to a spatial parcel during the Landonline title conversion project created non-spatial parcel references. As titles are spatially linked many of these non-spatial parcels will be made historic or will be merged with the associated spatial parcel. Parcels within this layer contain the following status flags: - Approved: The definition of a survey-defined parcel that has been processed and authorised as correct in terms of the survey network. - Current: A parcels that has been registered or the parcel is made current by a statutory action against a Legalisation plan. - Survey Historic: A parcel that has been extinguished from the primary cadastral network but still exists in live Title estates. - Historic: A parcel that has been extinguished from the primary cadastral network and no longer exists in live Title estates or has an current recorded statutory action. Typically this happens when a parcel is subdivided or merged, and new titles or actions are registered against the replacing parcels. Note: Only parcel made historic since the beginning of Landonline operations (2002) are included.See this [page](http://www.linz.govt.nz/survey-titles/landonline-data/landonline-bde/related-datasets/dcdb-datasets) for the actual dates when Landonline operations started. Polygons within this layer have a nominal accuracy of 0.1-1m in urban areas and 1-100m in rural areas. For more detailed information about parcel accuracies please refer to the Survey Boundary Marks layer which contains accuracies for each parcel node. The originating data for parcel/title associations includes some non-official sources where the official data does not support a link. For more information [see](http://www.linz.govt.nz/about-linz/linz-data-service/dataset-information/cadastral-titles-data).</SPAN></P></DIV></DIV></DIV>

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 30000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: false

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata