Pages

[Wes Cole]

Pages is a nice feature in J-Field. It's new to me so I have a few questions on how it functions.

Is it possible to change a point from say Page 1 to Page 0? A scenario: the other day I was staking a calculated point. I found the point then began to collect and store an observation. It stored it on the Deed page (Page 1 originally ) instead of Survey page (page 0 originally ). In this instance I wanted to move it back to Survey Page.

Are you able to move or rotate points by anything other than page? I'll compute points as C1, C2, etc in the office and upload. Then as I find and survey I want to move certain point ranges to my surveyed positons. Maybe it's not all of the C points or an entire page of points. Possible?

 

[Matt Johnson]

Yes points can be moved to different pages from the Edit screen for Points or with the Multi-Select actions option for multiple points.

The CoGo Rotate and Move functions work with any selection of points. The only restriction would be if they still have an Unknown coordinate system. You can use the name filter and then the select all option to select a range of points. For example C10..C20 would filter the displayed points to the range of C10 - C20.

 

[Wes Cole]

Great information Matt...thanks!

 

[Nate The Surveyor]

I often set page 0 as spc. Set Page 1 as a local, @ 95 ppm, and then I want to set page 0 current. And, simply stake sfuff on page 1. Inevitably what winds up happening, is some is on page 0, and some is on page 1. It changes my current page for me.
Is there a way to LOCK the pages, so it does not inadvertently make a change for me. Thanks.

N

 

[Matt Johnson]

I often set page 0 as spc. Set Page 1 as a local, @ 95 ppm, and then I want to set page 0 current. And, simply stake sfuff on page 1. Inevitably what winds up happening, is some is on page 0, and some is on page 1. It changes my current page for me.
Is there a way to LOCK the pages, so it does not inadvertently make a change for me. Thanks.

N

Points are always created on the current page and J-Field should never changes the current page on its own. It must be changed by the user. Are you able to reproduce some action that causes the current page to change inadvertently? I am not aware of any that do.

 

[Nate The Surveyor]

Yes. When you reset the filters. Then, proceed to stake a point on the page, that you were not previously on. It has happened to me over 10x... to be perfectly honest, I did not watch it do it, so I don't know and the EXACT junction it did it, but you know how it goes... in the woods, you find it on the page you did not want to have set current. Thanks for asking.
N

 

[Matt Johnson]

Ok I see that "Select Point" in the Stake Prepare screen changes the current page to the page of the selected point. I'll see if Mikhail can change this so that it does not cause the current page to be changed.

 

[Nate The Surveyor]

In considering it,

In stakeout, I do not often use the GREEN button "Accept" in the stake screen, except by accident. So, this is why it sets that screen current... because it expects us to hit the green button... which I avoid, and only hit by accident.... When hitting the green button, it stores the coord as a component of the point being staked....
I use exclusively the "Accept As" button. Except when accidents occur!

 

[Mikhail Drakin]

Nate, stakeout always traverses points on current page (except in From Map and Sekect Points to Stake modes). So if you select a point to stake from another page, next point will still be taken from current page (Page 0 in your case). I can implement explicit selection of page used for stake traversing (so that you choose current page to be Page 0, then either select a point from Page 1 or explicitly select Page 1 for traversing stake points). The flip side of this would be necessity to always select stake page in addition to current page, which is in my option a rather significant behavior change. I don't mind implementing this, but would like to see more opinions and, probably, better suggestions on what to do instead of "Use all points on current page" (currently called "Use All Points On Page" without specifying on which page).

 

[Shawn Billings]

What about adding page selection to the point details after accept as? Then the user can manually set the point to go into a different page from the target point. I understand why j-field changes pages and largely I think this is proper behavior, but I also often desire to store my accept as position in a different page.

 

[Matt Johnson]

I don't feel that the "Use all points on current page" setting is that useful or necessary. I'd prefer it be changed to "Stake All Visible Points". This mode would use all the points visible in the Points screen (accounting for current the filters) for the points to be staked with the traverse modes. Staking a point on a page other than the current page would not change current page and Accept As would save the points on the current page. As Shawn suggest, adding a setting in Accept As for the page would be good too.

 

[Joe Paulin]

Good idea Shawn, I think this would solve the issue. I also see the need to store the accept as point on a different page.

 

[Mikhail Drakin]

Ok for adding destination page to Accept As settings, but I still doubt that always using current Points List filter is very good idea - points screen is used for many things, and it could be tricky to remember that some filter settings have changed. For this we have "Select Points to Stake" option. Probably this should be made the only option, with some additional buttons to "Add to list all current page points" and/or "Add to list all currently visible points"? And make points list always explicitly edited (except in From Map mode)?

 

[Matt Johnson]

The other idea I had was for an "All Visible Pages" option along with the current "Select Points to Stake" option. "All Visible Pages" would use all the points in pages that are currently visible. I don't think we should force users to have to select a list of points with "Select Points to Stake" when they want to stake points.

 

[Nate The Surveyor]

This is where I got my "Points Dashboard" idea. Just a place, to set up points behavior. I have no idea how hard to implement it would be... but it would allow you to set it all up, while not trying to perform a survey. This would simplify things, from a field user point of view. That is, things behave as expected.

 

[Mikhail Drakin]

Matt, "All Visible Pages" will again require hiding all other data, while I can easuily imagine some imported linework been used as a background map while staking (note that imported points, unlike line vertices, currently are in all aspects the same as stake points and cannot be distinguished in a way other than by page or code).

Nate, I like the Points Dashboard idea in general, but it is somewhat global to implement. Currently we need to agree on a more local change, keeping the big idea in mind for further work.

It is rather easy to implement "All Visible Pages", but I'd still like to get more votes to know that this has kind of majority support.

 

[Adam]

Matt, "All Visible Pages" will again require hiding all other data, while I can easuily imagine some imported linework been used as a background map while staking (note that imported points, unlike line vertices, currently are in all aspects the same as stake points and cannot be distinguished in a way other than by page or code).

Nate, I like the Points Dashboard idea in general, but it is somewhat global to implement. Currently we need to agree on a more local change, keeping the big idea in mind for further work.

It is rather easy to implement "All Visible Pages", but I'd still like to get more votes to know that this has kind of majority support.

I support the All Visible Pages solution Mikhail.

 

[Nate The Surveyor]

Mikhail, I'm not approaching this from the point of view of what works for you... But what works for me! I do not intend any rudeness at all.

What I'm asking for is probably in the category of "Big Re-write" so, I will do my best to learn what is... and go from there.

But, I do think for pure simplicity to the end user, in the long term, there is value in the Dashboard Concept.

Thanks for your response.



Nate

 

[Mikhail Drakin]

Nate, no offense meant at all! As I said, I like your idea with the dashboard, but it requires significant time to think out thoroughly and implement, and the problem we have now, as I see, is kind of urgent and should be agreed upon and solved fast enough. Do not stop sharing your ideas and suggestions, as even when they are difficult to implement, they may provide valuable hints for us and for the 5PLS team.

 

[Mikhail Drakin]

Starting from dev. build .596, Page is not switched when selecting points; traverse works over all visible pages; Accept As allows selecting destination page (in this latter case, current page will be switched though).