AI Assistant
Notifications
Clear all

Leica Smartworx: adding point descriptions(?)

7 Posts
6 Users
0 Reactions
953 Views
i-ben-havin
(@i-ben-havin)
Posts: 495
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Can Leica Smartworx be set to prompt for description after each shot? Forget codes! I already understand that. However, it would be extremely helpful to be able to have the flexibility of adding detailed descriptions to points.
Thanks,
ibenhavin


 
Posted : February 5, 2015 9:14 pm
john-putnam
(@john-putnam)
Posts: 2431
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

All of our codes have a code descriptions followed by a series of attributes. For example, code 200 is a manhole. The code was created in LGO so that if I view the description for '200' then I see 'MANHOLE'. We then take it a bit further by adding attributes, some mandatory others not, the further describe said manhole. Attribute 1 is reserved for string values; Attribute 2 is used to identify the type of manhole such as sanitary, storm, unknown, etc; attribute 3 describes the shot location such as center of flow line or center of lid. Some of our codes have up to 6 attributes which sound like a lot but cuts down on the number of codes and is easier than entering extra data in a book and then transcribing it to the drawing. It is even nicer when you consider that you can create pick boxes for attributes.

When you go to export the data just choose to display the code description and various attributes in you export format.

Like I said you can I use LGO to create the code list but you can do it on the controller as well.


 
Posted : February 5, 2015 9:57 pm
Surveyor12345678
(@surveyor12345678)
Posts: 25
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Go under user, then work settings. Then prompt before storing . You can select what you want to enter before storing. Point id, antenna height, code, code information.

You might be able to hit fn under survey tab to open menu too.

If using gps hit the star key and under quality control theres a check box for auto store point. You might have to uncheck that too.


 
Posted : February 5, 2015 10:10 pm
Moe Shetty
(@moe-shetty)
Posts: 1430
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

you also might want to look into 'config sets' you could set one up for infrastructure mapping, one for day to day topography, one for the client that wants their work just so, etc. this can not only give you flexibility with codelists, it can customize your display settings on the controller.

and try to use attributes instead of annotations. attributes are much more powerful and versatile


 
Posted : February 6, 2015 6:41 am
Eric Kara
(@eric-kara)
Posts: 167
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

If this is a "viva" instrument,

Main Menu
User/Work Settings/Prompt Before storing/Check Code

B-)


 
Posted : February 6, 2015 9:15 am

i-ben-havin
(@i-ben-havin)
Posts: 495
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Thanks everyone.
(ubenhavin?)


 
Posted : February 6, 2015 3:24 pm
surveythemark
(@surveythemark)
Posts: 365
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

The issue of inputting after the measurement has been answered and two people have brought up attributes. Moe mentioned annotations which may be what you are thinking. I agree with Moe that attributes are stronger and can be structured and are basically a standard with some data flows. I want to explain the annotations that Moe brought up in his post.

Maybe you are looking for a Note kind of option. I think TDS and/or Carlson had this where you could insert a note and just start typing in as much as you wanted. Leica does have a component that can be stored with each point called Annotations. You can have 4 different annotations attached to a measurement but each annotation can only be 16 characters long. So in short you could display all the Annotation fields in your display mask and then enter as much information as the four fields can hold to document information for a point. The one drawback would be that you would need a format file to extract the Annotations in an ASCII file with your coordinates. Maybe and option... maybe not. The main purpose for Annotations in the system is to record information from say a fathometer pr other external devices that communicate with the controller while recording data.

I would also encourage you to start taking images with the CS controller and the Viva Total Station if you have an imaging TS. The images will document more information than you can store in the codes, attributes or annotations.


 
Posted : February 6, 2015 3:57 pm