HOME  CDS Tutorial Manual

Exporting an ePlan LandXML

If you have imported an existing ePlan XML file or you have created a job from scratch then you are now in a position to export your LandXML into the ePlan format. In this example we will use the job imported from an existing ePlan LandXML. It can be seen below:
Click on the menu item File -> Export LandXML -> NSW -> Export LandXML. The following dialog is displayed (extra fields may need to be added):
All the fields need to be filled in. They are header type information needed for the ePlan LandXML to validate. Once you click OK you are prompted for a file name where the ePlan LandXML is to be created. You have now created an ePlan LandXML file.
The next stage is to validate the file. We first suggest that you run the file through "XML Notepad". This editor will check that the XML validates to the version 1.02 LandXML Schema. In the file below we have purposely created an error in the file. Along the left hand side we have a Tree View of the XML data. You can see the major headings for Units, Coordinate Systems etc.
We have purposely changed the "pntSurv" value for the first CgPoint. It is not a valid enumeration for that data type. Along the bottom row there is an "error list". It lists the errors. If you left double click on an error it brings up the relevant entry in the XML which you can update. If you left click on the entry and then left click again
it will bring up a list of the allowable enumerations if available. In this case we can see the correct value should be boundary. If we select boundary then the value will be updated.
However we suggest that rather than update the created XML you go back to the original survey in CDS and correct it there. This way any changes will not be lost if you need to recreate the ePlan LandXML. Once you are satisfied the XML conforms to the 1.02 schema we are in a position to validate it against what ePlan NSW (or your state) requires.
The ePlan NSW at present has a further 38 checks it performs.
To validate your LandXML first enter into your web browser:   https://six.nsw.gov.au/wps/portal/landxml 
The following web site is displayed:
First click on the browse button and select the LandXML file that has just been created. Now click on the "Upload and Validate" button. The LandXML is uploaded to the Six website and the extra validation rules are performed on the XML file. The rules are listed and whether the XML passes or fails each validation. You can see that an error is flagged on Rule 22 (Scims Check). In this case the sketch plan is lodged separately with the Survey Control Branch prior to the plan being lodged and has nothing to do with the LXML. The validation service is just reporting that there is no sketch lodged. They are supposed to lodge the sketch within a certain time.
Apart from the sketch plan everything else passes the validation so you are in a position to lodge your plan.
Here is a list of the extra vaildation rules for your reference:
Rule No
Rule Description in UI
Full Description
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
Plan purpose
Checks that the Purpose of the survey is recorded in the file
Plan give effect to purpose
Plan gives affect to the purpose of survey
lot numbering
New lots have a numeric identifier
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.
Parcel attributes
Parcels must have a valid Parcel Format, Class and Use
Valid parish
Validity of parish
ᄋ         Name
ᄋ          And must be in correct County
Valid County
Validity of county
Valid LGA
Validity of LGA
Valid Locality
Existence of locality name, if locality element is used
Valid Areas
Validate areas for proposed lots (calculated vs stated)
Multipart lot areas
Validate Part lot areas and total areas, including only parcel with class of モlotヤ can have parts
New lot area shown
All proposed lots must have an area
Parcel overlaps
Basic topology of parcels that have a coordinate geometry.
Lines must not cross lines in own parcel or adjoining parcels.
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
Parcel topology
Parcel geometry must have a sequence of lines where the end of one line is the start of the next
Check misclose in parcels in within prescribe tolerance.
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)
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)
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
RM/PM dimensions
Monument point must be connected to by a ReducedObservation
SCIMS date
SCIMS date must be within 6 months of date of survey
SCIMS sketch
PM Sketch has been lodged for placed control marks
Offset boundary mark
Boundary marks must be placed on boundary corner. Must not be offset.
unmarked boundary
RMs must be placed for unmarked boundary corners
RMs within 30m
RMs must be within 30m of the point being referenced
SCIMS details
Control mark attributes (Coordinates, class, order) must match SCIMS at date of survey
close points
Checks the file for the existence of points that are within 5mm of each other. Probably an error
Datum terminals
Datum terminals must be labelled "A" and "B"
Datum dimensions
Checks datum line bearing and distance against those calculated from the coordinates of the terminal points
Verifying radiation
Checks for a verifying connection to a third PM from one of the datum terminals
RMs for urban plan no road frontage
Check for the required No of RMs for urban plan with no road frontage
Found RM origin
Checks for the origin of all found RMs
RM connect to  one boundary point
Checks that each RM connect to only one boundary point
PMs new road
Checks for connection to the required No of PM's for new roads
RMs road frontage terminals
Checks for the connection to RMs at the terminal points of the survey where new parcels abut a road.
RMs for total road frontage
Checks for connection to the required No of RM's for the total road frontage of new parcels
PM to PM dimensions
Checks the dimensions between PM's compared to those calculated from the coordinates of the PM's
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.
PMs close
Checks that measurements between all PM's found or placed, and connections to the land surveyed, are  proved by closed survey
Marks exist
Plans of survey must have survey marks in the file. Compiled plans must not have survey marks in the file
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
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