Page focus discussion

[David M. Simolo]

I am quite the newbie with my Triumph-LS and J-Field so bear with me if I get some of this wrong. My inherent terminology may not jive with the terms used by J-field. J-Field also has a lot of point features that are much more complex than what I am used to. The whole notion of 5 different coordinates for a single point name is not something I have tried to come to grips with yet, either.

Quite often my workflow involves looking for points based upon pre-calculated locations and then locating them upon finding them. I tend to put various islands of pre-calculated points on their own page.

When I am collecting field data I am trying to keep this all on a single page.

When I go in Stakeout mode I need to select the page that contains the point that I am looking for and begin my search.

Upon returning to Collect mode J-Field stays in the same page as the previous stakeout query.

Perhaps this makes perfect sense for the way J-Field is set up and how others work. In my mind it would be better if J-Field retained the page focus of Collect independently of the page focus for Stakeout and vice versa.

I am interested to see what others think about this or other workflows that seem to be useful.

I do want to say that I am very impressed with my new purchase.

Thanks.

Dave.

 

[Matt Johnson]

Hi Dave, you can select a point to be staked regardless of rather or not it is contained in the current page. The page it is in just needs to be visible. New points and lines will be be created in the current page so if you use the Accept As whitebox to store a new point from the Stake screen, it will be created in the current page.

 

[David M. Simolo]

Hi Matt,
Thanks for the input. You're throwing some things out there that are obviously different than what I've been doing. I will try to see how that works for me.
Dave.

 

[Nate The Surveyor]

Ahhh so that explains some things. I could not figure out how come my field shots, were winding up on the same page, as my staked points.
I was not bad worried about it, because it exported the field shots just fine.
But, I don't have this pages thing figured out either.

Thanks Dave, for asking that.

And, Matt, I'm going to try that. Thanks.
N

 

[Sean Joyce]

I have noticed when doing a localization that points and pages are cumbersome also.
In one column you pick design points and in the other column you pick a corresponding surveyed point.
The way I work and think I typically pick the design point and then jump to the surveyed column to pick the corresponding point.
This required me to jump out of localization and reset the page to survey (page 0) every time which is a PIA.
I tried setting both pages to be visible but that didn't seem to work.
My current workaround is choose all the design points first (which I don't necessarily like to do) then jump out and switch pages to page 0 (Survey), go back to localization and pick the corresponding points in the survey column.
Pairing up the wrong points is more of a possibility doing it this way.
If I am missing something please let me know.

 

[Matt Johnson]

This required me to jump out of localization and reset the page to survey (page 0) every time which is a PIA.

The

(filter) button allows you to change pages inside the points list screen, no need to exit localization.

It does appear that some issues need to be fixed when pages with both unknown coordinate systems and known coordinate systems are visible. Here when I make a page with an unknown coordinate system the current page and select a surveyed point with known coordinates, it list the coordinate system as unknown in the select points screen:

I find that this does not cause problems when I add this point on the surveyed side of the localization screen however. For the Design side, I think we should filter the points list to only points contained in the set unknown coordinate system.

 

[Sean Joyce]

Thanks Matt, I haven't used filters much, I will play around with it.
Is it possible to have a global setting in project setup assigning the coordinate system and page we want all our surveyed points to reside in? This might save some keystrokes.
When a routine needs to reference and or display a surveyed point or create one it would always reference the proper assigned page and coordinate system without using filters?
I try to put all my surveyed points to display in state plane/geodetic on page 0.
It is a way I can standardize my survey procedures and be consistent.
There are times when I forget to change to page 0 jumping between stakeout/search and measuring the found points.
I end up having some surveyed points displaying in a local system because I was in that page and others in state plane on the same job. (before export)
I realize that upon export it all comes out in the wash and I am only referencing being able to standardize data handling and display while performing the survey.
any thoughts on this?

 

[Matt Johnson]

Coordinates are always displayed using the coordinate system of the current page on the map and in the CoGo functions. There currently isn't a way to default surveyed points to be on a default page. You could add the Page whitebox option to the Collect Action screen so you can check that you have the correct page selected while surveying points.

 

[Nate The Surveyor]

I had thought of making a "Points Dashboard". Where, you set your job up. Field shots begin at point 1, Field calc points begin at point 301, And, ALL field calc points go on Page X, and ALL field shot points go on Page X. Of course, you can override this, BUT there is a place to set up the defaults. It is also here, that you set up the prefixes, suffixes, of alphanumeric points. And, you can NOT allow Alphanumeric also, if you want. It is a basic points control screen, so that you are NOT making decisions, while in the woods, unless, you want to. I personally, think this would solve alot of these issues.

Please keep in mind, with ALL my postings, that I am a FIELD SURVEYOR, I have little concept if I am asking for a little, or a lot.
Nate

 

[Adam]

I had thought of making a "Points Dashboard". Where, you set your job up. Field shots begin at point 1, Field calc points begin at point 301, And, ALL field calc points go on Page X, and ALL field shot points go on Page X. Of course, you can override this, BUT there is a place to set up the defaults. It is also here, that you set up the prefixes, suffixes, of alphanumeric points. And, you can NOT allow Alphanumeric also, if you want. It is a basic points control screen, so that you are NOT making decisions, while in the woods, unless, you want to. I personally, think this would solve alot of these issues.

Please keep in mind, with ALL my postings, that I am a FIELD SURVEYOR, I have little concept if I am asking for a little, or a lot.
Nate

This is something I recommended on another thread. I think it is essential to have points and pages working together to organize our data so we don't have to. Just set it up and there it is. No looking for points while in the field.

 

[Matt Johnson]

Field shots begin at point 1, Field calc points begin at point 301

This has been done, wait for the next version. The default point name has been divided so that it is different for CoGo points and Survey points. The developers are very hesitant about having multiple current pages for different types of points though because it can lead to a lot of bugs.

 

[Nate The Surveyor]

It would not be "Multiple current pages", (would it???) From the dashboard, it has simple instructions to send particular types of shots, to particular pages. The Dashboard is the controller, of where they go. Anybody else see the utility of this?

 

[David M. Simolo]

To me it seems like a good way to keep things organized in the right place. It seems to model my way of doing things pre-LS.

 

[Nate The Surveyor]

If we build the "Points Dashboard", and it ONLY does the configuration, for points, design points begin incrementing at point XXX and survey shots begin incrementing at point xxx, we can add things later, such as what page each item goes on, and the like, but for now, that would be quite useful.