Instrument Manual. Interface to Leica Geosystems Captivate

Transcription

1 Instrument Manual Interface to Leica Geosystems Captivate

2 Contents Introduction... 3 Chapter Install LSS, 3D Vision, Tutorials and Testdata Survey instrument and Machine Control support files Example Codelists LSS String coding and Reserved codes Configuring Captivate for LSS coding... 6 Chapter Survey practical exercise LSS String coding and Reserved codes Working with the plan and code table Instrument Data Capture on a Leica Captivate Creating a new Captivate job Setup procedure Detailing procedure Images Chapter Configure Hardware & System Configure H&S - Logger - Leica Job (DBX) reader Configure H&S - New Survey Parameters Configure H&S File Editor Creating a New Survey in LSS Data processing Input Download / Convert Data processing Input Load Introduction to load files GPS Survey Instrument Issues Page 1 of 53

3 Chapter Exporting data to Leica instruments Export Leica DBX Database Opening the DBX files in Viva Exporting Leica GSI File Exporting an LSS Code List Importing the XML Code list to Captivate Advanced code list use - example code list LSS1200Adv Conclusion Page 2 of 53

4 Introduction As modern surveying equipment and methods have evolved, LSS has also developed much more functionality in order to make the most of the techniques available. This is especially true when it comes to data acquisition, field coding and transfer from survey instruments. McCarthy Taylor Systems Ltd has strived to ensure that LSS surveyors are able to make the most of the options available. This manual has been prepared to help with the configuration of both the survey instrument hardware and LSS software. Page 3 of 53

5 Chapter Install LSS, 3D Vision, Tutorials and Testdata Select Install LSS & Test Data For a new install use Full LSS Install and Dongle Drivers Also choose Enhanced Testdata which includes examples of Point Cloud data and the files we use in our specialist training courses. Page 4 of 53

6 1.2 Survey instrument and Machine Control support files Select "Survey & Machine Control" Access the files/documents for your instrument type Page 5 of 53

7 1.3 Example Codelists Three Example Codelists are supplied on the LSS media. They are pre-formatted for immediate upload to the Leica instrument (how to transfer a code list to the instrument via a data card or USB stick is shown later in this document): LSSv10Captivate - the standard LSS Prototype for Captivate instruments LSSV980Road includes LSS road markings LSS1200Adv - an advanced version, which uses an alternative method to group features together in the code list. This is only intended as an additional facility and may be used to demonstrate ideas which can be added to the standard codelist in use. 1.4 LSS String coding and Reserved codes The PDF file 'LSS_String_and_Reserved_codes.pdf' contains very useful information on the principles of Survey and Feature Coding in LSS as well as a complete list of diagrams and descriptions of all the LSS Reserved codes. All the LSS media files used here are also available for downloading and installing from the LSS website at dtmsoftware.com. 1.5 Configuring Captivate for LSS coding Code List An example code list "LSSv10Captivate" has been built from the LSS prototype legend (supplied with Testdata) and is available on the LSS media within the folder Support_files\Leica\JobDBX\Code. The LSS point features translate as point codes and the LSS link features as point codes with lines (the use of line codes appears unnecessary) Page 6 of 53

8 The following steps explain the method of transferring this code list to Captivate; Copy the required Code list files.xcf,.x06 and.x23, from the LSS media Code folder to the Code folder on the card or USB memory stick. Transfer the Compact Flash card / USB memory stick from your computer to Captivate. From the Main Menu - 'Settings then Tools then Transfer user objects Set Object to transfer as Codelist - Set Codelist to the relevant code list. Set From as either SD Card or USB depending on the data transfer media. Set To as Internal memory then OK [F1]. Page 7 of 53

9 Customisation (identical for EDM and GPS) - Set the ID Templates... From the Main menu - Settings 'Customisation then ID Templates Page 8 of 53

10 TPS points as <Manually enter> and TPS auto points as TPS_Auto_0001 Note: These screen captures use TPS only as the example but the screen itself may refer to TPS, GPS or both depending on the instrument. These settings are to be set the same for each type of instrument and will need to be duplicated where both are present. The settings for ID Templates require the use of the second dialog ID Template Library - where relevant click Edit after selecting your choice Note: The Edit ID Template dialog is not always available because some options are system ID templates and cannot be edited e.g. <Manually enter> and Use code & string Page 9 of 53

11 Coding & Linework - Returning to Customisation select Coding' 'Code & attributes' - Tick Allow new codes to be created and 'Show code description alongside code'. Set Suggested attribute values to Last Used which will recall the last attribute value for each individual feature. Set Prompt for Mandatory Attributes to When code is changed where attribute input will not be requested unless the feature code is changed. Note: a feature change can be triggered by toggling the feature list. Linework Note: The above screenshot was made on a previous firmware version that does not show the Linework tab. If your version shows this tab please set the following; Begin Line = BEG Close Line = CLO Page 10 of 53

12 Quick coding Note: This can be enabled by setting the Coding functionality (shown above) to 'Only code pts - No linework'. Then on the Quick coding tab set to 'On' and the number of Digits to use and how they are stored. User defined pages - Returning to Customisation select User defined pages Note: This configures the displayed items seen during detailing. We suggest editing an unused Page just to help us see how the feature coding works. Select 'Page 3' to use as the Code page, then Click Edit' Page 11 of 53

13 Set each line for the display as indicated here. Note: This screen example is for a TPS. The equivalent setting for Target height on a GPS is Antenna height Continue using the vertical scroll bar. Once complete, click Ok or F1 Page 12 of 53

14 Hot keys & favourites - Returning to Customisation select Hot keys & favourites Tab TPS hot keys, then Set F7 to Data - Select free code from list Page 13 of 53

15 Chapter Survey practical exercise The following plan and accompanying coding document have been designed so that a practical exercise can be carried in which to practice some of the latest techniques that have been developed in conjunction with Leica DBX instruments. These include general feature coding, the use of string numbers and the. and.. special codes, feature attributes on the instrument and reserved codes used to generate additional observations in LSS. It is quite a condensed survey so be prepared to take a bit of time to acclimatize yourself with how the feature and other coding is applied on the instrument LSS String coding and Reserved codes The PDF file 'LSS_String_and_Reserved_codes.pdf' contains very useful information on the principles of Survey and Feature Coding in LSS as well as a complete list of diagrams and descriptions of all the LSS Reserved codes. This can be found on the LSS Installation media under support_files\lss_survey_codes or on the LSS Website Working with the plan and code table In the plan below the numbers refer to the point identifiers, marked on mini sports cones, which are to be the point ids on the instrument. The black numbered observations are the ones to be surveyed; whilst the blue numbered observations are those representing extra points created by using the LSS reserved codes, described fully in the rough guide. The table on the page opposite, to be taken outside along with the plan, is an itinerary of the codes to use on the instrument in order to make use of the coding options during Input Load in LSS. Page 14 of 53

16 Page 15 of 53

17 PtID/ Setup Setup Free code Attributes Code Attributes Description / Reason At A (Known Az./Resection etc) B CTLObsID Control obs to B C CTLObsID Control obs to C etc 1 K 1 Start new K string 2 -SO 0.5/0/F K 1 Add string offset 0.5m Horz. / 0.0m Vert / Fence. 3 Freecode CS1 K 1 Add CS1 link to this obs 4 Freecode CS1 K 2 Start new K and add CS1 (join to 3) 5 K 2 6 Freecode PGY K 2 Add gulley to this obs 7 K 2 8 Freecode..DK K 3 Start new K and start DK string from prev pt 9 K 3 10 K 3 11 K 3 12 Notes STORM PIC Add Notes to inspection cover 13 IC 1 Start IC string 14 IC REC IC 1 Create rectangle from 3 IC pts 16 PD 5 / 6 / 8m / Willow Tree c/w spread / trunk / ht / species. 17 B 1 Start B string 18 B NLP B 1 Create perp. to line 20 B 1 21 B RIN -0.3/DR B 1 Create rect. offset left of line. Page 16 of 53

18 NB Use ATTRIB button 23 Freecode CS1 B 1 Add CS1 (join to 4) 24 B 1 25 B INT B 1 Create intersection from 4 pts m TH SS Change target ht. for height diff m TH SS 29 -RS 3 SS Create steps from 3 pts. NB Return to original target ht. 30 None Spot level no feature 31 None B CTLObsID Control obs to B C CTLObsID Control obs to C etc Page 17 of 53

19 2.2 Instrument Data Capture on a Leica Captivate Creating a new Captivate job Select option Tap here to create new job from the Home screen Type in the Name and other settings for General. Also set the Codelist, Coord System and the Averaging settings. Then Store. Note: If only one Codelist is in use on the Instrument then it will be the default. Page 18 of 53

20 2.2.2 Setup procedure The following example assumes an arbitrary co-ordinate system. If existing control coordinates are needed the stations can be uploaded from LSS to a Fixpoint Job (see exporting data to Leica DBX) and then copied to the current job before doing the first set-up From the Go to work menu select 1 Setup On the Total Station Setup page select the Setup method as Set orientation. Then click OK. Page 19 of 53

21 To set the set-on station name and details, click Point ID to create a new point. Then click 'New' On the New Point - Coordinates screen, specify a Point ID (i.e. Station name) and the relevant arbitrary coordinates. Page 20 of 53

22 Specify a Backsight ID, Target Height and Direction, sight the target, then press Distance then Set You are now ready to start detailing Detailing procedure LSS uses Point, Point with Line and Free coding. The Codes are accessed via the display entry Code and the Free Codes via the [F7] key. In each case the relevant Codelist is displayed as exported from LSS (see the LSS media support_files folder). From the Home' menu select Measure In the Code option click the list icon Page 21 of 53

23 In the Code option click the list icon - Using the arrow keys highlight the Code entry and type the required code or Enter The codelist will appear defaulting to the closest entry to the typed characters. The arrow keys can further be used to manually select the required code. OK will return to the display mask with the highlighted feature code. Attributes - The display mask will show the required attributes (either integer, real, text or choice list) for the selected feature code. Note: The LSS default for mandatory attributes is Only on code change. The default values as set in the codelist. Note: The current feature remains active on repeated measurements. Note: It is necessary to use the Attributes button on the code list to change an attribute that is not set to Mandatory as per reserved codes -REC and RIN. Page 22 of 53

24 Note: The Last button will show the last used codes in order Images LSS fully supports the imaging/photos on the DBX based instrument series. When recording an image it must be attached to a PointID or a set-up When a DBX job is selected the images are found and copied to the Images sub-folder of the LSS model automatically. Page 23 of 53

25 The DBX job files and the images are also archived automatically when the Archive/DBX job database check box is selected (this is on by default). Note: Under certain conditions it is possible for the automatic Archive and copying of the image files to not be available. When this is the case the Archive/DBX job database check box will be greyed out as in the dialog above and the warning dialog no files are available for archive will appear. This will normally happen when the DBX folder itself is browsed but the job files are actually contained under a sub-folder of this e.g. as per the standard Viva (or later) Job files. All the sub-folders of the browsed DBX folder are searched and any of the DBX jobs can be processed. However, the archiving option and copying of the images is not available unless the actual job folder is browsed directly. If the images have not been copied use Explorer to copy them separately to the Images sub-folder of the LSS model. Page 24 of 53

26 Technical Notes Setup information when using the Job reader to import survey data it can only access the setup information when added within the same survey and when in the Survey application i.e. if a setup is done in the Stakeout application and the user switches to the Survey application the set-up must be repeated (all previous inputs will be remembered) otherwise LSS will not see the set-up. Station coordinates - these become the 2, station records in the load file. If these appear in the same load file as radial data then a subsequent occurrence of the same station name will update the station coordinates. The suggested setting so that the latest coordinate value will be the one to be used by LSS is to set the Filter to Highest Class using the following; Jobs & Data View & Edit Data Fn (function button) Filter: Points tab Sort by: Backward time Filter by: Highest class Using these settings allows the load file to always be given the current accepted value and the last occurrence in the load file is the one that LSS will use. (see Input Load below) Simulator default data paths - Captivate - C:\Users\Public\Documents\Leica Captivate\CS Page 25 of 53

27 Smart coding To turn on Smart coding at this stage click the CONF and set the values as listed; Use SCodes Yes Measure point - No (this can be set to Yes during the survey to automate the data collection by selecting Shift CONF) String Attrib - 1 (this is linked to the Coding and Linework config set values and should at this stage already be 1). Note: 1 must be used. Method - Not Used (Zig-Zag and Same direction can be used if required) Page 26 of 53

28 Note: The following details follows after the Setup during the detailing procedure When you arrive in Survey mode the SCode tab should now be available as shown. Highlight the first Code box by selecting it and press the Codes button [F3] and select your first code from the codelist. Note: String numbers need to be used and can be added to the entry point directly below each feature. Page 27 of 53

29 Repeat for each box until a complete set of codes are listed. Additional code blocks can be created by highlighting the existing code block name e.g. 1, press Enter and choose a New [F2] name and Store. Then repeat to add codes for the new block. In this way additional code blocks can be created until all required code block templates have been defined. The + or buttons can be used to increase or decrease the string numbers. Page 28 of 53

30 Chapter Configure Hardware & System This menu controls the default LSS settings held within the LSS registry i.e. 'once set always remembered'. If any values are changed while in Configure Hardware & System on return to the main dialog a 'Finish' button will have replaced 'Cancel' If Finish is clicked followed by the Save option on the following confirmation dialog the changed settings are written to the registry. Note: This process must be repeated for all PCs that are to use the Job reader. Page 29 of 53

31 3.1.1 Configure H&S - Logger - Leica Job (DBX) reader Select Configure Hardware & System, followed by Logger / Change (if this is the first time a logger is to be configured on this PC then the option will be Logger / New ). Select the logger format as Leica and give a description e.g. DBX. Choose 'Job (DBX) reader and make sure the tick box "No data transfer/download by default" is off. Click OK Page 30 of 53

32 3.1.2 Configure H&S - New Survey Parameters These settings/parameters are those applied at each survey initialisation i.e. 'File New'. Set these survey parameters to match your 'average' survey to minimise the number of times you will need to change them. Copy Prototype from - an LSS template survey from which the feature legend and display settings are copied. Default Scale factor - this value does not affect any distance calculations directly but is used to provide a default scale factor to newly loaded or edited stations to relate radial survey observations to their grid coordinates. The value is normally set to 1.0 Control tolerances set the Warnings and Errors used during Input / Load and other survey processing/reporting options and refers to the survey data processing of control observations. When a control observation exceeds the warning or error values compared to the held station coordinates it is reported. During Input / Load when an error is issued the option cannot be completed until the misclosure is resolved. Note: the LSS Prototype is set as the default during the LSS install and is found in the Prototype folder (as shown). To change this to your own edited prototype legend just Browse to the LSS file that contains it and 'Finish' and 'Save'. Page 31 of 53

33 3.1.3 Configure H&S File Editor This option sets the File Editor application that opens a browsed file when the Edit button is clicked. HiEditor is the file editor installed by LSS and is automatically set as the default, unless a setting already exists in the registry. Therefore, for existing users of LSS it is worth checking this setting. HiEditor should be selected as shown unless you have a preferred editor which can be browsed under 'Other'. 3.2 Creating a New Survey in LSS A survey must be open to process data into LSS and in this case we will use File New. Select File New DTM from the main menu. Click Browse against New survey Create a new folder as required within the surveys folder e.g. C:\ Surveys\Workshop; Select the folder. In the 'File name' input box enter the survey name, e.g. Workshop Survey Page 32 of 53

34 Click Save. (refer back to first diagram) This will return to the File New DTM dialog with the path and name of the intended LSS survey. Enter Survey title (if left blank LSS will use the survey name). The Prototype will be as per New Survey Parameters (see above). If we had stations already at the site we could bring them in here. Click OK Note: If required tick the Configure Survey Parameters box. See setting 'New Survey Parameters' above to minimise the need for this. Note: It is worth saving the survey immediately on completion of this option. This will allow File / Restore to be used to return to the survey "as initialised" and can be useful while addressing Input Load issues when processing the survey. Page 33 of 53

35 3.3 Data processing Input Download / Convert The first task is to transfer the survey Job DBX folder from the logger to the PC using the Utilities Transfer Job option (see elsewhere). Select Input Download / Convert Note: If Leica Job (DBX) reader is not available then click New/Change and follow the dialog boxes as shown above for Configure H&S Logger. Note: If a Leica GSI file already exists (e.g. '.SVY' from using the Legacy option),then Tick the No DBX read (convert GSI data file) box to skip to the conversion dialog. Click Next Page 34 of 53

36 Select the DBX folder by either; Clicking Browse (use when the DBX folder is on a removable drive). Click 'OK' Click Explorer (use if the DBX folder is already on the PC). Use 'drag and drop' on the DBX folder. Click OK for the job list that exists in the selected folder. This dialog displays the Job list of the selected folder. Select the required Job. Click OK. Page 35 of 53

37 Provide the LSS Load file Note: If the LSS load file input box is empty and 'Next' is clicked then LSS will automatically show the name of the next available load file number for the current survey. However, there is no need to hit Next The settings for 'Included data' and 'GPS QA warning values' are remembered. The Included data options relate to the requirement for Control stations in the Load file. The GPS ref station might be selected e.g. if the Job references an on-site base station. Archive Job DBX will copy the database files to a sub-folder of the current survey. Click 'OK' to process the Job, create the Load file, and automatically invoke Input Load. Note: The job database files (DBX) are not archived if browsed from within the current survey subfolder tree (the option will be greyed). Note: If the survey does not exist then File New will occur prior to Input Load. Note: A report is written at the bottom of the Load file showing the QA information, as well as the number of converted stations, set-ups, observations, text etc. Page 36 of 53

38 3.4 Data processing Input Load Introduction to load files The LSS Load Input file is the format by which all external data is processed in LSS Loading data into a survey model The Input Load command will invoke the following window, highlighting the correct load file i.e..001 if Save and Load has been chosen. A Load Report file will be generated and a number of options exist to aid the user to process their data and coding to their requirements (see Help for details). Click Next Note: Click Edit button alongside the Load file number to open the Load file in the File editor (see above) in order to address any issues raised during Input Load. Page 37 of 53

39 Click 'Next' to start the Input Load survey process Note: the next few pages will first help understand what to do if any QA issues are raised during this process. The Load process itself is continued after this. An explanation of the LSS Load file format A load file can contain either radial observations, coordinate observations or both, which can be opened in the default editor. Radial and coordinate record types 0 = Comment line containing information that will not be processed by LSS, such as the surveyors name, data and time of the survey. 1 = Parameters record containing e.g. survey units and angular settings. 2 = Station coordinate record. 20 = Station coordinate control observation used as a check and commonly encountered with GPS survey equipment to verify a survey station position. 6 = An item of general annotation (normally text entered on an instrument as a comment or note). Such annotation will be shown in the LSS survey centred on the previously surveyed point. 9 = End of file marker. It is not necessary to have one of these at the end of the file. Radial only record types 3 = An instrument setup record with set-on station, followed by backsight station, backsight angle, instrument height, vertical angle collimation and station scale factor. Some of the fields may be blank as in this load file as LSS will be getting information from lines which follow. 4 = A control observation where the final field is the station name. If there is a 4 record following a setup record, this will provide any missing information in the setup record. This is identical to a 5, record with a -ST code. Page 38 of 53

40 5 = A detail record which contains an observation to a surveyed point with the feature code appearing in the last field. Multiple features may be specified and separated by either a comma or a forward slash. This record type may also be a control observation, where -ST is the code, with the station name either following this or being taken from the observation number field. Coordinate only record types (not shown in this example) 21 = A coordinate record. Instead of collecting radial data it is possible to collect and convert coordinates, e.g. for GPS survey data. These survey data can also use Reserved codes. As the load file is processed so a report is produced showing all relevant information e.g. comments, setups and control observations. Any warnings or errors found in the data set will cause the processing to pause. An error will not allow Input Load to complete. The end of the Input Load Report should appear, with a note *** Warning(s) issued *** recognising that some warnings had been issued. Any misclosures that exceed the warning parameter are labelled Large differences, and Load will pause. Likewise for any that exceed the error parameter except that here Load will not complete. If we scroll back up the following report file, we might find Warning : Feature does not exist. and Warning : Large Difference. Warnings have been generated during the Input Load process. Otherwise, click Continue to update DTM and OK to close window. If a loaded feature is not found in the Legend, then the Warning : Feature does not exist. is created. We will also be prompted to save new feature selections to CNV file. For each control observation, the combined 3D measured slope distance is compared with any stored values and tested against the Control Tolerance warning and error values set in Survey Parameters. Those control observations with Warning : Large Difference. next to them, are where the warning tolerance (0.01m) was exceeded (but not the error tolerance). Note: The load file header includes the following information as comments; Coordinate system used (including the geoid and CSCS files used). Transformation name and type Projection Scale factor Note: The processing will also include comments on; Which detail observations have zero values and have been removed Whether a station observation is being used as 1d, 2d or 3d. 1d stations observations are commented out and not used, unless it is the only one in the set-up, in which case the load file set-up record uses its values as the backsight name and horizontal angle. Page 39 of 53

41 2d station observations have their target heights removed so that height differences are not attempted to be reported Whether a station coordinate is 1d, 2d or 3d. If a station's xyz coordinates are all zero then it is ignored. If it is 1d it is reported but not used If it is 2d it is reported and used. Note: The set-ups in the load file are annotated with the Set-up type Note: if an observed station does not exist in the survey, then the first observation is used to compute its coordinates they are not meaned here. Subsequent station shots become check observations. Note: if any errors are encountered the load will not be permitted. It will be necessary to review these errors and maybe re-specify the error tolerance to allow the load. Often errors occur simply because the stations have been incorrectly labelled during the set-ups, or there is one poor observation. To correct these click Back and then Edit to open the load file. Note: Warnings and Errors will both refer to a line number. When in Edit mode Ctrl+G will jump directly to the value input. Click 'Continue at each pause for a warning after checking the reason. The final 'Continue' will be available provided no Errors exist. This will 'update the DTM'. Click 'OK' to complete the load and display the data. Page 40 of 53

42 On the screen, the loaded survey should look like the screenshot: Note: Attachments in the form of images have come through from the survey data. 3.5 GPS Survey Instrument Issues GPS data can be read directly from the DBX Job when CSC and/or GEM projection files are using a suitable Ordnance Survey grid e.g. OSTN02 or OSTN15, or similar for Northern Ireland and the Republic of Ireland. Note: In the Load file LSS will report the CSCS or GEM files in use on the job list. Scale factor - combining GPS (coordinates) and TPS (EDM radials) If the GPS Job contains a scale factor and the survey to be processed also contains EDM data then use one of the following methods to process them both in the same LSS model. If the EDM Job coordinate system contains a scale factor then LSS is able to automatically apply this to the radial data provided the Geometric scale factor set on the instrument. Set Compute scale using to Stn & coord system If the EDM Job does not use a scale factor then manually apply the scale factor to all the stations in the LSS model. If the scale factor varies across the site then each station will have an individual scale factor. The grid scale factor in an LSS model can be changed to match another grid using File\Transform\Scale. If this is to be applied to an LSS survey with radials then first use File Transform / Obs to XYZ which will convert all radial observations to XYZ. Set the GPS coordinate system to a local grid using e.g. a One Step Transformation on the instrument Note: The above options are to avoid a mismatch between the GPS and EDM results. This also applies to avoiding the scale being applied twice by the instrument and by LSS Page 41 of 53

43 Chapter Exporting data to Leica instruments LSS exports data to most types of survey instruments using the same logger configuration as Input / Download / Convert. From the main menu the export commands are listed under Export; For survey instruments the key exports are: Upload data to survey instruments... Upload code list to survey instruments... Leica DBX Database XYZ (.CSV) LandXML Choose which is the most appropriate for your particular logger. The generated files can be copied via USB ready for transferring to the instrument Export Leica DBX Database The option Export / Leica DBX database exports the LSS model as the three types of DBX job file which can then be added directly to DBX based instruments. Select Export/Leica DBX database. Specify a folder name for the exported files using Browse or Explorer. If the folder name does not exist LSS will create it. Specify a Job name and Description which will become the Job name on the instrument. These will default to the Survey Name and its Title. Page 42 of 53

44 Select the type of data required Note: If DTM or Road are chosen then the name is extended to Job name DTM or Job name Road automatically (as long as the Job name is still the same as the LSS model name). In this way all the required DBX sets can be put into the same folder without the user needing to set different names. The user can choose from; DTM Data (Standard survey) the observations are exported as points and lines with the same point number as LSS and the linework has the same colours as the LSS legend the stations are exported as Control points Road an SPF is exported (either a design geometry SPF or a normal SPF) Multiple links can be selected - the longest string is accepted as the Centre line LSS will export the entire survey into the necessary DBX files which are copied onto the instrument card job folder via the card reader. With DTM, the DBX files are placed in another subfolder. If Road (alignment SPF) is selected an SPF will be needed. Use Configure / SPF Create first if one does not already exist. Page 43 of 53

45 Note: An SPF can contain either; road design geometry imported via MX Genio or LandXML or normal SPF that can contains multiple reference lines. This can be created Configure / SPF Create; SPF name Offsets Section title this will be the name of the alignment in the DBX (if empty the SPF file name will be used) Line method Click Next Select Mode / Whole String and then pick the string required For each reference line select New reference line and type a unique name for the section title When complete choose End and Save SPF and OK Page 44 of 53

46 4.1.2 Opening the DBX files in Viva Note: The following examples are using the Viva PC simulator Once the required files have been created the folder can be copied as a sub-folder to the DBX folder on the CF card. At the main menu click on the Map button Then Jobs Page 45 of 53

47 Select the exported Standard Survey as the Data job Then select the Road job and the DTM job as relevant Click OK and then the Zoom All button to see the data The display can be configured to show what is required The survey data The DTM The Alignments You are now ready to use the relevant application Page 46 of 53

48 4.1.3 Exporting Leica GSI File Note: The logger parameters can be altered by clicking Change Specify a name for the exported file and Click 'Next'. Page 47 of 53

49 This dialog allows the selection of observation and station data. The defaults assume that the Observations will be exported using the Selection filter. Click Next. Note: The observations can have the code added to the point number, which can be related to the SPF chainage. If chosen, the Selection filter dialog will offer the opportunity of multiple observation selection criteria. Hit Apply to make selections on the screen there can be many. As soon as there are observations selected then the 'Cancel' button is replaced by Finish. Click Finish once all required data is highlighted. Note: The data selected by the Selection filter is grouped in the export set first as complete strings and then as individual points related to their loaded order. To export the observations in the order they were located use Individual observations from the previous dialog. Page 48 of 53

50 There is the possibility of repeating several selection criteria to the same data set. If required, click Yes to Add more data and repeat the process. We might choose this option to export Survey stations or specific observations. 4.2 Exporting an LSS Code List The LSS option Export / Upload code list to survey instruments will produce a Leica code list. However, there is a pre-built code list "LSSv10Captivate" that is available in the Support_Files\Leica\JobDBX\Code folder of the LSS media (flash drive supplied with LSS). Select Export / Upload Code list to survey instrument / Leica HeXML (Captivate). Click 'OK' Page 49 of 53

51 Input the Filename and click 'OK'. Select the required point features. Use trailing digits as dimension attributes allows point features with dimension to be grouped under a single item e.g. PT1, PT2,,PT20 etc will be exported as a single feature PT with a Mandatory integer attribute. Select the required link features. The 'Tree feature' option is similar to the 'trailing digits' of the other Point features option but uses a combination of both Spread and Trunk features to be combined into a single code. Note: The Tree feature has two further attributes for including height and species information as well as the spread and trunk. Leave the LSS reserved codes + extras box ticked to create all the Reserved codes as Free codes. Note: This option will also export the String codes and Code words code groups that contain a mixture of free and point codes for extra functionality. The primary String codes and Code words are; CTLObsID for coding a control observation for the instrument and LSS simultaneously. Where the station name is added as the Point ID. CTLObsRO for coding a control observation for LSS only. Where the station name is added as an attribute. Notes: for adding general text at an observation, Freecode for adding multiple codes to one shot only, '..' - Start a new string from the previous point, 'PD' - The Tree feature requires two Point features with digit suffixes for dimensions, the first feature represents the spread and the second the trunk e.g. PD1 and PS1. Click OK. Page 50 of 53

52 4.3 Importing the XML Code list to Captivate Create a new job and select the codelist Page 51 of 53

53 4.4 Advanced code list use - example code list LSS1200Adv To shorten the number of items on the main code list but maintain the same number of codes in the code list overall; If a feature code has the two extra characters >> added LSS will ignore it on import. This code will have 2 attributes. The first attribute can then be made to be the feature code that LSS will use (in the example code list shown this attribute has been used as a choice list of all the fences). As can be seen on the first diagram the second attribute will be the string number. In order for the stringing to be seen on the Map you will need to change the coding and linework String Attribute setting in the config set to 2 (as in the example code list it is better to change all the codes in this way so that they will all appear on the Map). Where a code does not have a main code with >> it is necessary to introduce a blank attribute so that the string number is still attribute 2. Page 52 of 53

54 Conclusion Using this manual, we hope that you will be in a position to start making the most of the survey instrument. We strive to cover and support as much of the capabilities as possible but there are always new methods and developments, so do keep in contact by visiting the LSS Help and other on-line resources or call our support line. McCarthy Taylor Systems Ltd Aerial View Acorn House Shab Hill Birdlip Gloucestershire GL4 8JX Tel support@dtmsoftware.com June 2018 Page 53 of 53