special characters in descriptions

avoidthelloyd

Active Member
I’m old school and still use point descriptions instead of tags. fd3/8ipc and fd1/2ip etc are regulars. I wish the point description field didn’t split the description into separate descriptions in the recall function.

For instance when I describe a point shot as “fd3/8ipc”, the next time I find and shoot one I have retype it all again because the slash causes the description to be split into “fd3” and “8ipc”.

Can we get the descriptions field to just treat all characters as text?
 

nusouthsc

Member
At first I quit using spaces and symbols for that reason. But we have recently went to using codes. It really was simpler than I thought. It took maybe 30 min of typing in codes and the consistency is very nice. Plus you can add a description in addition to the code. I would be glad to share my rather simple setup if your interested. I’ve been using codes for about a month now and I prefer them.
 

Andrey Zhiganov

Active Member
5PLS
I’m old school and still use point descriptions instead of tags. fd3/8ipc and fd1/2ip etc are regulars. I wish the point description field didn’t split the description into separate descriptions in the recall function.

For instance when I describe a point shot as “fd3/8ipc”, the next time I find and shoot one I have retype it all again because the slash causes the description to be split into “fd3” and “8ipc”.

Can we get the descriptions field to just treat all characters as text?
Looks like a bug but I can not reproduce it. Could you describe your workflow step by step. Also, please, send the project to support.


1-PREPARE-COLLECT_20211022-05.27.11.pngCOLLECT-GNSS_20211022-05.28.07.pngEXPLORER-OBJECTS_20211022-05.26.37.pngEXPLORER-OBJECTS_20211022-05.26.46.png
 

Eric Tweet

Active Member
Andrey,

I believe they're referring to the typical way that typing in, and quick-selecting previously typed descriptions is handled. (see screenshots)

Like:
1. Type in the first description for the first point.
2. For another point, begin to enter the same description, but only a portion of that text is seen in the "quick recall" row.

Apparently some characters (such as "/") are considered delimiters similar to how a space is handled, making only portions of a line of text recallable with a single click.

There are some days when I agree that it would be handy to recall a full description, including slashes and spaces, but other days when I'm happy to have them separated. I'm still getting used to Tags+Codes+Descriptions, but there's a lot of potential for quick and easy identifiers using those.

For example, when I get ready to blast through a topo, I have a Tag "EG" which populates the code "EG" as well, and begins point numbering with Z001 so I know all my Z point names are existing ground shots, making processing nice and efficient. Then when I switch to some other feature measurement, and back to the "EG" tag, all my ground shots continue right where they left off.
 

Attachments

  • 1.png
    1.png
    23.2 KB · Views: 35
  • 2.png
    2.png
    20.8 KB · Views: 33
  • 3.png
    3.png
    176.7 KB · Views: 30
  • 4.png
    4.png
    23.4 KB · Views: 33
  • 5.png
    5.png
    23.9 KB · Views: 32
  • 6.png
    6.png
    22.9 KB · Views: 33

avoidthelloyd

Active Member
At first I quit using spaces and symbols for that reason. But we have recently went to using codes. It really was simpler than I thought. It took maybe 30 min of typing in codes and the consistency is very nice. Plus you can add a description in addition to the code. I would be glad to share my rather simple setup if your interested. I’ve been using codes for about a month now and I prefer them.
Sure! I'm not opposed to the change and had a good class over it recently, but being overwhelmed with other areas of work has just deterred the change over.
 

Matthew D. Sibole

Well-Known Member
5PLS
I don’t use tags either. I build codes for the descriptions I use most. I then in the description field put any additional info that I need like “12 inches deep”.
 

avoidthelloyd

Active Member
If the description field would ignore the special characters and treat it all as text, my workflow would be fine with just using the descriptions and not codes. I rarely would have to type more than 3 characters before my previously used description pops up. It works as is now... it would just be a convenience. I lengthen my descriptions when needed to '12"deep' or whatever. I have my own abbreviations to help shorten things. I like to see it all in CAD.
 

avoidthelloyd

Active Member
Andrey,

I believe they're referring to the typical way that typing in, and quick-selecting previously typed descriptions is handled. (see screenshots)

Like:
1. Type in the first description for the first point.
2. For another point, begin to enter the same description, but only a portion of that text is seen in the "quick recall" row.

Apparently some characters (such as "/") are considered delimiters similar to how a space is handled, making only portions of a line of text recallable with a single click.

There are some days when I agree that it would be handy to recall a full description, including slashes and spaces, but other days when I'm happy to have them separated. I'm still getting used to Tags+Codes+Descriptions, but there's a lot of potential for quick and easy identifiers using those.

For example, when I get ready to blast through a topo, I have a Tag "EG" which populates the code "EG" as well, and begins point numbering with Z001 so I know all my Z point names are existing ground shots, making processing nice and efficient. Then when I switch to some other feature measurement, and back to the "EG" tag, all my ground shots continue right where they left off.
Thanks for the explanation! Better than I would have!:)
 
Top