We are starting to decommission Survey Legacy Landonline functionality. Get help here using New Landonline functionality.

Exception requests

Exception processing is when a surveyor requests that LINZ checks Landonline for conflicts which are outside the surveyor's control. 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:

  • Resolve fatal topology and geometry errors that prevent a CSD being submitted.
  • Request that Landonline be updated to correctly represent the underlying cadastral framework.

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
  • When not to use the exception process.
  • 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.

Webinar presentations

The following sessions were presented by the Spatial and Requests Team in conjunction with the team at Survey and Spatial New Zealand

Reactive Exceptions


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

  • 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).
  • Where excessive use of placeholders have been necessary to correct topology

What to do if you encounter these issues:

The first step for any of these types of issues is to call the LINZ Customer Support (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.

Proactive Exceptions

There are a range of situations where surveyors are able to pre-empt issues resulting from inaccurate Landonline data. These situations typically involve:

  • Missing boundary nodes from the underlying parcel.
  • Water/irregular boundaries in Landonline do not reflect the underlying survey definition.
  • Significant distortions in the underlying cadastre due to the quality of the original digital record. (eg Digitised map records created prior to Landonline)
  • Missing parcels (eg hydro parcels)


  • 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.
  • 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 (eg when creating a non-primary parcel over a primary parcel that is not subject to survey in the CSD).
  • Where underlying surveys have linked incorrectly (i.e. boundary points to non-boundary point positions and vice versa, and topology is therefore incorrect).
  • 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 creation of a balance parcel.

Information required by LINZ to process an exception of this nature

  • Any relevant Plan References
  • Node ID(s) and/or mark references requiring attention. (e.g. can you please shift node id 900000 to my mark 1, and node id 90000001 to my mark 2.)
  • Details of any error message encountered that prevents submission.
  • Where the request involves altering an existing water boundary a complete and comprehensive explanation of the captured definition is required. This includes detailing adoption sources and providing other relevant information.
  • Attach any relevant documents such as the survey report, stream plots, field notes showing adopted stream fixes and aerial photo evidence.

When not to raise an exception request

  • To acquire general capture advice. Please call 0800 665 463,
  • To amend errors or omissions in the cadastre for land not under survey e.g. parcels created on Diagrams on Transfer not in Landonline. This should be done using a ‘Survey Amend Cadastral Data’ request in Landonline.
  • To create a residue or balance parcel that is required on the CSD (e.g. Limited Titles).
  • To update boundaries in terms of a new survey fix or better survey fix of a water/irregular boundary.  
  • When Landonline has extra 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 Pre-validation Report errors 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:

  • Unlink all boundary marks, including any Placeholders used.
  • Link one network mark. (preferably high order). For parcels without survey information datasets link the highest order boundary mark.
  • Refresh the Spatial window to ensure that captured data sits in the correct position.
  • Ensure your comments 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.