Codelist setup in LS

Symon

New Member
Hi,

Our other question in setting up the LS is around codes and strings. Currently our (Leica) way of doing things is we have a code library and some of the codes have an attribute that must be used which is the string number (ie. Top of Bank, string 1 = TB1). This allows the 12d software which everyone uses in our part of the world to draw the topo up.

When we are working in the field you are surveying along using one code and then if you change codes (say bottom of bank to top of bank) our existing system prompts you what the current attribute (string) you are up to so you can choose whether to keep using the last string or start a new one.

1) Could someone point out how we get our current codelist + attributes into the LS?
2) Also, is it possible to set the LS to prompt us to check the attribute (string) when you change to a different code?

Thanks
 

Matt Johnson

Well-Known Member
5PLS
Codes can imported as a text file (Codes & Tags > Import).
The first line needs to be a header line that defines the fields you are importing. An example:

index.php


Possible header fields that you may wish to use include the following:

Name;Description;Category;AttrName1;AttrValue1;AttrName2;AttrValue2;AttrName3;AttrValue3...

In J-Field, Tags are used to draw linework, not Codes. See pages 91 - 101 in the Users Guide.
 

Symon

New Member
Sorry perhaps I wasn't clear enough, all we want to do is pick up point data with attributes and then our desktop software does the drawing hence why we need to get the attributes right in the LS. We don't want any drawing to be done in the LS.

Very helpful with the text file, that's probably what we need.
 

Matt Johnson

Well-Known Member
5PLS
Attributes are set to their default value for that code when the code is changed. There currently aren't any options to automatically open the attribute prompt when a code is changed.
 

Adam

Well-Known Member
5PLS
Use the tag function for this. When exporting the points select "parent objects" It is located under Misc if you tap the + icon in the export setup screen. This will give you a "description" of bb1, tb1, etc. You don't have to draw the lines in Jfield if you don't want, you can leave it set to collect point only.
 

Symon

New Member
Hi Adam,

So we would enter all our standard codes into the code list and if we want to "string" the TB (top of bank) code in separate portions (string 1 here, string 2 over there etc.) we would use the tag function to create the discrete strings? Does it remember the previous string (if you swap from TB to BB and then back again) or similar to attributes it won't prompt to review the tag (string) automatically?

Thanks to you and Matt both for the suggestions, as you can tell we are still feeling our way!
 

Adam

Well-Known Member
5PLS
The string is remembered when changing tags. When a line is ended and a new tag of the same name is started it goes to the next numerical string number. Currently tags of the same name can't have simultaneous lines going.
 

Symon

New Member
Apologies for being dense on this; so we create Tag of "1" with a code from our library of "TB" survey all the point we want on that string then create a new tag "1" with a code of "BB" and survey all those points and if i reselect "1" "TB" it will default to a tag "2" with code "TB"?
Thanks again!
 
Top