Published
Rule No
|
Rule Description in UI
|
Full Description
|
0
|
Schema check
|
Schema check-
|
|
|
ᄋ Scheck structure of file
|
|
|
ᄋ Checks for all required and conditionally required elements and attributes.
|
|
|
ᄋ Checks for valid enumerations against NSW enumerations file
|
1
|
Plan purpose
|
Checks that the Purpose of the survey is recorded in the file
|
2
|
Plan give effect to purpose
|
Plan gives affect to the purpose of survey
|
3
|
lot numbering
|
New lots have a numeric identifier
|
4
|
valid secondary parcels
|
Check of secondary parcels attributes (e.g. easements)
|
|
|
ᄋ Secondary parcel identifiers must start with an Alpha can be followed by another Alpha or numeric or character without spaces ヨ except for lease parcels.
|
|
|
ᄋ The parcel format is valid. (standard or stratum only)
|
|
|
ᄋ Secondary parcels must not be part lots.
|
5
|
Parcel attributes
|
Parcels must have a valid Parcel Format, Class and Use
|
6
|
Valid parish
|
Validity of parish
|
|
|
ᄋ Name
|
|
|
ᄋ And must be in correct County
|
7
|
Valid County
|
Validity of county
|
8
|
Valid LGA
|
Validity of LGA
|
9
|
Valid Locality
|
Existence of locality name, if locality element is used
|
10
|
Valid Areas
|
Validate areas for proposed lots (calculated vs stated)
|
11
|
Multipart lot areas
|
Validate Part lot areas and total areas, including only parcel with class of モlotヤ can have parts
|
12
|
New lot area shown
|
All proposed lots must have an area
|
13
|
Parcel overlaps
|
Basic topology of parcels that have a coordinate geometry.
|
|
|
Lines must not cross lines in own parcel or adjoining parcels.
|
14
|
Multipart lot attributes
|
A lot that is described in parts must have at least 2 parcels
|
|
|
ᄋ Part parcels must have a parent multipart parcel
|
|
|
ᄋ The following attributes for the parts must be the same as the parent multipart parcel:
|
|
|
o class
|
|
|
o state
|
|
|
o Format
|
15
|
Parcel topology
|
Parcel geometry must have a sequence of lines where the end of one line is the start of the next
|
16
|
Misclose
|
Check misclose in parcels in within prescribe tolerance.
|
17
|
Line attributes
|
Each line that makes up a polygon of a proposed parcel must:
|
|
|
ᄋ have a set of observations consisting of a bearing and a distance value
|
|
|
o if the parcel format is standard a horizontal distance value is also required
|
|
|
ᄋ Each curve that makes up a polygon of a proposed parcel must have a corresponding arc observation and must have attributes for:
|
|
|
o arcType
|
|
|
o chordAzimuth
|
|
|
o length
|
|
|
o radius
|
|
|
o rot (rotation of either clockwise or counter clockwise)
|
18
|
Valid Instrument point
|
All instrument points in the plan must contain a valid InstrumentPoint@pntRef which is referenced to a valid CgPoint (i.e. not a Centroid)
|
19
|
All points used
|
Validates survey points
|
|
|
ᄋ All CgPoints that are not sideshots must be part of a line
|
|
|
ᄋ All instrument points must be part of an observation
|
20
|
RM/PM dimensions
|
Monument point must be connected to by a ReducedObservation
|
21
|
SCIMS date
|
SCIMS date must be within 6 months of date of survey
|
22
|
SCIMS sketch
|
PM Sketch has been lodged for placed control marks
|
23
|
Offset boundary mark
|
Boundary marks must be placed on boundary corner. Must not be offset.
|
24
|
unmarked boundary
|
RMs must be placed for unmarked boundary corners
|
25
|
RMs within 30m
|
RMs must be within 30m of the point being referenced
|
26
|
SCIMS details
|
Control mark attributes (Coordinates, class, order) must match SCIMS at date of survey
|
27
|
close points
|
Checks the file for the existence of points that are within 5mm of each other. Probably an error
|
28
|
Datum terminals
|
Datum terminals must be labelled "A" and "B"
|
29
|
Datum dimensions
|
Checks datum line bearing and distance against those calculated from the coordinates of the terminal points
|
30
|
Verifying radiation
|
Checks for a verifying connection to a third PM from one of the datum terminals
|
31
|
RMs for urban plan no road frontage
|
Check for the required No of RMs for urban plan with no road frontage
|
32
|
Found RM origin
|
Checks for the origin of all found RMs
|
33
|
RM connect to one boundary point
|
Checks that each RM connect to only one boundary point
|
34
|
PMs new road
|
Checks for connection to the required No of PM's for new roads
|
35
|
RMs road frontage terminals
|
Checks for the connection to RMs at the terminal points of the survey where new parcels abut a road.
|
36
|
RMs for total road frontage
|
Checks for connection to the required No of RM's for the total road frontage of new parcels
|
37
|
PM to PM dimensions
|
Checks the dimensions between PM's compared to those calculated from the coordinates of the PM's
|
38
|
PM connect to survey
|
Checks that at least 2 PM's are connected by direct connection to 2 separate points forming boundaries of new parcel.
|
39
|
PMs close
|
Checks that measurements between all PM's found or placed, and connections to the land surveyed, are proved by closed survey
|
40
|
Marks exist
|
Plans of survey must have survey marks in the file. Compiled plans must not have survey marks in the file
|
41
|
MM Radial Search
|
Checks for Established Marks within 300m for urban survey OR 1000 m for rural survey. If 2 or more marks exist then plan should have an MGA datum
|
42
|
PMs required for number of parcels
|
Checks that the survey connects to the specified number of PMs based on number of lots in the plan
|