Important Stuff
- Put gaps in mark names ie IT I DP 1234 not ITI DP1234 - a space between the mark type (IT) and the number (I) one between the mark and the plan type (DP) and one between the plan type and its number(1234) - new marks like PEG Ia or IT II
- In some cases you cannot fit the entire mark name in the code field, remember to correct these marks later (in SDRTransfer) before you create the file that is loaded into Landonline. Better still configure the marks names to set to the descrition field - this can be done under the data entry menu.
- Use the point numbers imported from SDRTransfer, do not assign new numbers to marks already loaded.
- Include all boundary observations.
- You do not need to enter observation for new boundaries or new easement lines if you don't want to (I don't), these will come from the parcel definition.
- Setup your Printer to print to a file rather than to the printer.
Data Entry:
To get the most out of SDRTransfer you should use the data entry mode within SDRMap. For those who don't currently use it the data entry mode allows you to enter all your observations in any order then perform closes in any order you wish. In my opinion this module is what makes SDR great, it is well worth having a play with.
When you enter the traverse data make sure you use the point numbers as imported, in the example below you can see I have entered 2 observations to marks from Landonline (pts 1025 & 1036) which are the front pegs, and one observation to a new tube (pt 1). One of the biggest traps for new users is double ups with 2 points for the same mark - be very careful to avoid this.
Landonline requires that all the existing boundary observations as well as the new boundary details are loaded. This simple with SDRTransfer as all you need to do is include the existing bdys in the traverse sheet, the new lines are passed to SDRTransfer later when we define the parcels.
Note IT IS VERY IMPORTANT that boundary observations link all points on the boundary, ie if there is an easement you must enter all observations in order, in the example below observations must be entered from 1-2-3-4 (the white parcel in the south is an easement). If you went 1-3-4 then added 2 separately there will be problems later when we define the parcels. This means you must be a lot more careful when working in SDRMap, you are creating a data set that can't be touched up in Cad to make look nice - you cannot have overlapping lines, parcels that don't close and points on the boundary that are not included.
Note that there is a trick for this once you get a good understanding of how things work. I would always have the new boundary intersections in the traverse sheet however I often have the easement intersetions only in the graphics display. When SDRTransfer reads the file from SDR it can't match the data in the traverse sheet with the lines in the graphics window as the trav sheet ignores the easement pointie the trav line goes from 1 - 3 where the graphics goes 1 - 2 - 3. SDRTransfer will liad the line from 1 - 3 as a traverse line and the lines from 1 -2 - 3 as boundary lines. the later will have the CALCED values only. You need to edit the bearings of these lines and ensure the distance adds up to the total then delete the total traverse line. To delete the line go TOOLS > EDIT MODE form the obs page then TOOLS > DELETE LINE.
In the image below I have finished entering all the data and am now creating the traverse sheet, for those who haven't used this function before - you select a start and end point then SDRMap will show all the possible directions you can go, just click on the line you want and you are away.
Once the close is complete you see the misclose, before going ok press the "Traverse" button to send the loop to the traverse sheet.
Make sure you put all the observations into the traverse sheet ie all the existing boundary lines, this makes sure that SDRTransfer gets the correct data and you can see the closes around the boundary. This data is normal entered into SDR anyway to see how the parcel closes. As the traverse sheet is just a reference document in an e-survey you can load it up with as much data as you want.
Note:
If you haven't included some existing boundary observations in the traverse sheet then they are automatically updated with the observation details from Landonline as long as the observation was captured. This is not the the preferred method as you don't have the same control over the data that is loaded into Landonline. It is much easier to sort out problems in SDR than in Landonline.
make sure you don't round the bearings
to put the pegging ties into the traverse sheet go to Graphical calcs > Inverses > Radial report, select the ties then click the "report" button, tick the "traverse" box and select "code" not "desc" from the name combo then go OK.
You will now have a traverse sheet that looks something like this. You may have typed it all in if you haven't used the data entry module.
We need to get the traverse sheet and later the parcel information into a text file for SDRTransfer to be able to read. To do this we setup the printer to print to a file;
- in SDRMap select Jobs>Printer
- Make sure Print to Printer is Ticked
- now select Jobs>Printer>Setup Printer
- Set the port to File
- Set the filename to something like output.txt
we will end up putting the traverse sheet and parcel definitions into this file for SDRTransfer to read.
Make sure your output.txt file is empty, this is easily done by exiting SDRMap, going to your job directory and deleting the file. Another option is to change the output file name when your job is ready to export. We need to do this to ensure no incorrect data is passed to SDRTransfer.
In the traverse sheet press F9 to print then F5 to list the traverse sheet, when asked to list as entered press No (this option will output all distances in metres, if you say yes and you have entered some data in links then they are listed in links)- this will print it to our text file.
Now lets deal with the parcels