Differences

This shows you the differences between two versions of the page.

--- android:smartgrade:smartgrade_rtk_grade_only [2014/07/23 01:10]
mikeclapp [Add Points function in Staking]
+++ android:smartgrade:smartgrade_rtk_grade_only [2015/03/27 22:26] (current)
mikeclapp [Story 10 (Version 1.6)]
@@ Line 338: / Line 338: @@
   * Add Section Offset functionality via menu
-  * Add Points function in Staking
+  * Add Points on line function in Staking
   * Add Image background toggle to menu (like SmartTrack)
   * Add Point Deletion/Labeling to Grade mode survey points
@@ Line 353: / Line 353: @@
 The new order should be this:
-  * Unordered List Item
+  - Break Line
+  - 3D
+  - Save
+  - Undo
+  - Section Offset
+  - Show Plans Sheets/Show Cut/Fill
+  - Create Benchmark
+  - Labels
+  - File
+  - View
+  - Progress Topo
+  - Stake Mode
+  - Settings
 **Stake**
+    - 3D
+    - Save
+    - Show Plan Sheets
+    - Undo
+    - Points along Line
+    - Labels
+    - Create Benchmark
+    - Grade Mode
+    - File
+    - View
+    - Settings
@@ Line 394: / Line 414: @@
-==== Add at interval =====
- ==== Individual points ====
+{{:android:smartgrade:points_on_line.png?300|}}
+===== Support for Stake List Points =====
+Earthwork 4D supports entry of Stake List points. The primary use of Stake list points is to make staking more regimented and less prone to an error in selecting the correct point to stake. It's often used when the actual survey user is inexperienced and the file preparer wants to make sure the user stakes the correct point.
+I don't think we currently do anything with stake list points when writing an ADF. We need to extend the ADF format to support stake list points as a unique entity. You can get an example of an esw with stake list points here: [[https://agtek.s3.amazonaws.com/Agtek/mLWeGsJbssLU]]. The AGTEK building in this file has a stake list point on each corner.
+ ==== Stake List points in SmartGrade ====
+Stake List points in SmartGrade are enabled by an option under View-Other ("Select Stake List Points Only"). When on, Stake mode only allows selection of Stake List points and no other. I do not wish to make the setting persistent past the session because I can see it causing support issues. What I would like to do is when switching to Stake mode, the program checks to see if Stake List points exist. If they exist, ask the user. "This file contains a Stake List. Do you wish to stake only the Stake list points?". Saying Yes flips on the setting, Saying No keeps it off.
 ===== Add Image background toggle to menu (like SmartTrack) =====
 ===== Add Point Deletion/Labeling to Grade mode survey points =====
+We have not previously allowed survey points to be deleted or labeled except for the Undo feature in any AGTEK RTK product. We're going to do it here and here's how it will work.
+ *  The Undo button/menu item is renamed to "Remove Last"
+ *  In Grade mode we do not currently allow anything to be selected but we will now.
+     * If a point is selected the Undo/Rename Last button changes to "Remove" and selecting it deletes that selected point. (Connectivity remains).
+     * The selected point can have its label changed by selecting the top (label bar) or choosing Label from the menu.
+     * The Break Line function can also be used to break a line at that at that point. Using this feature on a selected point does ask for confirmation that the user wants to break the survey line.
  ==== Connectivity after a point is deleted ====
-  * Add Camera support (Similar to SmartPlan/SmartDirt)
+After deletion of the point we should not break the line. A typical usage is to remove a single errant point. In this case, after deletion, connect the points on either side.
+==== Camera Support ====
-There is no pick for grade mode but there's no reason we couldn't pick survey points for deletion, labels, etc.
+  * Add Camera support (Similar to SmartPlan/SmartDirt)
@@ Line 410: / Line 453: @@
 ====== Story 9 (Version 1.5) ======
+  * Change upper and lower information bars (labels, NE upper, Layer, grades, c/f) to device independent layouts. The goal is to increase the size of the information on high resolution tablets. After converting to DI layouts we may still need to increase sizes. We also should evaluate all of the layouts for use with tablets since that's what we're selling on.
+  * Add Photos to stockpile? Suggestion from T. Emrich via tracker SmartGrade-464.
+  * Support the Javad Triumph 2 base/rover configuration
+==== Tablet/HiRes Layout Changes =====
+Here are the screens that could use improved layouts so far:
+    - File Screen (landscape) - Use the new vertical split layout.
+  -   Stake, Grade, Stockpile, Progress Topo, Alignment, New Survey (just about all working screens) need to increase the size of the top and bottom info bars at high resolution. Start by using device independent pixels but I suspect we may have to go bigger still.
+  -   The benchmark, pick, and base station glyphs are too small on the 2560 res screens. I think they are DI now but we should check.
+  -   The view screen could probably have an optimized layout in both Portrait and Landscape. Need to think of what would look better and I'm open to suggestions. Maybe a slider from the left that doesn't cover the entire screen so we could actually see the changes as we tapped like we do in SmartPlan. It would both be more consistent across the mobile line.
+  -   Should we do something similar with Settings?
+  - The Label window is out of proportion on the higher res screens. The labeling section needs to be shrunken down vertically to show more of the plan area. This especially bad in Landscape and will be only worse when we expand the bottom and top info bars. It's just kind of ugly.
+All this needs to also be viewed against the prism of putting out a 1.5 version with the recovery fixes for alignment compatibility with the old desktop software. My proposal for now is to do 1, 2, 3 and 5 and evaluate the effort on View and Settings.
+=== Label Window Changes ===
+Increasing the text size of the information panels made an already awkward layout for Labeling pretty much unusable so we need to address it. In the course of using the labeling I also discovered that it doesn't quite work right either and has two different interfaces depending on how it was picked. It's time for a rework.
+**Phone Layout**
+I'm doing the phone layout first because it's the most sensitive to the size changes made. Here's examples of the new layout. Forgive the graphical issues on the screens like R+0.00 appearing twice.
+{{:android:smartgrade:labelsportraitphone.png?200|}} {{:android:smartgrade:labelslandscapephone.png?400|}}
+**Tablet Layout**
+The tablet layout doesn't substantially change from the phone. It simply has slightly more room.
+{{:android:smartgrade:labelsportraittablet.png?200|}} {{:android:smartgrade:labelslandscapetablet.png?400|}}
+**Use Scenarios**
+**Labeling a point ahead of shooting it**.
+  * Tap the Label are of the top info bar or select Label from the menu.
+  * Type in the new label. Focus should start on Label field. If the label is a common one the user could either add it (+ button) to the list permanently or pick it from the list rather than typing it in. The list is strictly a fast way to label without the keyboard.
+  * Press the shoot button to take the shot with the assigned label. If Shoot is pressed again the subsequent shot also uses that label. To stop labeling shots the user needs to select "<no label>".
+  * The label window can be closed at any time by tapping the Labels menu command or tapping the top label info bar. Labeling points with the last label picked continues even with the label window closed.
+**Labeling or editing a point after shooting it**
+This wasn't a part of the earliest labeling methods but was added for version 1.4. That said it doesn't follow the same pattern in its current implementation.
+  * Pick any survey point on the screen. We should display any label this point has on the otp
+Label List usage
+Editing the Label List
+Press and hold displays label name - Choice of Edit or Delete. This is as currently implemented.
+Editing the label of an existing shot
+  Pick shot
+==== Story 9.1 ====
+  *Drivers and bug fixes. Expect the Hiper SR and the Cell using phone interfaces here too.
+====== Story 10 (Version 1.6) ======
+  * Expanded ADF data support (Pipelines, etc)
+  * Saving 3D view calculation to ADF similar to IsoPach for speed optimization
+  * Reviewing and making another attempt at saving the IsoPach in windows prior to uploading.
+  * Allow pushing of File to SmartBlade Machine Control? Substituting for a small portion of what Job Site Manager does? What are the implications for user getting update?
+Note: Some of these things are obviously part of ADF Writer and may only have minimal changes int hte
+====== Story 11 (Version 1.7) ======
   * Add Template labeling scheme
@@ Line 415: / Line 549: @@
-There is no pick for grade mode but there's no reason we couldn't pick survey points for deletion, labels, etc.
-Do we even show the labels at the top if the user hasn't set them?
-We can use Lat/Long positioning relative to benchmarks before we actually align. Once we shoot the first point we'll still use it for rotation but not position. This may make it easier to actually find field benchmarks during the initial setup. Benchmarks shot in should not overwrite the lats/longs on the benchmarks if present on any two benchmarks in the file. The Google Earth benchmarks are often much better than the ones established by the base. Since we really only use the Lat/long in Benchmarks for GE, matching it is more important.
 **3D Staking** - it appears like it should work with the quality we now have in 3D. The toughest part is probably picking in a 3D view but it would also serve as a confirmation besides labels that you have the correct point picked.

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools