John Thompson
Well-Known Member
CoGo > Stakes > Divide Line
I like this feature and used it a bunch today, and there are a few tweaks that I think would make it more useful.
1. "Points, n" defaults to 2, but it should default to 1. I almost always use this feature to calculate the midpoint between two points, but I don't think I've ever used it to divide a line into thirds. Personally, I think it would be more intuitive to specify the number of segments instead of the number of points, but most of the time I can do that much math in my head. So maybe default to two segments instead of two points.
2. It would be nice if I could specify "Points, n" and the resulting segment length would be displayed. Similarly, if I specify Segment Length to have "Points, n" displayed. (Or segment length and number of segments)
3. The Code of the resulting point(s) should be DefCode. It might be nice to be able to specify the Code, but DefCode is most likely fine. Currently, the points are created with the code of the last saved point. I'm unlikely to want a calculated design point to have the same code as any point I just surveyed.
4. A single-proportion tool would be super handy. If I could enter the record distance between P1 and P2 and the record segment length and number of equal segments, that would be awesome.
5. After I press Create (+) and the popup (which isn't necessary) shows the created points, the Create (+) button ought to be disabled until I make any changes to P1, P2, Segment Length, etc. Otherwise if I press it again, it creates a duplicate set of points with the same coordinates.
6. Better yet, after I press the "Create+" button, it could be replaced with a "Stake" button that stakes all of the resulting points from nearest to farthest, which is always what I want to do next.
I like this feature and used it a bunch today, and there are a few tweaks that I think would make it more useful.
1. "Points, n" defaults to 2, but it should default to 1. I almost always use this feature to calculate the midpoint between two points, but I don't think I've ever used it to divide a line into thirds. Personally, I think it would be more intuitive to specify the number of segments instead of the number of points, but most of the time I can do that much math in my head. So maybe default to two segments instead of two points.
2. It would be nice if I could specify "Points, n" and the resulting segment length would be displayed. Similarly, if I specify Segment Length to have "Points, n" displayed. (Or segment length and number of segments)
3. The Code of the resulting point(s) should be DefCode. It might be nice to be able to specify the Code, but DefCode is most likely fine. Currently, the points are created with the code of the last saved point. I'm unlikely to want a calculated design point to have the same code as any point I just surveyed.
4. A single-proportion tool would be super handy. If I could enter the record distance between P1 and P2 and the record segment length and number of equal segments, that would be awesome.
5. After I press Create (+) and the popup (which isn't necessary) shows the created points, the Create (+) button ought to be disabled until I make any changes to P1, P2, Segment Length, etc. Otherwise if I press it again, it creates a duplicate set of points with the same coordinates.
6. Better yet, after I press the "Create+" button, it could be replaced with a "Stake" button that stakes all of the resulting points from nearest to farthest, which is always what I want to do next.