Exception processing is when a surveyor requests that LINZ checks Landonline for conflicts which are outside the surveyor's control (eg underlying topology). A surveyor can request exception processing for their e-survey at any stage prior to submit, or while the dataset is on requisition.

The exception process is used to:
  • Manage fatal topology business rule errors that will stop a CSD being submitted.
  • Resolve geometry errors.
  • Request that Landonline be updated to correctly represent the underlying cadastral framework.

Requests need to be appropriate and to ensure that moving the topology will not affect the integrity of the Cadastre.

This document describes:
  • The situations in which the exception process can be used.
  • What information is required to enable LINZ to process an exception request?
  • Exception Misconceptions.
  • How to submit an exception request.

For the purpose of this document, exceptions are referred to as either reactive or proactive. This is because LINZ requires different information for each to assess whether they can process the exception or not.

  • A reactive exception is when a surveyor has experienced an issue while trying to complete their survey e.g. an error message has displayed, or the underlying data has distorted the new survey work when trying to link marks and parcels.
  • A proactive exception is when a surveyor is requesting an exception to avoid expected issues with geometry errors before they occur.

Reactive Exceptions


The following are examples of issues that may require reactive exception:

  • When attempting to access plan generation a surveyor receives a geometry error message.
  • When trying to link parcels, an error message indicating ‘multiple line IDs in the underlying topology’ is received.
  • When running pre-validation there is a fatal topology error.
  • When linking nodes some data has ‘flipped on itself' (Click Capture\Refresh, before trying to link marks – this might resolve the issue and avoid the need for the time delay associated with an exception).
What to do if you encounter these issues:

The first step for any of these types of issues is to call the LINZ helpdesk (0800 665 463)

Describe what you have experienced, the helpdesk may be able to help – if not they will refer you to the exception process and advise the information you need to include in your exception request.

Before an exception request is submitted please read the Exception misconceptions section.

Proactive Exceptions

There are a range of situations where surveyors like to pre-empt issues resulting from inaccurate Landonline data at later stages in their work by requesting exceptions at an earlier stage in their work. These typically involve:

  • Missing boundary nodes from the underlying parcel.
  • Water/irregular boundaries in Landonline do not reflect the underlying survey definition.
  • There are significant distortions in the underlying cadastre due to incorrect capture by a previous survey or the quality of the original digital record.


  • There are multiple nodes missing from the underlying boundary.
  • The Landonline nodes at either end of a water/irregular boundary do not match the new nodes.
  • The underlying water/irregular boundary does not match the most recent survey definition and the merge-irregular line tool is required to be used.
  • The underlying nodes are so inaccurate that it will cause parcels within the survey to overlap or “flip” when linked.
  • An irregular line requires splitting (should only be used when creating a non-primary parcel over a primary parcel that is not subject to survey in this CSD).
  • Where underlying surveys have linked incorrectly (i.e. boundary points to non-boundary point positions and vice versa, and topology is therefore incorrect).
  • Where a large number of place holders (ie more than five) are needed to correct topology issues.
  • To ensure the boundaries in Landonline are shown correctly in terms of underlying CSDs.
  • To split a large road or hydro parcel to enable easier handling of a balance parcel.
  • To remove significant amounts of distortion.

Information required by LINZ to process an exception of this nature

  • Existing Parcel ID
  • Any relevant Plan References
  • Node ID(s)
  • Confirmation that any nodes to be shifted are not already ‘survey accurate’
  • Evidence to describe how the boundaries that require moving the LOL node to are defined.
  • Explanation of why the boundaries need to be shifted:
    • The most important thing to explain is which nodes need to be moved and why
    • Is it going to distort a water boundary definition when linked?
    • When using the ‘merge irregular boundaries’ tool an accurate underlying water boundary definition is required to make it work.
  • Details from the capture data that LINZ needs to line up with. (e.g. can you please shift node id 900000 to my mark 1, and node id 90000001 to my mark 2.)
  • Attach any relevant documents.

If it is unclear whether to raise an Exception Request:

Call e-survey specialist support on 0800 ONLINE (0800 665 463).

When making an exception request, please supply sufficient information to explain the reasons you believe the change needs to be made. This is particularly important when proposing changes such as:

  • Any material changes in shape to water / irregular boundaries. Note that updates to the cadastre due to accretion, erosion, avulsion, dried-up water beds and other similar situations need to be made upon deposit, not via exception request.
  • When the shape of a right line boundary has changed, i.e. adding or removing a boundary angle.
  • Where a right line boundary is to be moved to a significantly different place, i.e. more than one metre in an urban area or five metres in a rural area.
  • Where the head title of the property is Limited as to Parcels.
  • Where there are issues with definition of the underlying parcel.

Exception misconceptions

This section is to explain situations where surveyors often think they need exceptions but they actually don’t.

  • To acquire general capture advice. Please call 0800 665 463, this may result in a Survey Information Complex request.
  • To amend errors or omissions in the cadastre, e.g. parcels created on Diagrams on Transfer not shown.  This should be done using a ‘Survey Amend Cadastral Data’ e-request in Landonline.
  • To create a residue or balance parcel that is required to be created on a CSD (e.g. Limited Titles).
  • To update boundaries in terms of a new survey fix or better survey fix of a water/irregular boundary in order to include accretion/dried up stream bed or exclude erosion. 
  • When Landonline has extra or missing nodes along a roadside. These will be optional blue nodes that should not be selected during parcel capture.  They will be dealt with on deposit of the plan.
  • Until all fatal errors reported in the Pre-validation Report have been addressed.
  • To make cosmetic changes. The purpose of the exception process is to address significant topology issues to allow CSDs to be submitted for processing.

How to submit an exception request:

Before raising an Exception Request, please ensure you follow these steps:

  • Unlink all boundary marks, including any Placeholders used.
  • Keep all non-boundary/Witness/PRMs linked except where a Landonline mark clearly appears in the wrong position then leave unlinked).Unlink parcels.
  • Refresh the Spatial window to ensure that captured Data sits in the correct position.
  • Ensure your notations clearly outline what is wrong and what is required in the Exception Request before submitting it.

In the Pre-Validation tab of the CSD workspace:

Screenshot of the ‘Exception…’ button in the Pre-Validation tab

  1. In the Pre-Validation tab click the ‘Exception…’ button.
    Screenshot of the 'New comment field' in the Pre-Validation tab
  2. Type request in ‘New Comment’ field.
  3. Select ‘Send Request’ to submit request to LINZ.
    Screenshot of the 'Save changes' windows
  4. Choose ‘Yes’ to save changes and ‘OK’ to close window for Message 29097.
    Screenshot of the View Survey details window, showing exception raised
  5. The Status of the survey is updated to ’Exception Raised’.
  6. The icon in the Workspace tree displays as an egg timer indicating that the survey is in LINZ Workspace.  The survey will be on hold and cannot be accessed until LINZ has completed the exception request.
    Screenshot of egg timer icon showing in the LINZ workspace

    When LINZ has completed request:
  7. The survey status updates to ’Exception Recommendation’
  8. A new icon appears alongside the Survey Reference in the Workspace tree
  9. A Survey Exception Process Notice is added to your 'My Messages' advising what changes LINZ have made or what changes you  should make
  10. Please note in the survey report that an exception request has been undertaken and outline the reasons for it.


Last Updated: 15 November 2018