Release Notes - Surveyors and TA

Each time a Surveyor selects the Generate Plan button for an Aspatial Plan, the Plan gets sent to run in the Plan Generation Batch. If no Plan Graphic supporting document is attached then the Batch will fail. This uses up resources required to ascertain why the batch has failed.

If the 'Generate Plan' button is selected for an Aspatial Plan for which no Plan Graphic supporting document is attached the following message will appear:

This message prevents the Plan Gen Batch from being initiated until a Supporting document type of 'Plan Graphic' has been attached to the Plan.

Users must attach a 'Plan Graphic' supporting document prior to selecting the 'Generate Plan' button for Aspatial Plans.

If an XML file contains new marks and the new plan reference is not part of the mark name, then upon Import the plan reference is not automatically assigned to the new marks. Users have to manually edit the mark details by adding the new plan reference.

This usually occurs where the plan is not 'pre allocated' by the surveyor prior to doing the field work.

Upon Import of any XML files containing new marks without the plan reference added, Landonline will auto populate the plan reference against these new marks.

An XML file example of new marks with no plan reference against it:

These mark names will contain the new plan reference as shown in the screen shot below of CSC_S03a – Mark List and CSC_S03b – Mark Details screens.

Landonline does not currently include capacity for networks as per Section 3 of LINZS25003 which outlines six geodetic networks. One of these consists of three sub-networks.

Every geodetic control mark is required to be part of at least one official geodetic network.

The following Geodetic Networks have been introduced to the Landonline Geodetic survey module:

1. National Reference Frame (NRF)
2. Deformation Monitoring Network (DMN)
   1. National DMN (NDMN)
   2. Regional DMN (RDMN)
   3. Local DMN (LDMN)
3. Cadastral Horizontal Control Network (CHN)
4. Cadastral Vertical Control Network (CVN)
5. Basic Geospatial Network (BGN)
6. National Height Network (NHN)

Every geodetic control mark will be part of at least one official geodetic network.

Workspace and Desktop users will be able to view information about the network to which a Geodetic Control Node belongs using the spatial view.

The inverted triangle symbol is used in spatial view to identify Geodetic Control Marks belong to Geodetic Networks.

A unique colour has been allocated to each layer and the symbol will be displayed in that colour in the spatial view.

Refer to the following screen shot for Geodetic Network layers and their colours in Geodetic Theme:

The following screen shot displays a 6th Order mark which belongs to NRF Network:

There is a possibility that this mark could belong to more than one network. The Object Information tool can be used to find if a mark belongs to more than one Geodetic Network.

The following screen shot displays the Geodetic Network information for the selected Node Id in the spatial view:

The Geodetic Network information will also be displayed in the Object Information tool for the following spatial layers:

NZGD2000 - Order 0-3
NZGD2000 - Order 4-5
NZGD2000 - Order 6
NZGD2000 - Order 7-9
NZGD2000 - Order 10-12

The View Mark/Node report in searches tree view has been modified to include Geodetic Networks.

Following is a screen shot of the modified report. The Geodetic Network information will appear in the bottom of the report:

A new business requirement is that the Title Plan must display both boundary bearings and distances.

When the Title Plan is generated the Bearings and Distances are displayed for both Primary and Non Primary boundaries to reflect exactly what has been laid out in Layout Sheets for the CSD Title Sheets by the surveyor.

This enhancement excludes retrospective enhancement of Surveys at the Stages of Submitted, Approved, Deposited or Registered in Landonline.

Boundary bearings will not appear on parcel Views. i.e. No Change.

In accordance with the new Unit Titles Act, there is the requirement to create new Plan Types.

6 additional Plan Types will be made available when the new Unit Titles Act comes into force. They will remain unavailable for selection until the Act comes into force.

The Plan Types are:

• Subsidiary PUD
• Subsidiary PUD with Survey Sheet
• Subsidiary Standard Unit Plan
• Subsidiary Standard Unit Plan with Survey Sheet
• Simple Redevelopment Unit Plan
• Simple Redevelopment Unit Plan with Survey Sheet

All existing Unit Plan types will remain.

There have been a number of instances where users have not been capturing and linking parcels correctly in their e-surveys. The most common fault is when an existing Easement is being brought forward to the new survey and it exists spatially in Landonline.

Users have been 'Referencing' existing spatially defined easements by linking with a 'referenced' parcel. The correct procedure is to 'extinguish' the existing spatial parcel and 'create' it as a new parcel on the survey.

Parcels that are listed as 'Referenced' can no longer be linked spatially. Only 'Created' parcels can be linked.

If a user attempts to link a 'Referenced' parcel the following message will appear:

In order for a parcel to be linked, the underlying (spatially defined) parcel must be 'Extinguished' and redefined spatially in capture. A new parcel must be 'Created' in the Parcel List screen and the two linked.

RCS 2010 have taken particular effort to discard the traditional term 'Traverse' and replace it with the term 'Non–Boundary'.

'Traverse' was used widely in Landonline to address Marks, observations and layers.

The RCS 2010 also refer to 'vectors' (Bearing and Distance) whereas Landonline has been referring to any 'bearing and distance', 'distance only' or 'bearing only' collectively as 'Observations'.

Surveyors are used to thinking of an 'observation' as something they have 'observed' when of course many are calculated or adopted.

A number of layers have been renamed to reflect 'Vectors'.

In Capture the Current layer tab has renamed 'Observations' to 'Vectors' as shown below for Boundary and Non Boundary layers:

In Current layer tab 'Underlying Observations' have been renamed 'Underlying Vectors':

In Labels tab the above changes have also been reflected:

Under the Capture drop down menu 'Traverse/Bdy Capture' has been replaced with 'Vector Capture'

The CSC_S04 Traverse/Bdy Capture screen has had three changes:

1. The screen is now called 'CSC_S04 Vector Capture'
2. The 'Observations' table is now called 'Vectors'
3. The 'Observation Details group box is now called 'Vector Details'

In Plan Generation/Define Diagrams the term 'Traverse' has been removed from 'System Generated Survey Travserse Diagams' and 'User Defined Survey Traverse Diagrams'.

This is reflected in:

• Current layers tab
• Survey diagram icons
• Menu drop down list 'Generate Plan/Add Survey Diagram'

In Plan Generation/Maintain Diagram Layers the term 'Traverse Observations' has been replaced with the term 'Non Boundary Vectors' in both System Generated Survey Diagrams and User Defined Survey Diagrams.

The Landonline 'Help' file has been updated to reflect these changes but reference to 'Observation' may still be apparent in some instances.

Under the Rules for Cadastral Survey 2010, it is no longer acceptable for parcels to have an appellation of CSC Parcel Number if a proper appellation is not supplied. The appellation CSC parcel id will no longer appear in the CSD Plan and the Title Plan (including the diagrams).

Landonline applies the CSC Parcel Number as the parcel appellation to parcels that are not given a proper appellation e.g Balance Road or Hydro Parcels. These are no longer acceptable as appellations on the CSD Plan and the Title Plan images under RCS2010.

A change has been made to stop CSC Parcel Numbers appearing as appellations in the CSD Plan and the Title Plan images.

The CSC Parcel Number will be removed from CPG_S04 – Layout Plan Sheets.

The CSC Parcel Number will not appear on Plan Gen Images.

The CSC Parcel Number will remain apparent in the CSC_S07a – Parcel List.

The CSC Parcel id will continue to appear in the parcel list in Landonline Searches.

The Survey Header will not display the CSC Parcel id after Submit (Current functionality).

Add user added text to parcel in Layout sheets to indicate parcel intent e.g. Roadname or Stream Name.

Business Rule C485 was designed to test RCS2010 7.4.2(a) “Every PRM is within the applicable horizontal distance specified in Table 8 of a boundary point that is required to be witnessed by Rule 7.3.1”.

RCS2010 7.4.2(a) was later revised to read “At least 2 PRM's must be within the applicable horizontal distance specified in table 8 of a boundary point that is required to be witnessed by Rule 7.3.1”.

Business Rule C485 now tests that there are at least 2 PRM's that are within the applicable horizontal distance specified in table 8 of a boundary point that is required to be witnessed.

The rule will fail if no PRM's are within the specified distance of any primary boundary point that is required to be witnessed.

Warning: The test does not include Non Primary, Lease and Stratum boundaries marks unless those boundary marks are coincident with a created Primary boundary.

MAR 1653 has been raised to address this situation.

Manual intervention is required where Lease and Stratum definition occurs.

An unintended consequence of changes to Mark Purpose functionality is that surveyors are obliged to accord an unsuitable Mark Purpose to system added marks.

System added Pseudo vectors that require editing must be captured as true vectors.

System Added marks should not be used to define the start or end point of user defined lines or vectors. Topology issues arise where they are used.

CSC_S03b – Mark Detail

New Mark Purpose

• DCR 3252 introduced a system code for the new mark purpose - "BNND" (Boundary Not Defined). It will be displayed in the dropdown lists in capture as "Not Defined" (consistent with other boundary mark purposes).

Conversion

• A conversion script has been run to update the Purpose of System Added marks to "Not Defined"
• The conversion script has also updated the node work purpose of submitted data to "Not Defined" if capture data is still present (Survey is not yet approved).

Mark Detail window (CSC_S03b)

• When editing a system added mark, only the Mark Ref field will be editable. This will allow the user to give a more meaningful reference to their marks while protecting the information pertaining to the Landonline mark that was automatically captured from changes.
• When selecting "Not Defined" for Mark Purpose the message 15299 will be displayed to the user.

Vector Capture

• All vector details (including From and To Mark Ref) in the vectors list and vector detail sections will not be editable for System Added Pseudo vectors (Starting or ending in System Added mark). Mark information will still be editable if the "To Mark" is not System Added.
• For External users, all Pseudo vectors are System Added and are therefore not editable.
• Internal users are allowed to manually enter Pseudo vectors (but they can no longer start or end in System Added marks). Details for these vectors will be editable.
• System Added marks will not default when creating new vectors. Mark State "System Added" and Mark Purpose "Not Defined" will not default.
• When the user attempts to enter a System Added mark for the FROM or TO mark, error message 15300 will be displayed.
• If the TO mark is system added, all Mark details will be disabled (not editable). This is unlikely to happen because Pseudo vectors are usually created with the System Added mark as the From Mark.
• If the user selects "Not Defined" for Mark Purpose (Mark Information section), message 15299 will be displayed.

Spatial

• If the user attempts to unlink a linked System Added mark (Blue Node), message 128203 will be displayed.
• If the user attempts to link an unlinked System Added mark (Pseudo vector ending), message 128204 will be displayed.
• If the user spatially adopts a line or vector starting or ending in a System Added mark, message 128205 will be displayed. This will also apply to "Adopt Observation Sequence" and "Process Balance Parcel" if one of the vectors/lines that is adopted ends in a mark already added automatically by the system.
• If the user selects a System Added mark as a start or end point while capturing an irregular boundary, message 128206 will be displayed.
• System Added marks will be created with a purpose of "Not Defined".
• Automatic mark linking will exclude system added marks from the linking process. This will prevent System Added marks for Pseudo vectors from being linked where it is within tolerance of a Landonline mark.

CMN

A change has been made to a function to determine Boundary Marks Defined by Survey not to rely on capture data when checking if a mark was System Added. The new Purpose in the node works table will now be used instead.

Respond accordingly if the following messages occur:

Message 128203: The mark you are trying to unlink was added by the system during missed mark functionality. It must remain linked or be deleted from capture.

Action: Refrain from trying to unlink the mark.

Message 128204: The mark you are trying to link was automatically added by the system via the merge irregular line functionality. It cannot be linked.

Action: Refrain from trying to link the mark. Alternatively, capture the mark by measurement or adoption.

Message 128205: A system added mark cannot be the start and/or end point of an adopted line or vector.

Action: Replace the system added mark with a captured mark defined by adoption.

Message 128206: You cannot use the selected system added mark to define the end point of an irregular line. The capture irregular line process has been terminated.

Action: Replace the system added mark with a captured mark defined by adoption.

As a result of the Auckland council amalgamation, 7 Territorial Authorities will merge into the one. From day one (1st November 2010), TA Certifications will need to be completed under the new Authority.

From (Old) - Firms involved

To (New) - Firms involved

1. All Users from the Old firms will be moved to Users of the New firm, with the same privileges assigned to them.
2. All transactions under 'My Work' work will be moved to the same user in the New firm.
3. All transactions under 'Unassigned' work will be moved to the 'Unassigned' queue of the New firm.
4. All transactions under 'Completed' work will be moved to the 'Completed' Folder of the New firm.

• All Certificates within a 'Package' will have to be re 'Certified' before the Package will be able to be 'Signed' – thus making the whole package come under the Auckland City.
• There will be some Transactions (about 50% of approx 60) from the 'Franklin District Council' firm that will now fall under 'Waikato District' or 'Hauraki District'. These will be moved by script to the unassigned queue of these 2 Firms.
• Old Firms will not be able to be selected from the drop Down List by the Surveyor – thus all new work will be sent to the New Firm.
• All Surveys not yet submitted to LINZ that show the Old Firm name, will be updated to the New Firm automatically.

Currently the Pre-validation report lists a variation of failures/warnings for each Business rule. The number of reports per rule is inconsistent and some users have expressed a desire to view all Warnings/Failures.

It is inexpedient to list exhaustively for each rule because of character field limitations and performance impact.

In order to establish consistency in reporting Business Rule Warnings /Failures at Pre-validation each list has been extended to list the first 50 Warnings /Failures for almost every Automatic Business Rule. Where a rule currently reports Zero returns no change has been made.

Failed business Rules were appended with %s and the specific details were also reported. The %s should not be displayed.

The P rules that report conflict will now only detail the specific features. The %s is not displayed.

Rule C430 reports more failed marks at Submit than it does at pre-validation.

The rule is reporting fails where positions defined as 'unmarked' on an underlying survey are defined as new boundary points and linked on the new survey. The pre-validation report passes correctly but the same rule is failing at Validation. It should only be failing where the new mark is captured as 'Unmarked'.

Rule C430 is including marks that are already commissioned and have been created by another survey.

The rule has been corrected to ensure that the boundary marks selected for testing each new primary parcel are created by the current survey. The rule will fail for marks on new primary parcel boundaries where the marks have a state of NEW and mark type of Unmarked or Unknown.

Enhancement 1560 implemented for the new cadastral rules, introduced functionality that identifies boundary marks requiring witnessing (Boundary marks defined by Survey). The same functionality may be used to pass this information to the Landonline Adjustment datablade. There are two components to this rule; a requirement that all applicable vectors meet the accuracy and a requirement that there is at least one applicable vector per mark defined by survey. Only the requirement that all meet the accuracy was included in the adjustment datablade thus affecting rules 3.6 and 7.3.2a.

A stored procedure hot-fix script has been run to apply to the database in conjunction with a new version of the Adjustment datablade. The function to identify marks (nodes) requiring witnessing was designed with pre-validation and validation in mind. It will work correctly for pre-validation and validation because data for the survey in the capture staging tables (cpl) is still present. The function excludes system added marks which can only be identified from the capture staging tables.

When a survey is not within 10 kilometres of a geodetic mark (6th order or higher), Business rule C440 will sometimes report incorrectly in both Pre-validation and Validation.

The rule reports a failure with no Node ID reported. This will only happen when there are no geodetic marks (6th order or higher) within 10km.

The rule now reports only when there are Geodetic Marks (6th order or higher) within 10 Km of the survey and none have been connected. The rule also reports the node ID of the nearest mark. Any linked marks beyond that limit are not reported.

When centreline parcels are extinguished, rule C41B sometimes reports incorrectly. The problem is encountered when the Capture parcel id for a Centreline parcel is the same as an existing LOL parcel id.

A fix has been applied to production to prevent the occurance.

C484 should not include boundary marks in the report that non- boundary marks do not have unique alpha numeric identifiers. C484 was warning that boundary marks defined by adoption did not have a unique alpha numeric identifier.

The Pre-validation and requisition procedures have been changed to test only non-boundary marks. IBM have also pre-pended the plan type to the mark plan reference prior to blanking the mark number - this ensures the full plan ref for the mark is still shown.

Surveys in workspace with discontinued Survey purpose will not have a rule version after conversion because no SGR 2010 rule set was associated with those survey purposes. Error message 124431 is encountered when the user changes the survey purpose to a current purpose.

A hot fix solution has been applied. Production Change Request (CHG 33206) has been applied the fix to Production.

This change is to ensure that Landonline does not show Lease areas on the Survey diagrams for primary or non primary parcels.

With the introduction of MAR 1509 (DC 445) lease parcels are now required to be captured with an area.

If the lease parcel is for a Lease over 25yrs the parcel is captured in the primary layer. However, if the lease parcel is for a Lease under 25yrs the parcel is captured in either the Secondary or Tertiary layers and an area is shown. When the user is in Plan Generation, and the Survey Traverse diagrams are laid out on the layout sheets, the area associated to the non-primary lease parcel is displaying. Only Title diagrams should display the area against the parcel. No areas should be displayed on the Survey diagrams for primary or non-primary parcels.

Neither Online nor Offline tools show non primary parcel areas on any survey diagrams.

Pre-validation rule Y001 refers 'Replaced' marks. New term is 'Renewed'.

New term 'Renewed' applied.

When a user modifies a mark symbol in the Layout window, the modification (including the font size) is saved to the database. The system recreates the mark's properties applying the values from the database. When the default property changes (eg changing the mark purpose or a system wide change to the default property implemented via static data change), the default property (which cannot be changed by the user) is overwritten by the property saved in the database. The property in the database should be ignored for properties that cannot be changed by the user.

Resolved

When a series of failures occur while processing an extract, the batch rolls back the status of the batch entry to "Pending" instead of setting it to "Failed". While monitoring the job in production, it was found out that the batch successfully updates the status of the batch entry to "Failed" but shortly after that, it changes back to "Pending". This would indicate that a rollback has occurred. The minimum fix for this is to commit the transaction right after a change of status (to "In Progress" and "Failed").

There were two entries in the batch queue for the same user having exactly the same AOI. The first had a delivery method by email. This entry was successfully set by the batch to "Failed". There was however an error entry in the batch log stating an "sql -284" error followed by "MAPI profile not found". The batch must have been trying to send a failure notification via email.

The second entry had a delivery method by "Online Message". This was the entry being rolled back to "Pending". The -284 error is also recorded in the batch log. There must have been an error sending the Online message (notification of failure) causing the transaction to rollback.

Resolved

When the user uses the Hide feature (unticks the feature tick box) functionality in Maintain Diagram Layers, error 32029 will be encountered when opening the Layout window. The initial error encountered is an Informix -696 error.

Resolved

The Filter Vectors by observation class functionality does not work for the new survey classes introduced by the Rules for Cadastral Survey 2010. The filter relies on system codes 'Reduced Observation Cadastral Class' and 'Reduced Observation Geodetic Class'. Confusion may be caused by the presence of 'old' class A, B & C values being present.

Codes A, B & C have had the descriptions and values changed to distinguish them in the class selection window.

The data blade is providing accuracy test information that is not required – which leads to additional surveyor effort or unwarranted requisitions.

1. Rule 7.4.1 does not need to be tested for accuracy
2. The data blade does not have sufficient refinement to adequately subset or exclude various marks based upon the information regarding the mark that Landonline obtains from the Surveyor. The data blade therefore list marks in various situations as unnecessarily failing, thus requiring surveyors to explain away the failure.
3. Some error messages were potentially confusing

The data blade now has refined capability to subset and exclude vectors as required in different situations and some wording has been refined.

1. The test previously described as "Rule 3.7, Rule 7.4.1 and Rule 3.6: Misclose of obs from PRMs to boundary marks" has been removed. Rule 7.4.1 does not require an accuracy test, and is covered by other business rule testing. Rule 3.6 is covered by other accuracy tests.
2. Several rules have been refined in the selection of vectors to be tested. This means that for some vectors relative accuracy tests are not longer applied, though residual (misclose) tests still are. That is, the potential accuracy (design) of the survey is not assessed, but the quality of the survey (implementation) is still tested.
   
   The following vectors are no longer included in relative accuracy tests:
   1. vectors excluded by ruling LINZR65312
   2. vectors to marks only connected by bearing observations (eg orientation, shots to trigs)
   3. vectors between marks with SDC status.
3. There have been some changes to the way that the results of rules testing are worded.
   1. In the testing of compliance against rule 3.6The word 'misclose' has been replaced with "residual", to avoid confusion with a 'Bowditch misclose' that surveyors commonly use.
   2. where there is a 95% pass rate requirement the wording has changed from something like:
      
      Tested for 20 vectors of which 1 failed
      More than the required 95% passed
      
      to
      
      Test achieved required 95.0% pass rate
      19 of 20 vectors meet accuracy requirement