TopSURV 8: Creating a Custom Code Library. Oscar R. Cantu

Transcription

1 Oscar R. Cantu

2 Data Entry Method of Codes versus Notes, review Supported Code Library File Formats, review Export existing Code Library from office software Modify for Import into TopSURV Import a Code Library from a Custom Text File Review of Import and Editing Exporting a Code Library from TopSURV Standardizing all future field jobs with Default Code Library

3 TopSURV 8: Creating a Custom Code Library What it is: Our company has an existing Code Library within our CAD software. However, we do not have this Code Library available for our field crews. What it could be: Our company has standardized between the field and office with a single Code Library file. Therefore, each time that our field crews submit field work, we have to process each measurement looking for and fixing possible mistakes in the job s Coding. As a result, the field crews have a listing of our company s Codes to select from while they take their measurements. Plus, we only get a text file of points from the field crews. We d like to have linework too. Plus, their normal procedures in the field now deliver three dimensional linework and we can collect GIS code and attribute information now and then.

4 In TopSURV version 8 field software, there are two distinct options for working with either Codes or Notes. The option to toggle between the two are found within the Configure >> Codes >> Global Code Options screen. Here, you can toggle between the two Data Entry methods of either Codes (by default) or Notes. The two Data Entry methods affect how you describe your field observations, resulting in either: Point Number, Northing, Easting, Elevation, Codes - or - Point Number, Northing, Easting, Elevation, Notes

5 The two Data Entry options of either Codes or Notes are available to support the unique ways that field work can / could be described.

6 Using the Codes method, special characters such as decimal, asterisk, slashes, or white spaces are not used. The Data Entry method of Codes is available for users that have and are using an existing Code Library. Meaning, you have standardized between the field and office that the same Codes are to be used for data collection. These often short Codes such as BM, CP, EOP, etc are functional (they do work for you). They control the field observation s Point Symbol, Color, Layer, etc. Using the Data Entry method of Codes, users are offered a pull down menu of all available Codes from the field job s Code Library. You can then automatically generate 3D linework in real time as you collect your field data as well as satisfy (GIS) Code and Attribute information.

7 Using the Notes method, special characters such as decimal, asterisk, slashes, or white spaces can be used. The Data Entry method of Notes is available for users that are not using an existing Code Library. Meaning, you have the option of typing / declaring anything that you like to describe your field observations. Typically, the Data Entry method of Notes is used by those who do not want to have their field work sorted by Layer, Point Symbol, Color, etc. in TopSURV. Instead, their approach is to export a simple text file from TopSURV and task their office software with sorting Point Symbols, Layers, Colors, etc. Using the Data Entry method of Notes, users are not able to automatically generate 3D linework within TopSURV.

8 We use the Codes method since we have a standardized Code Library between the field and office. We are interested in automatically creating and exporting Code Driven Linework within TopSURV. Plus, we also occasionally collect (GIS) Code and Attribute information. We use the Notes method since we typically describe our field work not with repeating Codes but with information like, TREE*3ft,Pine. We need to use special characters such as a decimal, an asterisk, slashes, and / or white spaces.

9 TopSURV 8: Creating a Custom Code Library

10 Default Code Library Recall that by design, TopSURV v8.0 and higher will automatically use a default Code Library as part of the software installation. Therefore, if we do NOT want to use this default file and instead want to use a custom Code Library, we will need to remove this global option. Here is how. Go to Configure >> Codes and look within the Code File edit field.

11 Before After To remove the option of TopSURV automatically using the default Code Library during the creation of a new field job, simply remove the path in the Code File edit field. With this path cleared, the next field job that is created will not have a Code Library at all. This is exactly how we want the software to be since our task is to use an existing Code Library from our office CAD software instead.

12 Go to Import >> From File, where Data = Code Library to see supported File Formats for importing an existing Code Library into a TopSURV field job. Change from default import options where Data = Code Library and Format = Topcon XML (*.xml).

13 Shown above are supported file formats for direct import of an existing Code Library into a TopSURV field job. Our task for this example will be to import a text file containing (at a minimum) Codes from our office software. Any other supporting information (Code Descriptions, Layer information, etc) can be handled as well. Recall, once we import a text file of Code Library information, we will then export from TopSURV in XML file format so we can standardize for future field job creation and usage.

14 There are many CAD software options out there. To the left is a random sample file of a company s current Code Library exported as a simple text file. So how do we get this text file of information and turn it into a Code Library for our field software? We simply need to take what we have (only Code and Layer Name for this example) and import into TopSURV as a custom text file.

15 If necessary, it is common to take the text file of the Code Library export into Microsoft Excel for some quick Find and Replace and formatting. Why in Excel?..only because it is faster. The goal when done is to have a simple comma separated text file. Again, for this example, we have two columns of Code and Layer Name information. Perfect.

16 TopSURV 8: Creating a Custom Code Library

17 If other supported formats will not work, you can export your existing Code Library from your office CAD software as a simple text file. Transfer text file from personal computer / laptop to a TopSURV field controller. Possible editing in Microsoft Excel. Import the Code Library as simple text file into a TopSURV field job. Ultimately, export the field job s Code Library in XML file format. This XML file is what is used to standardize for all future field job creation and usage.

18 With the text file now quickly edited in Microsoft Excel, we saved our work in a CSV (comma separated vales) file format. Since TopSURV is looking for a text file format, we simply renamed the file extension from CSV to TXT without consequence. Transfer the resulting text file to your TopSURV field controller. It is common to place these files within the IEFiles (Import Export Files) folder in the TopSURV directory. From the main menu, tap Import >> From File to begin the process of importing the text file.

19 Pause.. Verify that Data = Code Library and Format = Topcon Text Custom (*.txt) Browse to and select the text file containing what you know and have for a Code Library. Pause. Within the Custom Code Library screen, you can define how the incoming text file is organized. In this example and from the top, we know that the text file: Is a comma separated Contains only Code and Layer Name information Does not contain a header row

20 Sample Code Library Export Since this is the first time (within this particular TopSURV field controller) that this File Style has been imported, we will tap the Add button to create a new style / format. In the listing above labeled as Available is what columns of information could be included. Tap the applicable items to select then send down into the Order section below.

21 Before After Sample Code Library Export In support of the incoming text file, we have declared a Custom Style Order of Code and Layer Name. The big idea here is to know about the incoming text file that you are working with and simply match up in TopSURV. Tap the Save button to proceed.

22 With the supported File Style confirmed and created, tap the green check at top center to begin the Customer Text File import. As a result, TopSURV will inventory the file that was just imported...now let s check our work.

23 First, we ll begin by going to the data collection screen by tapping Survey >> Topo and selecting the Code pull down menu. Here, we see all of the Codes that were initially exported from an office CAD software package. Standardization. As a result of this import, the office and field staff are instantly using the same Codes to describe features that are measured, calculated, etc.

24 For this random example, we started off with a text file that contained only Code and Layer Name information. No problem. We simply needed to let TopSURV field software know what was about to be imported and we are ready for production...what we started with.

25 Continuing with this random sample, we will look at this field job s Code Library now that we have imported our custom text file. To view a the job s current Code Library, tap Edit Job >> Code. Of course, we see the listing of all of the codes that were imported from the text file. Let s select the Code at the top, ACU and tap the Edit button.

26 Just to review what happened, the Code of ACU (we assume that this stands for air conditioning unit?) is of course available to be used for data collection. Working our way down, it would helpful to add an intuitive / easy to understand Code Description for this Code. It is set to be a Line Type of a code. This means that once we use this Code for field measurements, we will be offered a String Identifier edit field. By simply adding a String Identifier to the predictable three or four measurements, TopSURV will automatically generate linework...efficiency! Layer. For this example, all points collected with the code of ACU will automatically be placed on a layer named, PNTS-UTIL-ACU. Perhaps not ideal yet, but certainly a great start and more efficient than having to recall all codes from memory and mistakes.

27 TopSURV 8: Creating a Custom Code Library

28 If other supported formats will not work, you can export your existing Code Library from your office CAD software as a simple text file. Transfer text file from personal computer / laptop to a TopSURV field controller. Possible editing in Microsoft Excel. Import the Code Library as simple text file into a TopSURV field job. Ultimately, export the field job s Code Library in XML file format. This XML file is what is used to standardize for all future field job creation and usage.

29 From the main menu, go to Export >> To File to begin the process of exporting the field job s current Code Library to a file. Note: The task here is to export our Code Library as a single (sharable) file to be used either in other remaining field controllers or your particular field controller so TopSURV will automatically use for all future jobs that would be created. Change the from the default file export options where Data = Code Library and Format = Topcon XML (*.xml).

30 By default, the file location for the exported file will be in TopSURV s IEFiles (Import Export Files) directory. For this example, we will name the new Code Library XML file as, From TopSURV. Done. As usual, an inventory of the file export is offered showing what was done.

31 For convenience, it is common to next declare that we want the new Code Library to be used for future job creation. Here is how. From the main menu, go to Configure >> Codes and look within the Code File edit field.

32 Tap the Browse button to select the XML file of a custom Code Library that we just made. Recall, that for this example, we placed the resulting XML file in the IEFiles (Import Export Files) directory. Select the XML file and tap the green check to accept. TopSURV will now automatically refer to this custom Code Library when creating new field jobs. These new field jobs will automatically inherit (import) this Code Library and make available...let s test.

33 With the new custom Code Library now being pointed to in our Configuration options, let s quickly create a new field job to confirm our results.

34 With the new field job made, we will quickly go to Survey >> Topo and tap the Code pull down menu. Success. Here we see that as expected, our custom Code Library is automatically populating our newly created field jobs.

35 TopSURV 8: Creating a Custom Code Library

36 TopSURV 8: Creating a Custom Code Library What it is: Our company has an existing Code Library within our CAD software. However, we do not have this Code Library available for our field crews. What it could be: Our company has standardized between the field and office with a single Code Library file. Therefore, each time that our field crews submit field work, we have to process each measurement looking for and fixing possible mistakes in the job s Coding. As a result, the field crews have a listing of our company s Codes to select from while they take their measurements. Plus, we only get a text file of points from the field crews. We d like to have linework too. Plus, their normal procedures in the field now deliver three dimensional linework and we can collect GIS code and attribute information now and then.

37 TopSURV 8: Creating a Custom Code Library

38