Instrument Interface to. Workshop Manual

Transcription

1 Instrument Interface to Workshop Manual

2 Introduction 1. Session Installing LSS, Tutorials and Testdata 1.2 Installing Other Files used by LSS 1.3 Configuring Leica System Configuring Leica Viva System 1.5 Configuring Leica Captivate System 1.6 Summary of Session 2. Session Survey Practical Exercise 2.2 Instrument Data Capture on a Leica Instrument Data Capture on a Leica Viva 2.4 Instrument Data Capture on a Leica Captivate 2.4 Summary of this session 3 Session Configuring the Job reader in LSS 3.2 Configuring the New Survey Parameters in LSS 3.3 Configuring the File Editor in LSS 3.4 Creating a New Survey in LSS 3.5 Processing the Workshop Survey in LSS 3.6 Leica 1200 format file 3.7 GPS Survey Instrument Issues 3.8 Summary of this Session 4 Session Exporting Data to Leica 4.2 Exporting an LSS Code List to Leica 4.3 Leica Geo Office Importing an LSS Codelist 4.4 An Advanced code list example 4.5 Summary of this Session Conclusion Version LSSv Page 2 of 70 Mar 2017

3 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 workshop manual has been prepared for trainees attending the LSS and Survey Instruments workshops to help with the configuration of both the survey instrument and computer laptop. It is normal (and recommended) that the trainees bring their own instruments and laptops to the workshop, so that they leave with a fully configured and working system. Hence we will start by ensuring that the latest version of LSS is installed on the trainees laptops, upload a standard LSS code list onto the instrument and make any required configuration changes to the survey instrument. We will look at feature coding for strings and points, plus the LSS Reserved codes and how these can be used to add extra observations effectively and efficiently into the LSS survey. There will be a practical exercise outside to help demonstrate these options, followed by the downloading (transferring) of the practical exercise survey data onto the laptops and the processing in LSS. We will finally look at the export commands in LSS to see how we can upload design data for setting out back onto the instrument. We will also look at how to update the LSS legend in a typical LSS prototype survey before creating the necessary code lists to upload back onto the survey instrument. The workshop is split into four teaching sessions as follows. Session 1 09:30-11:00 Break Session 2 11:15-13:00 Lunch Session 3 13:30-15:00 Break Session 4 15:15-16:30 Survey instrument support files are held in folders specific to each manufacturer on the LSS installation media. Version LSSv Page 3 of 70 Mar 2017

4 1. Session 1 Duration: 1 hour 30 minutes 1. Install LSS, 3D Vision, Tutorials and Test Data 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. 2. Survey instrument and Machine Control support files Select "Survey & Machine Control" Access the files/documents for your instrument type Version LSSv Page 4 of 70 Mar 2017

5 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 LSSv9_80 the standard LSS Prototype 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. Leica Geo-Office Tools is the software we use to add new feature codes into a codelist and transfer the updated codelist to the Leica DBX platform instruments. We will need to install Leica Geo Office Tools Program by saving the zip file, unzipping on the C: drive and running the Setup.exe file to install Leica Geo Office Tools on the PC. Alternatively we can open the LSS media with Windows Explorer, find the Leica_Geo_Office_Tools_en directory in "Support_files\Leica", and run the Setup.exe file. All the LSS media files used here are also available for downloading and installing from the LSS website at dtmsoftware.com. Version LSSv Page 5 of 70 Mar 2017

6 Rough Guides The following window is invoked when selecting the How to Guides from the Home screen: For example clicking on Feature coding for Land & Eng. Surveyors will open a very useful document Principles of Survey and Feature Coding as a pdf file. This describes in detail the aspects of coding and stringing on the instrument for optimum input into LSS and we will look at some of the details later on as part of the practical exercise. Version LSSv Page 6 of 70 Mar 2017

7 Version LSSv Page 7 of 70 Mar 2017

8 1.3 Configuring Leica System 1200 The two requirements for using LSS coding to the best advantage are a relevant code list and a subset of the config set both of which have identical usage for both TPS and GPS. Note: the instrument firmware is important for the support of some of the functions in this section. If you do not have the latest firmware, particularly if it is earlier than Version 5.62, not all the options will be available. Code List An example code list has been built from the LSS prototype legend (supplied with Testdata) on the LSS media (in Support_files\Leica\JobDBX\code_list ). The LSS point features translate as point codes and the LSS link features as point codes with lines (replacing the use of line codes for processing purposes which are deliberately avoided by the Job reader owing to a problem relating to the ordering of data when they are used). The following steps explain the method of transferring this code list to the System 1200; 1) Copy the required Code list files.xcf,.x06 and.x23, from the LSS media Code lists folder to the Code folder on the card. * Note : The 1200 Simulator card folders are in Configuration/Data Paths/PC card path 2) Transfer the Compact Flash card from your computer to the System 1200 sensor. * Note : The Compact Flash card must always be Stopped before removing it from the PC and the System 1200 must always be switched off before removing the Compact Flash. 3) Select option 6 Tools from the Main Menu. * Note : This option can be selected by pressing the number 6 key, or by navigating to 6 Tools... and pressing the Enter key, or by touching the Tools icon when using an active touch screen. 4) Select option 2 Transfer Objects from the Tools Menu. 5) and Codelists from the Transfer Objects Menu. 6) In the Transfer Codelists screen copy From CF Card and To System RAM, select the copied code list and CONT [F1]. Version LSSv Page 8 of 70 Mar 2017

9 7) Config Set Alterations This indicates the settings for a System 1200 instrument (especially within the Display mask and the Coding/Linework) that enable it to work well with LSS; Display Settings (Display masks) The LSS example display mask tab shows the Code and its description along with up to five associated attributes (as used by the example prototype tree feature PD). Use the scroll bar to reach the fifth attribute e.g. the tree species in the LSS example code list. To amend your display mask to match that shown above choose Management / Configuration Sets from the main menu. Highlight the configuration set to be updated then select New to create a copy of this config set (select [F3] Edit to change the existing one) typing in the new Name and Description etc. Click Store to create the copy. On the Wizard Mode screen select [F6] List / Display Settings and [F3] Edit. We suggest the following settings; Mask 1 Survey - leave as your preferred view of the measurements etc Mask 2 Offset - remove this by setting Use in Survey to NO (not needed for LSS). Mask 3 Code change to see the code list attributes as below by clicking DMASK Enter the Lines as shown below using the scroll bar to access the settings as shown in the second screen capture. Then select [F1] CONT twice to accept these changes. Version LSSv Page 9 of 70 Mar 2017

10 Coding & Linework Settings Note: These changes are necessary in order for the LSS coding to perform correctly. On the Wizard Mode screen again select Coding and Linework Settings /[F3] Edit. This is essential for the correct use of the Code list etc. 1. Quick Code set Off although the prototype code list has been set to use 3 digit codes if this is switched On. 2. The Rec Free Code set to Before Point. 3. Attributes set to Last Used means that values added for a feature code will be remembered it is used again. when 4. Mand Attribs set to Code change Only so that shots without a change of code will not request the attribute values again e.g. a row of trees all with the same dimensions. 5. Thematc Codes set to With Codelist allows the Code input to enter the codelist. 6. Show codes set to All Codes. 7. String Attrib set to 1 will use the string number attribute as set in the LSS prototype codelist. 8. Then select the Linework tab. Check that Begin Line is set to BEG to allow LSS to automatically recognise a System 1200 start of string. 9. Finally press CONT to confirm settings and [F1] Store to update the configuration set. ID Templates On the Wizard Mode screen again select ID Templates / [F3] Edit. Note: The settings should be made according to those shown so that the instrument can increment the numbering systems efficiently. If these settings are not available, then the firmware may need to be re-installed. Please contact Leica for advice. Hot Keys and User Menu On Wizard Mode again select Hot Keys and User Menu. Set Hot Keys [F7] to be Select Free Code. Version LSSv Page 10 of 70 Mar 2017

11 1.4 Configuring System Viva The two requirements for using LSS coding on a System Viva to the best advantage are Code List - created by LSS Work Settings suitable configuration for LSS coding (identical for both EDM and GPS). Code List An example code list 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_list. The LSS point features translate as point codes and the LSS link features as point codes with lines (Note: the use of line codes is incompatible for LSS processing purposes. Please see the Export Code List section below). The following steps explain the method of transferring this code list to the Viva; 1) Copy the required Code list files.xcf,.x06 and.x23, from the LSS media Code lists folder to the Code folder on the card or USB memory stick. 2) Transfer the Compact Flash card / USB memory stick from your computer to the Viva. 3) From the Main Menu User Tools & utilities Transfer user objects 4) Set Object to transfer as Codelist Set From as either CF Card or USB depending on the data transfer media Set To as Internal memory Set Codelist to the relevant code list OK [F1]. Version LSSv Page 11 of 70 Mar 2017

12 Work Settings ID templates From the Main menu User Work Settings ID Templates TPS points as <Manually enter> TPS auto points as TPS_Auto_0001 Lines as Use code & string or Line0001 Note: These screen captures use TPS 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 dialog ID Template Library second Where relevant click Edit after selecting your choice This will display the New ID Template dialog Set Increment By as 1 Note: The New ID Template dialog is not available because some options are system ID templates and cannot be edited e.g. <Manually and Use code & string always enter> Note: It may be necessary to go down one to Area001 first, to effect this change. Version LSSv Page 12 of 70 Mar 2017

13 Coding & Linework Returning to Work Settings select Coding & Linework Code & attributes tab Tick Use a list box to view codes Set Suggested attributes to Last Used which recall the last attribute value for each individual feature e.g. for link features the last used string number for the selected feature will be offered. will Set Prompt for Mandatory Attributes to Code change Only 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 using the right and left arrow keys. Linework tab Tick Automatically create lines & areas when coding. Tick Use a stringing attribute and set Attribute to Attribute 1 Set Begin Line to BEG or. Quick coding tab Set Quick coding to Off Note: The LSS prototype code list has been use 3 digit codes if Quick coding is switched Set Store free code to Before pt is stored i.e. all Free code (F7) additions made before a shot to that observation. set to on. apply Version LSSv Page 13 of 70 Mar 2017

14 My Survey Screen Returning to Work Settings select My survey screen Note: This configures the displayed items seen during detailing. Here we will edit the Code tab to help us how the feature coding works with the attributes in LSS code list. This will not affect the information displayed on the Survey screen. see the Select the relevant Page number for the Code page Define Page 3 (Code) and click Config 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 Hot keys & favourites Returning to Work Settings select Hot keys & favourites Tab TPS hot keys Set F7 to Data - Select free code from list Version LSSv Page 14 of 70 Mar 2017

15 1.5 Configuring Captivate The two requirements for using LSS coding on Captivate to the best advantage are Code List - created by LSS Work Settings suitable configuration for LSS coding (identical for both EDM and GPS). Code List An example code list 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\LSSv10Captivate. The LSS point features translate as point codes and the LSS link features as point codes with lines (Note: the use of line codes appears unnecessary and has been avoided because of the incompatibility when processing the same code list from a Viva. The following steps explain the method of transferring this code list to the Viva; 5) 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. 6) Transfer the Compact Flash card / USB memory stick from your computer to Captivate. 7) From the Main Menu Settings Tools Transfer user objects 8) 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 OK [F1]. Version LSSv Page 15 of 70 Mar 2017

16 Work Style Settings ID templates - To set the ID Templates.. From the Main menu Settings Customisation ID Templates TPS points as <Manually enter> TPS auto points as TPS_Auto_0001 Note: These screen captures use TPS only as the example. 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 New 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 Note: It may be necessary to go down one to Area001 first, to effect this change. Version LSSv Page 16 of 70 Mar 2017

17 Coding & Linework Returning to Work Settings select Coding' 'Coding & 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 e.g. for link features the last used string number for the selected feature will be offered. 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 using the right and left arrow keys. User defined pages Returning to Customisation select User defined pages Note: This configures the displayed items seen during detailing. Here we will edit the Code tab to help us see how the feature coding works with the attributes in the LSS code list. This will not affect the information displayed on the Survey screen. Select 'Page 3' to use as the Code page To define Page 3 (Code) click Edit' Version LSSv Page 17 of 70 Mar 2017

18 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 Hot keys & favourites Returning to Customisation select Hot keys & favourites Tab TPS hot keys Set F7 to Data - Select free code from list Version LSSv Page 18 of 70 Mar 2017

19 1.6 Summary of Session You should now have an understanding of: a) How to access and install LSS and other files. b) How to install the various files needed to download survey data from the Leica DBX based instruments. c) How to Configure the various Leica instruments. If you have any questions on the above subjects then please ask the trainer now. There will now be a break for refreshments. Version LSSv Page 19 of 70 Mar 2017

20 2. Session 2 Duration: 1 hour 30 minutes 2.1 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. Before we go outside, we will just go through codes used in the exercise and then explain how to start a new survey job on the survey instrument. The rough guide, Feature coding for Land & Eng. Surveyors. Titled Principles of Survey and Feature Coding. can be found on the LSS Installation media or the Website, is a good reference. Version LSSv Page 20 of 70 Mar 2017

21 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. Version LSSv Page 21 of 70 Mar 2017

22 Leica 1200 / Viva / Nova Workshop Coding Details PtID/ Setup Free code Attributes Code Attributes Description / Reason Setup 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. 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 Version LSSv Page 22 of 70 Mar 2017

23 2.2 Instrument Data Capture on a Leica 1200 Creating a new 1200 job Select option 1 Survey from the Main Menu to access the Survey Begin screen. Note: Select by pressing the number 1 key, or by navigating to 1 Survey and pressing the Enter key, touching the Survey icon when using an active screen. or by touch Select the Job list and Enter. Select New 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. Returning to the Survey Begin page, the Coord System, Codelist and Config Set should be set for new survey e.g. as per the LSS media Support_files folder. Note: When using a TPS the Setup needs to be selected from this page unless no co-ordinate information is required during the survey. In which use the Free Code Setup Fr, and the Point codes Setup Pt and CTLObsRO to store the Setup and control obs information for LSS purposes only. the case Note: CTLObsRO may also be used following a CTLObsID when multiple control obs are required and recorded average is to be avoided. Version LSSv Page 23 of 70 Mar 2017

24 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 from LSS to Leica 1200) and then copied to the current job before doing the first set-up using Convert [4] then Copy Points Between Jobs [3] Press SETUP [F3] to input the details and observe baseline stations. the For Method choose Set Azimuth to supply an arbitrary bearing. For Station Coord use From Job rather than Frm Fixpoint Job (see first paragraph above). Select the Station ID to select or enter a new station (as shown) Enter the Instrument Ht. If you have selected a new Station ID the New Point screen will be displayed for co-ordinate entry. press STORE [F1]. Then Press CONT [F1]. Select the Backsight ID Enter the Reflector Ht. Click Az=0 to set the HA to 0 Press DIST [F2] to measure the distance to the RO. Press SET The Instrument confirms that the Station and Orientation has been set. Press OK [F4]. You are now in the detail measurement screen. Control Observations For a control observation highlight the Point ID and press Shift INDIVID (avoids the incrementing Point then enter the station ID For Code select CTLObsID and take the shot - do use the ST Reserved code. IDs), NOT Version LSSv Page 24 of 70 Mar 2017

25 Detail procedure For basic measurements centre the TPS1200 accurately on the prism at your detail point, set the Point Id (e.g. to 1) and press ALL [F1]. If the ATR is being used the Total Station needs only to be aimed approximately at the prism. If LOCK is being used the Total Station will follow the prism as it is moved from point to point. The DIST [F2] and REC [F3] keys can be used instead of the ALL [F1] to measure an object that the prism cannot occupy the centre of (e.g. a pole). The prism is placed next to the object and DIST pressed to measure the distance and place it in a buffer. The instrument is then turned so that the centre of the object is bisected and REC pressed. Note: that LOCK must be disengaged to use this function. Detail Coding LSS uses Point coding and Free coding. The Codes accessed via the display entry Code and the Free Codes via the Select Free Code [F7] key. are In each case the relevant part of the Code list is displayed as exported from LSS (see the LSS media Support_files folder). Using the arrow keys highlight the Code entry and the required code or Enter. type The codelist will appear defaulting to the closest to the typed characters. The arrow keys can further used to manually select the required code. entry be CONT or ENTER will return to the display mask with highlighted feature code. the Version LSSv Page 25 of 70 Mar 2017

26 Attributes Attributes are integer, real, text or choice-list values in certain features in the code list and behave in the following way: used The Code Display mask will show the required attributes for the selected Point feature code. It is necessary to use the ATTRIB button on the list to change an attribute that is not set to mandatory. code For the Reserved codes this applies to REC and RIN. Where Attribute 1 is the string number it can be left blank and a new string is started each time the code is toggled. This is true even when the code remains the same. Free-codes Free- The Reserved codes, e.g -REC. are all referenced as codes via the [F7] button and behave in the following way: A Free-code is additive to the Point code currently in i.e. As well as, NOT replace. Free-codes can be stacked, e.g. Notes and REC can added on a single shot. use, be Note: Not all combinations work. A Free-code applies to One shot only as it only applies to the current observation and does not appear on subsequent measurements. The LAST button will show the last used codes in order. Version LSSv Page 26 of 70 Mar 2017

27 Subsequent set-up procedure When it is time to move to a new Survey Station; a. Press ESC to leave the Survey: screen b. Press ESC to leave the Survey Begin screen and return to the Main Menu. c. The TPS1200 can now be turned off. At the new Setup, switch on the instrument and use the SETUP [F3] option in the Survey Begin screen to enter the Station Setup screen where subsequent set-ups on a job assume a coordinate system using the existing Station coordinates. For Method you can now choose Known BS Point. For Station Coord choose From Job For Station ID select or enter an existing station Enter the Height of the Instrument. Press CONT [F1] to go to the Set Stn & Ori Known BS Point. Select the Backsight ID and enter the Reflector Ht. The instrument will report the calculated azimuth and horz dist. Press DIST [F2] to measure the distance to the RO. Press SET The Instrument confirms that the Station and Orientation has been set. Press OK [F4]. Important Note: Never insert or remove the Compact Flash [CF] card unless the System 1200 sensor is switched off. If there is data access to the CF card when removing or inserting it, your files may become damaged. Version LSSv Page 27 of 70 Mar 2017

28 2.3 Instrument Data Capture on a Leica Viva Creating a new Viva job Select option Jobs & Data from the Main Menu Select the 1 New Job list and OK. 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. Version LSSv Page 28 of 70 Mar 2017

29 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. To set the set-on station name and details, set Station point from to be Enter new point then the Instrument height. Click OK enter On the New Point screen, specify a Point ID (i.e. Station name) and the relevant arbitrary coordinates. Specify a Backsight ID, Target Height and Direction Sight the target, then press Dist then Set You are now ready to start detailing. Version LSSv Page 29 of 70 Mar 2017

30 Detail 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 Go to work menu select 2 Survey In the Code option click the list icon Using the arrow keys highlight the Code entry and the required code or Enter. The codelist will appear defaulting to the closest entry the typed characters. The arrow keys can further be to manually select the required code. type to used OK will return to the display mask with the highlighted feature code. Attributes - The display mask LSScod will show the required attributes (either integer, real, text or choice for the selected feature code. Note: The LSS default for mandatory attributes is on code change. The default values as set in the codelist. list) Only Note: The current feature remains active on repeated measurements. Note: It is necessary to use the ATTRIB button on the code list to change an attribute that is not set to Mandatory as per reserved codes, -REC and RIN. Note: The LAST button will show the last used codes in order. Version LSSv Page 30 of 70 Mar 2017

31 Images LSS fully supports the imaging/photos on the DBX based instrument series. 1. When recording an image it must be attached to a PointID or a set-up. 2. When a DBX job is selected the images are found and copied to the Images subfolder of the LSS model automatically. 3. 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. a. 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. b. 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. c. All the sub-folders of the browsed DBX folder are searched and any of the DBX jobs can be processed. d. However, the archiving option and copying of the images is not available unless the actual job folder is browsed directly. e. If the images have not been copied use Explorer to copy them separately to the Images sub-folder of the LSS model. Version LSSv Page 31 of 70 Mar 2017

32 Extras Using F7 Freecode Notes o In order to maintain your input text exactly as entered use & - When adding F7 Notes the user may sometimes want to make sure that the whole sequence of typed letters appear exactly as entered i.e. that the conversion does not apply standard character stripping etc. An example would be the phrase 0.2m wide may appear as.2m wide in the LSS model because leading zeroes are stripped. The solution to this is to use an & character at the start of the Note i.e. &0.2m wide will appear as 0.2m wide in the LSS model. Applications o Reference Plane This relates to the use of the -EL Elevation reserved code when wanting to survey an elevation (a vertical plane as a plan) then it is best to use both Reference Plane and the EL code at the same time. By using this application during a topo survey the instrument will allow the graphical map to display the elevation in plan but when returning to the survey application the map returns to the main coordinate system. All points will be saved as radial data and therefore when processed in LSS will be seen as radials. If the user adds the code -EL when entering the application then LSS will be able to see these radial shots as an elevation as well and process them accordingly. The Reference Plane Base Points are processed as Comments in the Load file and therefore can be cut and paste into the Elevation processing dialog. The XYZ of the transformed grid can be calculated from angle only shots these are written to the load file as comments. These can be added to the LSS calculated face plane coordinates manually as long as the Y and Z values are reversed Viva (or later) imaging option displays lines and points on the camera video feed so no need for Ref Plane 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. String information - The Job reader only reads the points and the point features from an LSS exported dbx all link features are missing i.e. return as spot levels. This is because the lines created by the DBX export option (Points and Lines job) uses an alternative method to denote the linework.. 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. This is so that the latest coordinate value will be the one to be used by LSS. Version LSSv Page 32 of 70 Mar 2017

33 Smart coding To turn on Smart coding at this stage click the and set the values as listed; CONF Use SCodes Yes Measure point - No (this can be set to Yes during survey to automate the data collection by selecting CONF) the Shift 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) 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 the Codes button [F3] and select your first code the codelist. press from Note: String numbers need to be used and can be added to the entry point directly below each feature. 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. Version LSSv Page 33 of 70 Mar 2017

34 2.4 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. Version LSSv Page 34 of 70 Mar 2017

35 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. 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. Specify a Backsight ID, Target Height and Direction Sight the target, then press Distance then Set You are now ready to start detailing. Version LSSv Page 35 of 70 Mar 2017

36 Detail 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 Using the arrow keys highlight the Code entry type the required code or Enter. and 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. Note: The Last button will show the last used codes in order. Version LSSv Page 36 of 70 Mar 2017

37 2.5 Summary of this Session You should now have an understanding of: a) The various methods of string coding. b) How to use LSS Reserved Codes. c) How to start and carry out a survey on the instrument. d) How to carry out detail coding on the instrument. If you have any questions on the above subjects then please ask the trainer now. There will now be a break for lunch. Version LSSv Page 37 of 70 Mar 2017

38 3. Session 3 Duration: 1 hour 30 minutes 3.1 Configuring the Leica Job (DBX) reader in LSS This is a once-only operation, for each type of instrument to be used, on every computer into which data is to be downloaded. To configure our logger of choice in LSS we select Configure Hardware & System, followed by Logger - New (if this is already another logger configured then the option will be Logger / Change ). Now we need to choose the format of the data. We will configure LSS as a Leica logger using the Job (DBX) Reader. Select the logger format as Leica and the description as DBX. give Next we choose 'Job (DBX) reader Clicking OK will allow us to Finish and Save our logger settings to the registry. Note: This must be repeated for all PCs that are to use the Job reader. Once installed and configured, the Job reader will read the card and the list of jobs will appear in the next window. On selection of the Job to process LSS will directly create a Load file. Version LSSv Page 38 of 70 Mar 2017

39 3.2 Configuring the New Survey Parameters in LSS For each survey the following parameters are set during what is termed the survey initialisation process, which is the starting point for all surveys. The command Configure Hardware & System - New Survey Parameters allows many of these options to be set in the following window: Set the Handling of 2-D data, Alter standard Annotation of Levels for hydrographic surveys. The Drying height is the height above Chart Datum to be considered as tidal. Set Survey units for length, area and volume in the survey, And other survey parameters: Angular units, Obs format, Vertical angle collimation. Control tolerances set the Load values for Warnings and Errors, and also maximum and minimum Target heights, 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 be set to 1.0, but, Note: GPS data (including stations) based on the OSGB36 TN02 transformation should have the local scale factor applied here. Curvature / refraction adjustment - will apply a fixed correction to radial survey data. The difference in level between adjusted and non-adjusted observations amounts to 7mm in the first 1km, rising to 7m at 10km, so is rarely of concern for most surveys. Conditioning tolerance - applies to arcs and circular steps - either surveyed or Co-Go generated - or when Output smoothed links is used. Angles format all survey data is displayed in this format and can be changed. Obs format cannot be changed once radial survey data have been processed. It is possible to have different formats contained in loadfile(s), but after being processed all survey data is displayed / reported in this format. VA Collimation - sets the default Vertical Angle at horizontal- either 90 or 270. LSS is able to process combined Face Right and Face Left station observations. Control tolerances refer to the survey data processing of control observations. When a control (station) observation exceeds the warning or error values it is reported. However, when an error is issued the survey processing will be terminated as well. It is the responsibility of the surveyor to be aware of these settings. Note: It is possible to use negative target heights for when the detail pole is inverted, but exceeding the set values will also issue a warning. Version LSSv Page 39 of 70 Mar 2017

40 3.3 Configuring the File Editor in LSS etc Configure / Hardware & System This menu option controls the default LSS settings within the registry on this PC. File Editor which application opens the browsed data file when the Edit button is clicked. Note: HiEditor is the recommended Editor for LSS and is installed with v10 and set as the default unless a previous version of LSS was already installed. In this case HiEditor will need to be selected here. New survey parameters holds the default settings for when a New survey is created; Control tolerances - for Control Observation warnings and errors. Target Height Load issues warnings if a target height is outside this range. Copy Prototype from an LSS model that contains a feature legend template and display settings. Note: the LSS model Prototype.LSS is available in the \Testdata\Prototype folder (see above) and if copied to, say, d:\<survey Folder>\Prototype it can be user defined. Saving the configuration changes If a change is made then on return to the main dialog a Finish button will be offered. Click 'Finish' will offer the Configuration changes options. To save the changes select Save and click 'OK' when LSS will permanently save these settings on this PC. Version LSSv Page 40 of 70 Mar 2017

41 3.4 Creating a New Survey in LSS A survey must be open to process data into LSS and we will this exercise in a new survey. do Select File New from the main menu. Click Browse against New survey. Create a new folder for the new survey to go in and call it e.g. C:\ Surveys\Workshop; Select it in the Save in box Enter the survey name, e.g. Workshop Survey to File name. Click Save. This will return to the File New dialog with the path and name of intended LSS survey. Enter Survey title (if left blank will use the survey name). the LSS The Prototype will be as per Survey Parameters (see above). If we had stations already at the we could bring them in here, We will set the survey so any 2- data will go to the survey s Nonterrain. New site D Tick Configure Survey Parameters, then Version LSSv Page 41 of 70 Mar 2017

42 Click OK Version LSSv Page 42 of 70 Mar 2017

43 Ticking the Configure Survey Parameters allows us to revisit the parameters set during the initialisation process, and we would not normally require this: Or this window can also be invoked by the command Configure Survey Parameters. But if we continually have to reset a particular parameter, then it might be worth reconfiguring the New Survey template values. Note: the LSS Prototype is found in Testdata and also in Prototype directory, and either can be used here. Testdata is set here because this is where all the training datasets are held. It is assumed that the surveyor will look to create their own prototype for their features in say C:\Surveys\Prototype and so will not be accessing the original LSS prototype in Testdata. Version LSSv Page 43 of 70 Mar 2017

44 Data processing Input Download / Convert The first task is to transfer the CF card from the instrument to the PC. Selecting Input Download / Convert will invoke the Download data window. If Leica Job (DBX) reader is not shown nor is it present on the logger list when Change is selected then we have not already configured a logger. To rectify this click New and following the dialog boxes or refer to the Configure Logger section above. Note: If a Leica GSI file e.g. '.SVY', from reading a Job via Legacy mode, already exists on the C: drive, we can tick No DBX read (convert GSI data file). This will skip straight to the conversion dialog where the file is selected as the 'Downloaded file'. Click Next Select the DBX folder by either; a) Clicking Browse (particularly useful when the DBX folder is on a CF card) and Click OK, or b) Click Explorer (particularly useful if the DBX folder is already on the PC). This uses a Windows Exporer dialog from which the DBX files (or the folder itself) can be selected using drag and drop. Clicking OK to the selected Job folder will provide a list of the Jobs in that folder. Select the required Job and click OK. Note: For Viva (or later) instruments each Job is located in its own folder Note: The 'Use Legacy DBX method' is present to allow a user to process a Job as per LSSv9.91. Please see the documentation from this version if this option is required. Click 'OK' Version LSSv Page 44 of 70 Mar 2017

45 If the LSS load file input box is empty and 'Next' is clicked then will automatically provide the next available load file number for the current survey. LSS 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 DBX job database will copy the database files to a sub-folder of the current survey. Note: The job database files (DBX) are not archived if browsed from within the current survey sub-folder tree (the option will be greyed). Click 'OK' to process the Job, create the Load file, and automatically invoke Input Load. 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. Version LSSv Page 45 of 70 Mar 2017

46 Data processing Input Load Introduction The LSS Load Input file is the format by which all external data is processed into LSS e.g. data from a survey instrument has to first be converted to a load file via the Input Download & Convert option. 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 we select the file type. Leave the options as per default and click 'Next'. If the survey is empty and no station coordinates provided prior to the first instrument set-up Load file, then an Initial Set-up dialog will presented to verify the station coordinates orientation. are in the be and Click OK. Otherwise the station coordinates from the Leica instrument are loaded along with the detail. Clicking the Edit button next to the Load file 001 will open the load file in Programmer s Notepad, if this has been set as the File editor, The Load file can be viewed and edited to address any issues raised during Input Load. Version LSSv Page 46 of 70 Mar 2017

47 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 Programmer s Notepad; 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. 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. We may also use the special or Reserved codes, described in detail in the next session. 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. Version LSSv Page 47 of 70 Mar 2017

48 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; a) Coordinate system used (including the geoid and CSCS files used). b) Transformation name and type c) Projection Scale factor Note: The processing will also include comments on; a) which detail observations have zero values and have been removed b) whether a station observation is being used as 1d, 2d or 3d. i. 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. ii. 2d station observations have their target heights removed so that height differences are not attempted to be reported a) whether a station coordinate is 1d, 2d or 3d. i. If a station's xyz coordinates are all zero then it is ignored. ii. If it is 1d it is reported but not used iii. If it is 2d it is reported and used. Note: The set-ups in the load file are annotated with the Set-up type Version LSSv Page 48 of 70 Mar 2017

49 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 respecify the error tolerance to allow the load. Often errors occur simply because the stations have been incorrectly labelled during the setups, or there is one poor observation. To correct these click Back and then Edit to open up the load file. If you have set PFE as your editor program then use CTRL+G to go to the line directly. If available, Click 'OK' to continue and 'Continue' to complete the load and display the data. This includes updating the triangulation to create the DTM. On the screen, the loaded survey should look like the screenshot: Note: Attachments in form of images come through the survey the have from data. Version LSSv Page 49 of 70 Mar 2017

50 3.6 Leica 1200 format file This will not be required under normal circumstances but as as a back-up a format file is supplied on the LSS media in \support_files\leica\jobdbx\format\lss1200.frt. This will allow the user to export a file from the instrument that is identical to that created in the Job reader (Legacy mode). You will need the LSS format file if; There is not a working version of the Job (DBX) reader available In this case copy the format file to the CF Card and then Transfer it from the CF-card to System RAM using the similar procedure to transferring the code list shown earlier. Then from the main menu choose 4 Convert then 1 Export Ascii and then select the LSS format file. This will create a file identical to the SVY file created by the Job Reader (Legacy mode) and can be copied to the PC. There is a need to post-process the DBX data in Leica Geo Office. When using conventional GPS it may be necessary to post-process the observations with Rinex dat in Leica GeoOffice. In this case use the option Export / Ascii with the following settings; a. Filetype Custom Ascii b. Right click on New Settings Add name c. Settings button d. Coord class Current e. Sort by time i.e. not Point ID f. Format template: use LSS1200.frt from the \support_files\leica\jobdbx\format folder on the LSS media. g. Deactivated points turn off Note: This will not include the free codes. Processing in LSS Following the processing sequence in Input / Download and Convert shown earlier just tick the box No DBX read (convert GSI data file) which will skip the Job reader and then Browse the exported file as the Downloaded file in the conversion dialog. Version LSSv Page 50 of 70 Mar 2017

51 3.7 GPS Survey Instrument Issues GPS data can be read directly from the DBX Job when CSC and/or GEM projection files are in use as long as the GPS coordinate system is OSTN02 or OSTN15, or similarly for Northern Ireland and the Republic of Ireland. Note: During the Input Download / Convert process LSS will report if a job is using CSCS or GEM files on the job list. Or as a local grid via a coordinate transformation or a fixed base station and the levels relate to Orthoheights. Combined GPS (coordinates) data and TPS (radials) data will be processed simultaneously during the same DBX read. Scale factor If the Job coordinate system contains a scale factor then LSS can also apply this and therefore correctly maintain the radial (TPS) data with the GPS data in the same LSS model as long as the Geometric scale factor is automatically set on the instrument For the 1200: Select the Station Setup dialog Click Scale Set TPS corrections / GeomPPM / Calc Scale to Automatically. For the Viva Select Jobs and Data Select New job or Job properties (if it is an existing Set Compute scale using to & coord system job) Stn This enables LSS to set the relevant scale factor for each individual station and apply this to each shot in the set-up and also to seamlessly process Smartpole data. The grid scale factor in an LSS model can be changed to a local grid using File\Transform\Scale. This requires the use of File Transform to first Transform Obs as XYZ (which converts all radial observations to XYZ). Version LSSv Page 51 of 70 Mar 2017

52 3.8 Summary of this Session You should now have an understanding of: a) Configuring LSS for the Job (DBX) reader and other functions. b) Creating a new Survey file in LSS. c) How to process a Leica DBX Job into an LSS Load file. d) How to load the survey raw data file into LSS. e) The Input Load warnings and errors. f) Some Leica DBX GPS aspects. If you have any questions on the above subjects then please ask the trainer now. There will now be a break for refreshments. Version LSSv Page 52 of 70 Mar 2017

53 4. Session 4 Duration: 1 hour 10 minutes 4.1 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 are copied to the CF card or USB ready for transferring to the instrument. Version LSSv Page 53 of 70 Mar 2017

54 Exporting a Leica DBX Job The option Export / Leica DBX database directly exports the LSS model as the three types of DBX job file direct to DBX based instruments. The user can choose from; a) Standard survey DBX all the observations are exported as Control points with the same point number as LSS and the linework has the same colours as the LSS legend b) Stations (Standard survey DBX) the stations are exported as Control points c) DTM DBX d) Road alignment DBX - can be exported as an SPF of a design geometry file or an SPF with single or multiple reference strings. Note: If multiple reference strings are selected via a combination of 'Links as alignments' and 'SPF' then it will be the longest string that is accepted by Leica as the Centre line. 1) From the main menu, select Export/Leica DBX database. 2) Specify a folder name for the exported files using Browse or Explorer. If the folder name not exist LSS will create it. does 3) Specify a Job name and Description which will become the Job name on the instrument. These will default to the survey name and its description. 4) 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. Version LSSv Page 54 of 70 Mar 2017

55 5) If Road (alignment SPF) is selected an SPF will be needed. Note: An SPF can contain either; a) a road design geometry imported via MX Genio or LandXML or b) a normal SPF that can contains multiple reference This can be created by; lines. SPF name Offsets Section title this will be name of the alignment in DBX (if empty the SPF file name will be used) the the Line method Click Next Select Mode / Whole String and then pick the string required For each reference line select reference line and type a unique name for the section title New When complete choose End and SPF and OK Save Version LSSv Page 55 of 70 Mar 2017

56 Opening the DBX files in Viva 1) The following examples are using the Viva PC simulator 2) Once the required files have been created the folder can be copied as a sub-folder to the DBX folder on the CF card. 3) At the main menu click on the Map button 4) Then Jobs 5) Select the exported Standard Survey as the job Data 6) Then select the Road job and the DTM job as relevant Version LSSv Page 56 of 70 Mar 2017

57 7) Click OK and then the Zoom All button to see the data 8) The display can be configured to show what is required 9) The survey data 10) The DTM 11) The Alignments 12) You are now ready to use the relevant application Version LSSv Page 57 of 70 Mar 2017

58 Opening the DBX files in the ) The following examples are using the 1200 PC simulator 2) Click on Survey 3) Then click select the input box for Job 4) Then select the imported job 5) The data can now be displayed on the Map and set-out using the Stakeout onboard application. The DTM and Alignments will need to be accessed via the relevant applications Version LSSv Page 58 of 70 Mar 2017

59 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. Version LSSv Page 59 of 70 Mar 2017

60 Exporting Data as a Leica GSI File Note: The logger parameters be altered by clicking Change or using Configure Hardware & System / Logger. Specify a name for the exported and click can by file 'Next'. This dialog allows the selection observation and station data. The defaults assume that the Observations will be exported the Selection filter. Click of using 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 will offer the opportunity of multiple observation selection criteria. dialog Hit Apply to make selections on screen there can be many. the As soon as there are observations selected then the 'Cancel' button is replaced by Finish. Click Finish once all required is highlighted. data 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. There is the possibility of repeating several selection criteria to the same data set. If required, we can click Add more data and repeat the process. We might choose this option to export Survey stations or specific observations. Version LSSv Page 60 of 70 Mar 2017

61 Version LSSv Page 61 of 70 Mar 2017

62 4.2 Exporting an LSS Code List The LSS option Export Upload code list to survey instruments will produce a Leica code list. However, we suggest that for new users the LSS prototype legend (supplied with Testdata on the LSS media) is used as a standard starting point for which there is a pre-built code list available in the Support_Files\Leica\JobDBX\Code_list folder of the LSS media. Please refer to the Transferring a code list in Session 1 above that explains how to copy these files onto the device. As a consequence it is suggested that the Export code list option is best used for sending new additional features to the Leica code list as they are added to the LSS Prototype Survey. Follow the process below to create a new code list in Leica Geo Office and then cut and paste the new features to the existing code list before placing it back on the instrument. Within a survey containing the prototype legend use the option Export Code list to survey instrument / Leica. Provide the filename for the code list. Use LSS to generate the IDX code list Note: It is suggested that no path is provided i.e. no backslash, so that LSS will save the file in the current survey path. When imported to LGO this will also then become the path for the LGO database files. Version LSSv Page 62 of 70 Mar 2017

63 Version LSSv Page 63 of 70 Mar 2017

64 Select the required point features. Tick the Use trailing digits as dimension attributes under Points if there are dimension items e.g. PT1, PT2,,PT20 etc. This will allow LSS to export these as a single feature with a Mandatory integer attribute for a more efficient code list. Note: It is important in this instance to have an extra feature without the numeric suffix e.g. PT, within the legend so that LSS can convert the items cleanly during the survey processing. Select the required link features. Tick the Include attributes for string numbers (links only) under Links if required. This will add a Normal integer attribute, with a default of 0, so that each link feature can have a string number. Leave the Extra LSS codes 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. OffsetLR, OffsetFB and OffsetUD are identical to the relevant reserved code offsets and SetupFr, SetupPt and CTLObsRO are for use when not using the instrument set-up and coordinate menus. The primary String codes and Code words are; CTLObsID for point coding a control observation for the instrument and LSS simultaneously. 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 The reserved codes as a group 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. This also requires the features PD and PS to exist without the integer value as per Point features. Note: The Tree feature has several attributes combined to make it a tree function including adding height and species information as well as the spread and trunk. Select TPS1200 and click OK. Version LSSv Page 64 of 70 Mar 2017

65 4.3 Leica Geo Office Importing an LSS Codelist from an IDEX file Click on the Codelists icon to open the Codelist Management screen in Leica Geo Office (LGO). Click on Codelists under the Management pane. Right click on the mouse in the Contents panel, which contains the Codelists folder. Select Register option to open the Register Codelist panel. Browse the IDEX file folder. The file name will in line with Name: Note: Once an IDX code list has been imported its name will appear duplicated on this list but without the IDX suffix. Always chose the name with.idx Click on the drop down arrow to the right of the top line if there is more than one suitable file in the folder. Once the correct file name is displayed in the top line, click on OK to Register the IDEX file. A dialog will appear saying Register codelist from IDEX with a warning that the IDX file will not maintain the changes in the code list edits. Version LSSv Page 65 of 70 Mar 2017

66 Use the pull down arrow to the right of the Instrument Class: field and select the Instrument Class that the Codelist is for i.e. SYSTEM1200 Leave the Type: field as Advanced. Click OK. The new Codelist will be displayed in the Contents pane with the same name as the IDEX file. If you wish to rename your Codelist, right click on the Codelists file name and select Modify Note: There is a limit to the amount of code list information that can be imported via an IDX file. If necessary Points, Links and Extra LSS codes can be exported separately from LSS and Cut and Paste from separate codelists into your prototype within LGO. This is the LSS suggested way of creating code lists: i.e. cut and paste newly exported features into the existing LSS prototype code list after deleting those codes that are not required. Clicking on the + next to the file name will display the Code Groups. Clicking on the + next to a Code Group will display the Codes in that Group. The exported link codes from LSS require the Linework setting amending. To do this, left click on the Links group to display all the exported links in the right hand pane. Version LSSv Page 66 of 70 Mar 2017

67 Then in the right hand pane right click on each link feature and select Properties. Change the Linework from None to Start (This applies to v5 firmware format upwards). The right hand end of the dialog will now show the additional properties e.g. Line Style and colour which can now also be set. Important Note: Both the LSS prototype code lists LSSv10Captivate and LSSv9_80 on the LSS media have been generated from the LSS prototype legend and have had all the above work already applied and is ready to put straight on the instrument. If you require to amend the required code list and/or export an IDX code list from LSS you will need to have Leica Geo Office installed (LGO Tools v6 is available on the LSS media). As an LSS user you only need direct use of LGO for the Code List Manager and only then when you wish to amend the prototype codelist supplied with LSS. Other examples of code lists have also been provided e.g. LSSv980Road and LSS1200Adv, to give examples of what can be added to a code list. Version LSSv Page 67 of 70 Mar 2017

68 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. Version LSSv Page 68 of 70 Mar 2017