Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
Appendix 5:
Cadastral Survey Data (CSD)
Digital Data Format
Version 1.1
Includes updates for
Versions 1.2 & 2.0
for polygon record changes;
GDA94 requirements;
Carbon Rights, Carbon Covenants
and Tree Plantations;
User Guide
For further technical specification of this format refer to:
The CSD DATA FORMAT AND REQUIREMENTS Version 1.1
available from:
Manager- New Subdivisions
Information Services Division
Western Australian Land Information Agency (Landgate)
PO Box 2222
MIDLAND WA 6936
Appendix 5
Page 1 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
1.1.
Digital File Lodgement Requirements
The following documentation is provided as Landgate’s requirements for the lodgement of digital
survey data. Version 1.0 of the Cadastral Survey Data (CSD) file format was distributed to software
developers, educational institutions and to surveyors as part of the Accreditation process. The
documentation has been reviewed, to remove ambiguities and updated, to ensure it meets
Landgate’s internal requirements. This revised edition, Version 1.1, has also been provided to
known software developers and some surveyors to confirm the format and as an aid in the
lodgement of digital data with Landgate.
This User Guide is intended an aid for surveyors when compiling CSD files for lodgement with
Landgate.
1.1.1.
Business Rules
Landgate has a number of key data requirements in relation to how a file is to be created for digital
lodgement of survey data, these are:
•
The data is to be lodged in the file format specified by Landgate.
•
The accuracy and completeness of the data is to be the surveyor’s responsibility.
•
The data is to be comparable with the survey plan, as lodged, ie angles and distances will be
as shown on the plan. Angles will be in degrees minutes and seconds and distances will be
to a minimum precision of three decimal places.
•
All polygons on the plan, including the surround and easements, are to be included in the file
except polygons shown in an inset, for road closure and amalgamation purposes.
•
All files will contain a “surround” polygon or multiple surrounds linked by traverses for those
plans with split subjects of survey.
•
All surveyed points on each boundary to be included for each polygon.
•
The file is to contain all available ties to the geodetic framework or if none, ties to the existing
cadastre to allow accurate positioning of the survey.
•
One file to be lodged for each Plan, with the digital file number written on the survey
document in pencil or attached thereto in a temporary manner.
•
Field book numbers are to be included in the file, if known prior to lodgement of the plan. See
Data Requirements (Record 12 polyident2)
During the legal check of the plan, Landgate will undertake an electronic validation of the data
supplied. Failure to pass this validation will cause a stopped document charge and require a new
copy of the data to be lodged.
Appendix 5
Page 2 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
1.1.2.
1.1.3.
Special Survey Area Subdivisions
•
There is a preference for coordinates to be supplied based on GDA 94 or Perth Coastal Grid
(PCG 94) rather than plane coordinates.
•
Observed data is required, as per the Survey Practice Guidelines for Subdivisions within
Special Survey Areas under Regulation 26A of the Licensed Surveyors (Guidance for
Surveyors) Regulations 1961. Observed control values must be lodged in an eFB_CSD file
(refer guideline 7.1).
Accuracy & Completeness
It is the surveyor’s responsibility under the accreditation process to ensure that the data lodged is
an accurate representation of the survey and to ensure it contains only that information relevant to
the subject of the survey. Any discrepancies identified will be the surveyor’s responsibility to resolve
and will incur standard Stopped Document charges.

Note:
Attributes and Definitions written in Italics could be expected to be input by software and may not be
the concern of a user.
RECORD ID 0
Miscellaneous Remarks
Optional: May appear anywhere in the file.
Record example:- 0,”This is a sample of a miscellaneous remark”
ATTRIBUTE
DEFINITION
recordid
remarks
The record identification number.
Any remarks the user wishes to include. (max 80 characters)
RECORD ID 1
Main Header Record
Mandatory. Contains file header details. Must appear in record order.
Record example:- 1,”1.1”,19940705,P,”A CAMPBELL”,”LOT 1 OF SWAN LOCATION 1305”
ATTRIBUTE
DEFINITION
recordid
version
datecreated
coordmode
The record identification number.
The CSD file version number.
Date this file was created.
Indicates the type of coordinates used in this file.
P P= Plane coordinates. File should not include Record IDs 3 - 4. Coordinates
are determined using plane trigonometry and a local datum.
T T= Transverse Mercator coordinates. File must include Record IDs 3 - 4.
Rigorously determined TM projection coordinates. This can be UTM or a
LANDGATE approved TM local grid such as PCG 94.
G G= Geographicals. File must include Record ID 3 but not 4. These are
rigorously determined latitudes and longitudes.
Optional author of the file. (max 20 characters)
Optional user description of the file. (max 40 characters)
author
description
Appendix 5
Page 3 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
RECORD ID 2
Record Count
Mandatory. Provides a count (for audit purpose) of each and every record type
appearing within this file. Must appear in record order.
Record examples:- 2,0,12
2,1,1
2,2,3
ATTRIBUTE
DEFINITION
recordid
recordidno
recordno
The record identification number.
The record identification number being counted.
The number of records occurring for that ID.
RECORD ID 3
Spheroid constants used in coordinate computations
Mandatory if the coordinate mode (Record ID 1) is geographical or TM
projection. Must appear in record order.
Record example:- 3,”GRS80”,298.257222101,6378137.0
ATTRIBUTE
DEFINITION
recordid
sphernme
The record identification number.
The name of the reference spheroid. With the implementation of the Geocentric
Datum of Australia 1994 (GDA 94) after 4th December 2000, the only valid value
is “GRS80”. This covers Australia, Christmas and Cocos Island regions. . (max
40 characters)
spherinvflat
spheraradius
Appendix 5
The inverse of the flattening. At the moment the only valid value is:
298.257222101.
The a radius. At the moment the only valid value is:
6378137.0
Page 4 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
RECORD ID 4
Projection constants used in coordinate computations.
Mandatory if the coordinate mode (Record ID 1) is TM projection. Allows for
different projections such as Map grid of Australia (MGA), PCG94 . Must appear
in record order.
th
The implementation of GDA94 on 4 December 2000 requires that Project grid
co-ordinates be defined in relation to grid projections based on GDA94
geographicals.
Record example:4,50,”MGA”,49,111.0,6.0,0.5,500000.0,10000000.0,0.9996,0.0
4,1,”PCG94”,1,115.8166667,0.6416666,0.0,50000.0,3800000.0,0.99999906,0.0
•
All attributes must be provided if a Transverse Mercator projection is used.
•
Trailing non significant zeros may be omitted as shown in the example above.
ATTRIBUTE
recordid
tmzone
projnme
zonecm
cmzone
zonewid
zoneolap
falseast
falsenorth
centscalefact
origlat
Appendix 5
DEFINITION
The record identification number.
The TM zone of this particular file.
If projection is UTM, valid zones are 47 - 52 for WA, Christmas and Cocos Island
Region.
If projection is local, such as PCG94 then the only valid zone is 1.
Name of the projection. either, MGA or PCG94. (max 40 characters)
Zone number corresponding to the central meridian in cmzone.
Longitude of central meridian corresponding to any particular zone.
Zone width.
Zone overlap. Current valid values are:- UTM = 0.5 and PCG94 = 0.0.
Easting of the false origin.
Northing of the false origin.
Central scale factor.
Latitude of the true origin.
Page 5 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
RECORD ID
10
Point Record
Mandatory. Must appear in record order.
Record examples:10,1,50123.469,49861.098,456.532,0.020,T,O,,Y
10,2,50617.135,49747.483,256.823,0.001,L,S,”KAL87”,Y
•
If a Point record is referenced by a Line, Azimuth or Angle record then it must be supplied.
•
Existing SSMs must have the SSM name as the pntlabel.
ATTRIBUTE
DEFINITION
recordid
locpntno
xcoord
ycoord
zcoord
pnthoracc
pnthormethod
(Wescom “Capture”
= Point Code)
The record identification number.
Local point number unique within this file.
X coordinate of point in metres or degrees.
Y coordinate of point in metres or degrees.
Optional height of point in metres. Based on AHD.
Estimated accuracy of the horizontal coordinates in metres.
Code describing what method was used to establish the horizontal
coordinates of the point.
D= digitised or scaled from hardcopy graphic
T= traverse adjustment - generally all traditional surveys that are not Precal.
F= transformation - map projection conversions
K= keyed in - eg. by co ordinates
G= graphical construction - eg. CO-GO calculated
L= least square adjustment
P= precal - all SSA surveys.
Code describing the type of point.
S= standard survey mark
O= Other
T= temporary control point
Optional label of point for identification, but mandatory for a pnttype of S.
(SSM name/number) (max 20 characters)
Point surveyed.
Y= yes
N= no
If point has been surveyed previously, code = Y
If point is surveyed by this survey (includes points not yet marked in SSAs),
code = Y
pnttype
pntlabel
surveyed
Appendix 5
Page 6 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
RECORD ID 11
Line Record
Mandatory. For a line to exist, so must the 2 supporting end points. Must
appear in record order.
Record example:
11,1,1,2,S,Y,23.150,G,4000,M,R,
Appendix 5
•
Both of the point records referenced must exist.
•
If a Line record is referenced by an Angle, Azimuth or Polyline record then it must exist.
•
If a Line record is referenced by a Circular arc record then it must exist with a linconst of “A”.
•
If a Line record is referenced by a Topographic string then it must exist with a linconst of “T”.
Page 7 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
ATTRIBUTE
DEFINITION
recordid
loclinno
locfrompnt
loctopnt
linconst
(Wescom “Capture”
= Line Shape)
The record identification number.
Local line number unique within this file.
Local point number where line starts.
Local point number where line ends.
Type of line construction.
S= straight line
A= clockwise arc
T= topographic string
P= parallel of latitude
M= meridian of longitude
Line surveyed
Y = yes - If line was previously surveyed, is surveyed by this survey
including not yet actually marked in an SSA.
N = no - lines never surveyed as defined by Lic. Surveyors Regs.
Length of line in metres to 3 decimal places.
For arcs this is the Arc Distance
For topographic strings this is the imaginary line between each end of the
string. A “Topo string” being a high water mark.
The datum for the distance value.
G= ground level
S= spheroid
Estimate of distance accuracy expressed as a ratio.
Code describing derivation of distance.
M= measured. - Physical measurement, includes precal and original
distances.
C= calculated. - Not physically measured itself but calculated from a
physical measurement. eg: Arc distance, imaginary topo line.
V= derived. - Unsurveyed. eg derived from digitised coordinates of the two
end points.
D= described - Unsurveyed. eg legal description.
A= approximate - highly inaccurate. eg scaled.
Code describing line type.
For adjoining polygons, the following order of precedence should be
used:(see examples below)
R= Cadastral Road - includes all lot boundaries abutting roads.
I= Cadastral Internal - all remaining cadastral boundaries not listed here.
W= Cadastral Water - cadastral boundary that is also a topographic water
feature.
C= Cadastral Construct - eg. road construct lines and traverses.
E= Easement
K= Easement Construct. - Cadastral connection to an easement.
N= Control Network - eg. SSA.
Optional label of line for identification. (max 35 characters)
surveyed
distance
distdatum
(Wescom “Capture”
= Line Datum)
distacc
distderiv
(Wescom “Capture”
= Line Code)
lintype
linlabel
Appendix 5
Page 8 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
Examples of lintype, demonstrating order of precedence:
•
If a road abuts a lot then the line type is R for road.
•
If two lots abut then the line type is I for Cadastral Internal.
•
If a lot and an easement abut then the line type is I for Cadastral Internal.
By definition, outside of the precedent rule:
•
If two road polygons abut then the line type is C for Cadastral Construct.
RECORD ID 12
Polygon Record
Mandatory for subdivisions. For a polygon to exist, so must the lines
constructing the polygon. Must appear in record order.
Record example:- 12,1,50070.223,49931.437,F,”34”,,1632,”68”,”ORRONG ROAD”
Appendix 5
•
Surround Polygon or Multiple Surround polygons linked by traverse for those plans with split
subjects of survey. This is the extent of the survey on the plan. A surround polygon/s is
required for all plans, this includes surveys of one polygon.
•
All lots, locations, roads, road truncations, road widenings, ROWs, PAWs, closed roads and
any other primary tenure polygon within the extent of survey require a polygon record.
•
A polygon is required for each severance or segment of an allotment.
•
Easements must also be captured but are not considered as primary tenure polygons and
are therefore not considered to be inside the surround for the purpose of area validation.
•
An easement polygon is required for each allotment the easement encumbers.
•
Where an easement passes through a polygon, sufficient connections to cadastral corners to
position it, are required.
•
Easement polygons may contain cadastral points and lines.
•
All polygons are to be captured in a clockwise direction.
•
All polygons must be named and conform to the naming convention defined in the Polygon
Naming Convention: Page 11 herein.
•
All polygons must have associated polyline records.
•
Street address to be supplied if available.
Page 9 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
ATTRIBUTE
recordid
locpolyno
centx
centy
polytype
polyident1
polyident2
area
houseno
streetnme
Appendix 5
DEFINITION
The record identification number.
Local polygon number unique within this file.
X coordinate of centroid in metres or degrees.
Y coordinate of centroid in metres or degrees.
Polygon type. (refer to the Polygon Naming Convention)
A= agricultural area
C= closed road
E= estate area
F= TLA lot (freehold land, includes lots for revestment)
I= land to be included into an allotment
L= location
M= marine park
O= right of way
P= pedestrian access way
R= road casement
S= suburban area
T= townsite lot
W= road widenin
X= easement
Y= miscellaneous
Z= surround
First polygon identification (refer to Polygon Naming Convention).
Dependant upon polytype (max 35 characters)
Second polygon identification (refer to the Polygon Naming Convention
below). (max 35 characters)
Area of the polygon to the nearest square metre.
Optional, house number. (max 6 characters)
Optional, street name. (max 35 characters)
Page 10 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
1.2.
Polygon Naming Convention
1.2.1.
Surround
1.2.2.
Appendix 5
•
A surround polygon/s are required for all plans registered.
•
The surround polygon/s are to encompass all polygons subject to the survey only. Polygons
physically separate from others within the survey are to be captured as separate surround
polygons linked by traverse. All points along subject polygon boundaries are to be captured.
•
For the “Surround” polygon polyident1 will contain the word “Surround” and polyident2 will
contain the numbers of all field books used for the plan of subdivision. Field Books registered
at the time of plan registration will be added by LANDGATE. Separators of dashes (to
indicate consecutive numbers) and commas (for non consecutive numbers) should be used.
eg. “67120,67122-5,67127”
Polytype
Polyident1
Polyident2
Z
SURROUND
67120,67122-5,67127
Z
SURROUND
COMPILED
TLA Surveys
•
For TLA Lots polyident1 is the allotment number; polyident2 is not applicable and will
remain blank.
•
If an allotment comprises two or more polygons then there will be a duplication of polytype,
polyident1 and polyident2. Additional information relating to multiple segments or part
allotments is not required. See example for lot 23 below.
Polytype
Polyident1
Polyident2
F
TLA Lot No.
N/A
F
6
F
23
F
23
Page 11 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
1.2.3.
Polygon record Changes for Version 1.2
•
For subdivisional surveys that create Normal Lots, ROW’s, PAW’s or Vesting lots and Survey
Strata plan Common Property lots, the polygon records will be:
Polytype
Polyident1
Polyident2
F
TLA Lot No.(Lot Type)
N/A
Normal Lot
F
21
N/A
Right of Way
F
12(ROW)
N/A
Pedestrian
Access Way
F
15(PAW)
N/A
Vesting Lot
F
24(VEST)
N/A
Survey Strata
CP Lot
F
10(CP)
N/A
The following data is an extract of polygon records from a version 1.2 CSD file as illustrated in the
table above.
•
12,1,3106.355,3161.914,F,"21","",633,"36","HEDGES RETREAT"
•
12,2,3108.758,3108.502,F,"12(ROW)","",91,"",""
•
12,3,3108.567,3161.654,F,"15(PAW)","",73,"",""
•
12,4,3107.709,3143.266,F,"24(VEST)","",672,"34","HEDGES RETREAT"
•
12,5,3107.234,3126.880,F,"10(CP)","",480,"",""
For SOLE subject surveys of Road extensions or widenings, the polygon records will be:
Polytype
Polyident1
Polyident2
Road
F
5(JOHN STREET)
N/A
Road Widening
F
23(WDG)
N/A
The following data is an extract of polygon records from a version 1.2 CSD file as illustrated in the
table above.
•
12,3,3107.713,3144.219,F,"5(JOHN STREET)","",672,"",""
•
12,4,3106.228,3126.810,F,"23(WDG)","",680,"",""
No spaces should be placed between the lot number and lot type in the polyident1 field. The lot
type must be enclosed in parenthesis of type ().
Appendix 5
Page 12 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
1.2.4.
Polygon record Changes for Version 2.0
For survey companies that are able to modify their existing CSD file creation applications,
LANDGATE is also promulgating the use of CSD File format version 2.0.
This version makes further changes to the polygon records that will assist in the identification of lot
type for pre-cal subdivisions.
Surveyors who choose to submit CSD files in this format must identify the file as being a version
two (2) file by placing “2.0” in the version field of the main header record.
1,"2.0",20000329,P,"A. SURVEYOR","PART JANDAKOT A.A. LOT 215".
Version 2.0 changes will also be limited to the polygon record fields as shown below. That is the
polyident1 field will be reserved for lot number only (or it may be left blank if not applicable) and the
polyident2 field will be used in describing the type of lot, purpose or road name.
Appendix 5
Polytype
Polyident1
Polyident2
Normal Lot
F
34
N/A
Vesting Lot
F
24
VEST
Common Property
Lot
F
6
CP
Right of Way
O
12
ROW
Pedestrian Access
Way
P
15
PAW
Truncation
R
4
TRUNCATION
Truncation
R
N/A
TRUNCATION
Road
R
5
JOHN STREET
Road
R
N/A
JAMES STREET
Road Widening
W
10
WDG
Road Widening
W
N/A
WDG
Page 13 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
The following data is an extract of polygon records from a version 2.0 CSD file as illustrated in the
table above.

•
12,1,3108.734,3108.567,F,"34","",671,"",""
•
12,2,3107.229,3126.810,F,"24","VEST",680,"",""
•
12,3,3105.629,3124.210,F,"12","CP",870,"",""
•
12,4,3107.429,3126.833,O,"12","ROW",680,"",""
•
12,5,3108.758,3108.502,P,"15","PAW",671,"",""
•
12,6,3108.237,3162.449,R,"4","TRUNCATION",33,"",""
•
12,7,3109.237,3164.345,R,"","TRUNCATION",18,"",""
•
12,8,3108.237,3162.449,R,"5","JOHN STREET",633,"",""
•
12,9,3109.237,3164.345,R,"","JAMES STREET",1035,"",""
•
12,10,3107.513,3144.541,W,"10","WDG",672,"",""
•
12,11,3103.513,3141.840,W," ","WDG",282,"",""
Note
The polygon record format for Crown Allotments will remain the same as version 1.1.
Appendix 5
Page 14 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
1.2.5.
Crown Surveys
•
Appendix 5
For Crown Allotments polyident1 is the Allotment number and polyident2 is the associated
crown allotment name.
Polytype
Polyident1
Polyident2
L
Location No.
District
L
67
WELLINGTON
L
2
SWAN
L
2
SWAN
S
Lot No.
Suburban Area
S
45
SOMERVILLE
S
23
AUGUSTA
T
Lot No.
Townsite
T
12
KARRATHA
T
34
BROOME
T
34
BROOME
E
Lot No.
Estate Area
E
545
BOLGART
A
Lot No.
Agricultural Area
A
23
APPERTARRA
M
Park Number
Marine Park
M
8
MARMION
Page 15 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
1.2.6.
Appendix 5
The Following Apply to Both Crown and TLA Surveys
•
For road polygons created on a Subdivisional surveys polyident1 is the road name and
polyident2 is not applicable and will remain blank.
•
For road widenings, created on a Subdivisional surveys polyident1 is the text “WDG”,
polyident2 is the allotment that these polygons are adjacent to.
•
For closed roads polyident1 is the text “CLOSED ROAD” and polyident2 is blank.
•
For easements and portion only covenants and notifications polyident1 is the section and
regulation of the relevant act under which the easement, covenant or notification is effective.
If an easement or covenant has been created by a deed and no Act applies polyident1 is to
be “Doc”. polyident2 is the allotment the easement encumbers.
•
For Inclusions polyident1 is the text “INCLUSION” and polyident2 is the allotment the land
is to be amalgamated with
Polytype
Polyident1
Polyident2
R
Road Name
N/A
R
CATHEDRAL AVENUE
R
TRUNCATION
R
TRUNCATION
R
TRUNCATION
R
JOHNSTON STREET
R
JOHNSTON STREET
W
Road Widening
Adjacent lot/location
W
WDG
101
W
WDG
303
W
WDG
303
C
Closed Road
N/A
C
CLOSED ROAD
Page 16 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
Appendix 5
Polytype
Polyident1
Polyident2
X
Regulation/Sec.
X
27A/5,8
3
X
27A/6
45
X
Doc
48
X
Reg 14I
6
X
Reg 14E,G,H,F
6
X
Sec 136C
7
X
Sec 136D or Sec 129BA
45
X
Sec 195 & 196
63
X
Sec 144
7
X
Sec 12A or Sec 70A
27
I
Inclusion
Allotment to merge
I
INCLUSION
561
Y
Miscellaneous
Page 17 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
Land Usage (Polyident1 in CSD file)
Carbon Right
Carbon Covenant - Benefit
Carbon Covenant - Burden
Caveat
Contaminated Site
Covenant – LAA 15
Easement - doc
Easement - LAA 144
Easement in Gross – LAA 195
Easement - Public Access LAA 195 & 196
Easement – P&D 167 Reg 5
Easement – P&D 167 Reg 6
Easement – P&D 167 Reg 7
Easement – P&D 167 Reg 8
Easement – P&D 167 Reg 9
Easement – P&D 167 Reg 33(a)
Easement – P&D 167 Reg 33(b)
Easement – P&D 167 Reg 33(c)
Easement – P&D 167 Reg 33(d)
Easement – P&D 167 Reg 33(e)
Easement STA 5D
Easement TLA 136C
Easement TLA 167A
Easement TP&D 27A Reg 5
Easement TP&D 27A Reg 6
Easement TP&D 27A Reg 7
Easement TP&D 27A Reg 8
Easement TP&D 27A Reg 9
Lease
Memorial
Notification
Profit a prendre
Restrictive Covenant – Benefit
Restrictive Covenant – Burden
Tree Plantation
Appendix 5
Page 18 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
RECORD ID 13
Angle Record
Mandatory. For an angle to exist so must the 2 lines forming the angle
exist. Must appear in record order.
Record example:- 13,1,2,2,1,34:45:55,0.0042,M
•
The point record and the two line numbers must exist.
•
Angles that form part of a polygon must be to whole second accuracy, provided in degrees,
minutes and seconds.
•
Angles must be supplied for the internal angle at every point within a polygon. This angle
must be the positive, clockwise angle between the line the angle is turned from and the line
the angle is turned to.
•
Angles turned to or from an arc (lineconst A) should be turned to or from the imaginary
chord of the arc. It is not necessary to provide a Line record (Record ID 11) for this imaginary
chord. See sketch below:
The Arc is
Line 27
The straight line
is Line 31
In this example, an angle is turned from Line
27 to Line 31 and the angle value which is
entered, is that of the angle between the
imaginary chord of the arc and the straight
line 31.
An Angle is Required at the End of Each Arc
Angles turned to or from a topographic string (lineconst T) should be turned to or from the
imaginary straight line joining the topographic string’s two end points. It is not necessary to provide
a Line record (Record ID 11) for this imaginary line as the distance will be in the line record with a
linconst of T.
Appendix 5
Page 19 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
In this example, an angle is turned from Line 12 to Line 19 and the
angle value which is entered, is that of the angle between the
imaginary line joining the end points of the topographic string and
the straight line 19.
Straight line is
Topo. string is
Line 12
Line 19
An Angle is Required at the end of the Topographical String
Previous documentation has stated that angles cannot be turned to or from topographic strings
(linconst T). This is no longer the case as ANGLES ARE REQUIRED, as above, to enable
calculation of an area.
RECORD ID 13
Angle Record (Cont.
Mandatory. For an angle to exist so must the 2 lines forming the angle
exist. Must appear in record order.
ATTRIBUTE
DEFINITION
recordid
locangno
locpntno
locfromlinno
loctolinno
angval
angacc
The record identification number.
Local angle number unique within this file.
Local point number at which angle is observed.
Local line number which angle is turned from.
Local line number which angle is turned to.
Angle value in degrees : minutes : decimal seconds
Estimated accuracy in decimal degrees. eg +/-15” = 0.0042, angles of 180
degrees have an accuracy of 0.0000.
Code describing the derivation of the angle.
M= measured. - Physical measurement, includes precal and original
angles.
C= calculated. - Not physically measured itself but calculated from a
physical measurement. eg: closing angle.
V= derived. - Unsurveyed. eg derived from two azimuth values.
D= described - Unsurveyed. eg legal description.
A= approximate - highly inaccurate. eg. from two magnetic bearings.
angderiv
(Wescom
“Capture”
= Angle Code)
Appendix 5
Page 20 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
RECORD ID 14
Azimuth Record
For an azimuth to exist, the associated line must also exist. Must appear
in record order.
Record example:- 14,1,1,1,30:45:5,0.0167,A,M
•
The line record and the point record must exist.
•
Azimuths supplied in a plane co ordinate file as aztype “M” will be treated as bearings,
observed azimuths will be maintained as such.
•
Only supply azimuths if they are observed or required for plan orientation.
ATTRIBUTE
DEFINITION
recordid
locazno
loclinno
locpntno
The record identification number.
Local azimuth number unique within this file.
Local line number to which this azimuth relates.
Local point number of end from where azimuth observed, if end point type,
or emanates from if mid type.
Azimuth value in degrees : minutes : decimal seconds.
Estimated accuracy in degrees.
Optional code describing the derivation of the azimuth. ?????
M= measured. - Physical measurement. This has to be an end type
V= derived. - Only applicable for mid azimuths and is derived from a mean
of the reverse azimuths calculated from the two end points.
D= described - Unsurveyed. eg legal description.
A= approximate - highly inaccurate.
Azimuth type.
O= astronomically observed end azimuth by solar or stellar means. It must
be observed and not calculated from end coordinates
M= unsurveyed mid azimuth. A mid azimuth of a line cannot be measured
and is derived from the algebraic mean of the end azimuths derived from
the two end points. Can also be used from a GPS baseline adjustment.
(Unless it is in a plane coordinate mode file when it can be accurately
determined by plane geometry)
azval
azacc
azderiv
aztype
RECORD ID 15
Circular Arc Record
To be used when a line defining a parcel's boundary is an arc. For an arc
to exist, so must the supporting line. An arc is always defined clockwise.
Must appear in record order.
Record example:- 15,12,10.060,50026.456,51044.837
For an arc to exist, so must the supporting line. With a line of linconst of: A= clockwise arc
Appendix 5
Page 21 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
ATTRIBUTE
DEFINITION
recordid
loclinno
radius
xarccentre
yarccentre
The record identification number.
Local line number representing arc.
Radius of arc in metres.
X coordinate of arc centre in metres or degrees.
Y coordinate of arc centre in metres or degrees.
RECORD ID 16
Topographic String Record
A topographic string is a series of coordinates used to define an
unsurveyed boundary such as high water mark. For a topographic string
record to exist so must its supporting line. Must appear in record order, be
sequential and consecutive in the file.
Record examples:- 16,43,1,50667.345,51500.835
16,43,2,50654.545,51534.567
•
The line record referenced must exist
•
All the internal points of topographical strings must be defined sequentially within each
record. The sequence number (strgseqno)must be in order starting from 1, with no gaps in
the numbers.
•
Points on Topographic strings need to be close enough to represent the boundary; not, as in
the past, close enough to merely define a curve to ensure an accurate area calculation.
ATTRIBUTE
DEFINITION
recordid
loclinno
strgseqno
The record identification number.
Local line number representing the string.
The sequence number of this particular point within the entire topographic
string.
X coordinate in metres or degrees.
Y coordinate in metres or degrees.
xcoord
ycoord
RECORD ID 17
Polyline Record
Mandatory for subdivisions. Specifies which lines are used to form a
polygon and in what sequence. A polygon is always defined in clockwise
order. Must appear in record order.
Record example:- 17,3,4,16,F
The line and polygon records referenced must exist and the sequence number (polyseqno) must
be in order starting from 1 with no gaps in the numbers.
Appendix 5
Page 22 of 23
Survey and Plan Practice Manual for Western Australia- Edition 9.0 March 2013
ATTRIBUTE
DEFINITION
recordid
locpolyno
polyseqno
The record identification number.
Local polygon number.
The sequence number of this line forming the polygon in a clockwise
circuit.
The local line number forming the boundary of the polygon.
The forward or reverse sense of this line to maintain the clockwise circuit.
F= forwards
R= reverse
loclinno
sense
RECORD ID 99
End of File Record
Mandatory. Defines the end of the file. Must be the last record. (No blank
lines to follow)
Record example:- 99
ATTRIBUTE
DEFINITION
recordid
The record identification number.
CSD File Requirements for Carbon Rights, Carbon Covenants and Tree Plantations
Polytype
Polyident1
Polyident2
Easement
Carbon Right
Lot number of affected land
Easement or Interest
Tree Plantation
Carbon Covenant - Burden
Carbon Covenant - Benefit
Appendix 5
Page 23 of 23