Points list

[John Thompson]

I have difficulty navigating the points list. I would much rather see the points list displayed as a scrollable table format like a spreadsheet.

I use SurvCE some, and I like the ability that it has to scroll up and down through a long list of points and see at a glance all of the information about all the points displayed. I can quickly resize the column widths, and I can reorder the columns to show what I'm looking for and hide information that I'm not interested in.

With the J-Field points list I can't scroll. The long list of points requires a lot of taps on the > button to navigate. It would be nice to at least be able to scroll through the pages of points by holding the > button. After several taps on the > button, if I inadvertently tap on the >> button, I lose my place and have to start over.

The T-LS has a nice big screen, but the points list does not utilize it well. There are large areas of blank space and the information is presented in a tiny font. A spreadsheet/table format would better fill the space.

But my biggest complaint about the points list is that I have tap on each point name to see any other information about that point. Only the point names are displayed, and my point names are generally not very descriptive. Often I'm looking for a point with a particular description, or maybe the last of a range of points with a particular description. I don't even see any way to filter or search by description. So I have to guess the name of the point I'm looking for (within the nine points displayed at any one time), and tap on it to see if I guessed correctly.

Maybe I'm the only one that is bothered by this, and maybe there are advantages to the current format that I'm not seeing, but I think this would be a welcome improvement. My favorite thing about this unit is that the hardware is amazingly capable and the software is continually improving.

 

[Matt Johnson]

Hi John,

With the J-Field points list I can't scroll. The long list of points requires a lot of taps on the > button to navigate. It would be nice to at least be able to scroll through the pages of points by holding the > button. After several taps on the > button, if I inadvertently tap on the >> button, I lose my place and have to start over.

This item is already on our list (VSAPP-2168).

But my biggest complaint about the points list is that I have tap on each point name to see any other information about that point.

You can use the up/down hardware buttons to change the point displayed in the blue box. Once the left/right hardware buttons are able to navigate the pages it should be pretty easy to navigate through your points.

I don't even see any way to filter or search by description.

Do you use Codes? If not, I would highly recommend you try using them as well as descriptions. They can be merged into one field when you export your points in CSV format. The points list can currently be filter by codes.

We also have it on our list to be able to customize the point information displayed in the blue box of the points screen (VSAPP-1806). It may be good to add an option for the font size of it too.

 

[John Thompson]

Matt,

Thanks for the quick reply. I would have been back on this, but I've had a pretty crazy week.

First of all, thanks for the recommendation to start using codes. I have not been using them. I have read about using them in the manual, and I keep thinking that I won't bother using them because they don't match my way of describing points in the field and manipulating points in the office. But I'm coming to realize that my objections to using both Codes in J-Field and Field-to-Finish in Carlson Survey are both unfounded. I'm finding that if I make a few small changes in the way I've been doing things, I can save myself a lot of work both in the field and in the office. So thanks for the friendly nudge to get me going. I'm excited to be trying something new.

I don't see how to merge codes and descriptions when exporting a csv. Can you post a screenshot?

Would it be possible to make the left pane of the points list show both point name and code? I think that showing both name and code would fill the blank screen space with useful information, and together with improved scrolling ability would really help navigating the list.

 

[Matt Johnson]

Use the Sep. 2 as a space to merge fields together in a csv as I have done below to merge the code, attributes and description fields:

This is very useful as the codes and attributes can be used for points descriptions that are common and then the description field can be used miscellaneous descriptions and also for storing more information about the point.

 

[John Thompson]

That's slick. Thanks!

 

[Matt Johnson]

Would it be possible to make the left pane of the points list show both point name and code? I think that showing both name and code would fill the blank screen space with useful information, and together with improved scrolling ability would really help navigating the list.

I agree that it would be beneficial to display "PointName Code Description" on the left pane of the points list. The Code would only need to be displayed if it is something other than DefCode. Does anyone else have opinions about this?

 

[Matt Johnson]

We have decided to show "PointName Code Description" on the left pane of the points list soon. Also addition point filters for descriptions and date filtering was just added and will be included with the next verizon J-Field:

 

[Andrey Zhiganov]

We have decided to show "PointName Code Description" on the left pane of the points list soon

Done. Call through Context Menu (right button) / Settings.

 

[Matt Johnson]

Done. Call through Context Menu (right button) / Settings.

Andrey, what would you think about adding one more formatting option of "PointName Code Description" without displaying the commas and not displaying the Code if it is "DefCode"? This is the format I would prefer to see.

 

[Adam]

Use the Sep. 2 as a space to merge fields together in a csv as I have done below to merge the code, attributes and description fields:

View attachment 3215

This is very useful as the codes and attributes can be used for points descriptions that are common and then the description field can be used miscellaneous descriptions and also for storing more information about the point.

How do you get the plus symbol after code? II also usse a string designator like this ea1, ea2, so on, how can I do that? Add it to the code or use 1 as the tag? I don't see an option to add the tag in the export setup?

 

[Adam]

How do you get the plus symbol after code? II also usse a string designator like this ea1, ea2, so on, how can I do that? Add it to the code or use 1 as the tag? I don't see an option to add the tag in the export setup?

I figured out how to get the +, does this mean I can keep adding fields and it will all be exported as one field?

 

[Matt Johnson]

With Sep. 2 set to Spc the delimiter is a space so it will be exported into one field and you can combine multiple fields. Tags are used for linework. The manual explains how to use them.

 

[Adam]

In the export page I have
Name
N
E
H
Code name+
Tag+
But when I look at the preview the tag isn't appended to the code. For this to work with my office software I need this.... (Code) ea + (tag)1 to look like this ea1 when exported. Am I doing something wrong?

 

[Matt Johnson]

Did you set the Sep. 2 to Spc?

These should be the default settings now that are used when a new profile is created. I would recommend using Description for the last field instead of Tag+

 

[Adam]

With Sep. 2 set to Spc the delimiter is a space so it will be exported into one field and you can combine multiple fields. Tags are used for linework. The manual explains how to use them.

I think having a delimeter option of none would solve my problem.

 

[Adam]

Did you set the Sep. 2 to Spc?

View attachment 3428

These should be the default settings now that are used when a new profile is created. I would recommend using Description for the last field instead of Tag+

I did use the description as my linework string number and this will work if I can get it with the code without a space, but I was hoping to see the linework in j field too.

 

[Shawn Billings]

Line work is 'code free' in J-Field. You build lines and curves by switching from point to line or curve in the action screen. I use Carlson f2f and have for about a decade. I like J-Field better. After creating lines in J-Field, just export the dwg file and copy it to your CAD drawing. No f2f coding needed.

 

[Adam]

Line work is 'code free' in J-Field. You build lines and curves by switching from point to line or curve in the action screen. I use Carlson f2f and have for about a decade. I like J-Field better. After creating lines in J-Field, just export the dwg file and copy it to your CAD drawing. No f2f coding needed.

Carlson's f2f is sweet, I have been using for over a decade too. I do not want to import a dxf from j field and don't really care if I see linework in j field so long as I can get a number string appended to the code. If this isn't possible I will keep on using descriptions like I have been doing.

 

[Adam]

Maybe an option would be to be able to add the string number into the code directly from the collect screen without going thru the edit code process.

 

[Matt Johnson]

How do you get the plus symbol after code? II also usse a string designator like this ea1, ea2, so on, how can I do that? Add it to the code or use 1 as the tag? I don't see an option to add the tag in the export setup?

I have never used Carlson's f2f but I think understand what you are trying to do now. What if you were to set your point names to ea1, ea2 etc.? Then you could use this export format:

Name
N
E
H
Name

If you set the point name to ea1, ea2 automatically becomes the next default point name.