Differences

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

--- android:planview:planstories [2016/07/11 22:58]
mikeclapp [Story 3]
+++ android:planview:planstories [2020/09/10 23:51] (current)
mikeclapp
@@ Line 16: / Line 16: @@
 Phones
+====== Story 7 - Extending ADF & SmartPlan for Materials ======
+Once upon a time we had a program named Materials Pilot running on the old handheld HP PDA's. The most interesting thing it did other than show you on the data (self put me here) was to allow creation of a measure area that broke down existing Materials structures by clipping them with the measure areas. It was truly a useful feature and the ability was unfortunately emphasized and sold how it should have been. We have many of the pieces of that in SmartPlan now and the release of new Materials makes this timely.
+Things likely required:
+  * Extention of the ADF file format to understand Materials Geometry, structure, and materials designations
+  * Creating an ADF writer from Materials that can write the above
+  * Reader in SmartPlan to parse the new ADF format
+  * Creation of clipping methods on structures to calculate materials quantities
+  * Reporting Interface added to SmartPlan Measure report Screen
+  * Exporting to Access of report values (KMZ or Journal)
 ====== Story 1 ======
@@ Line 151: / Line 173: @@
 ====== Story 3 ======
-Refinements and new functionality. As the IOS versions approach equivalence there are some features from IOS to integrate and reconcile the two. Also, recent field experience is pointing out refinements in the measuring and saving of areas into the KMZ upload
+Refinements, platform reconciliation and new functionality. As the IOS versions approach equivalence there are some features from IOS to integrate and reconcile the two platforms. Also, recent field experience is pointing out refinements in the measuring and saving of areas into the KMZ upload
   * The IOS version saves tracks, notes and pictures with the file rather than by session. Android should do the same and include measurement areas.
@@ Line 159: / Line 181: @@
   * Add measure areas, photos, tracks to View control with the inherent controls (selectable, hide)
   * Direction on photos? Don't know if I trust the compass to be reliable
+===== IOS Reconciliation =====
+Bringing SmartPlan to equivalence on two platforms
+==== Maintaining Added Data beyond Session ====
+The IOS version has no clear exit point to save so it forced us to develop a way to save locally to avoid losing data from a phone call. In Android we do not save until the user initiates and we do not save it to the existing file. Story 3 changes that and makes created data persist beyond the session until cleared by the user.
+Clearing would be done by long pressing on the file name on the file screen and would be another option on that popup. Alternatively we could also enable long press on view list items and allow a user to edit his local file (Note an argument against doing this is that we'd have to do it on IOS as well and that might be more difficult there.)
+==== Put me Here ====
+SmartPlan allows saving of an offset (Put me here) in both IOS and Android but the implementation is different. The Android version uses a button under the Settings-GPS tab. IOS uses a long press on the GPS compass. The IOS version is also slightly more capable in that it allows the user to remove any offset whereas the Android version require reloading of the file.
+**Android changes**
+We're going to make the Android version behave like IOS. To do a put me here the user does the following:
+  - Picks a point from the data
+  - Presses and holds on the GPS icon
+  - A prompt appears confirming the move. The pictures below include the IOS verbiage.
+  - Pressing yes applies the offset
+  - Upon the pick, press and hold, as slightly different dialog appears (IOS example below). The user can clear the offset, change the offset to relate to the new pick point, or do neither and close (no)
+{{:android:planview:file_jul_14_12_50_04_pm.png?200|}} {{:android:planview:file_jul_14_12_57_52_pm.png?200|}}
+===== Saving Measure in KMZ =====
+(IOS and Android) Measure areas are not currently stored in KMZ file that contains photos, tracks, and notes. Story three adds saved measure areas to the KMZ file. ([[https://agtek.s3.amazonaws.com/Agtek/3RJgIjCQbgUI|example KMZ link]]) Note that I have two measure areas in the example file to show the result when we add the multiple measure area capability.
+===== User Added data in View Control =====
+(IOS and Android) The view control has changed quite a bit and because it is a list style that easily added to I'd like to add the User data additions to the list. Adding them to the list also allows visibility control and deletion of individual items.
+{{:android:planview:screenshot_20160715-143652.png?200|}}
+Ted and I have made and arbitrary decision to put the user added data at the top of the list. Some things a user can do with this is:
+  * Items on the list are named identically to what the user names them
+  * Tapping Items on the list zooms to those items like any other item on the list does
+Things you can do to View list items now and future:
+  * Hide/Show - Android (checkbox) Apple (eyeball) controls visibility
+  * Find on screen - Tap on items list to zoom and show on planview.
+  * Polygons, Placemarks - Press and hold on polygons to display property sheet
+  * Overlays, polylines - Press and hold displays window to choose whether selectable, IOS uses Check for all types
+  * Delete - Swipe
+  *
+  * Edit Name - Press and hold on item on the plan screen
+  * Show Info - Press and hold on item or press the info button on the action bar
+====== Multiple Measure Areas ======
+Multiple measure areas started out as a simple extension to the single measure area we have now. It's bigger than that and working with it makes one realize there's much more to it as an authoring communication tool. It also feels like it's a mode but with much of the same interface as outside of measure mode. The new functionality means that exposing commonly used features via menu isn't optimal, some of the menu items aren't necessarily named correctly, and some functions need to be added. Here's some thoughts in no particular order:
+  * Measure areas need to be named. Sometimes a measurement is simply two points (pipe laid that day). The measure needs labeling for someone else's consumption or just as a memory hint.
+  * Requires a way to start a new area and change the area being entered/edited/viewed
+  * Do we repurpose the Tracks, Photos, Notes buttons while in measure mode? The likelihood of using those in measure is small, the screen real estate is valuable, and the change in buttons is yet another hint that the mode is different
+  * Clear may not be the correct name. It is more important if line snap is implemented because backing out hundreds of points would suck.
+{{:android:planview:smartplanmeasure-story3.png?200|}}  {{:android:planview:smartplanmeasureinfo-story3.png?200|}}
+===== Changes/New Features Measure Screen =====
+  * Below the zoom controller buttons I've removed tracks, the camera icon, and notes. In there place I've added a control for Snap and adding a new measure area.
+  * The info panel at the bottom has become a swipe up panel. When swiped up, the user can edit the measure name and add notes that appear as Info/ GE property sheets when exported or viewed outside of measure.
+  * On the info bar I've shortened the descriptors to L: and A: and removed the . from the end of ft to allow more room on the phone and also allow for a right arrow similar to SmartTrack. Pressing this arrow cycles between measure areas. It should not appear until there is more than one measure area.
+==== New Measure Use Case ====
+The dirt foreman at the end of the day wants to estimate how many yards are left in a section of pads. He opens the KMZ file and selects measure. He taps in an area surrounding the pads, sometimes toggling snap on/off as he follows the edge. The length and area accumulates at the bottom. Satisfied he swipes up and the default measure name is highlighted along with displaying the keyboard. He replaces the default name with "Pads 35-55" and then taps below to enter his notes. "4 - 637 scrapers had a load count of 184. Est 3420 cy moved to Pad 74-87". Then he swipes the screen down to minimize that display. Next he walks to the end of concrete ditch being demoed and hauled off. He taps new measure and puts a point on the arrow where he's standing. He then walks to the end of the demolished ditch and taps another point to generate a length. Again he swipes up and gives the measure a name of "Ditch removal" Tapping below he adds "Removed and hauled concrete to grinder the above lf of ditch". He then taps exit measure and returns to the main smartplan screen. The measure areas he entered display both on screen and in the list view. He picks each and taps info to make sure his notes are present and then presses save to send the results back to the office.
+====== Changes to Save =======
+The persistence of user data change also has implications for save. Are we content to just save the additions without the other KMZ data or sometimes do we wish to have a composite of all the data (original file + additions) saved. I think need both. The default behavior is to just save the additions and upload. An checkbox to save and upload the entire file should be added to the save dialog (how do we do this in IOS?)(Discuss with Ted for his opinion)
@@ Line 164: / Line 284: @@
 ====== Story 4 ======
+Add to note taking ability a default list of notes that can be selected rather than typing.
+**Use Story**
+The foreman is at the end of the day and documenting the work accomplished. He circles an area of pads where clay was found and excavated to be remixed with other materials. He knows the scrapers spent 3 hours removing it and did 38 loads.
+He goes into Measure and circles the pad area. He then opens up the notes and taps the Note List with the focus in the title and chooses "#23064 Clay Removal". This text is inserted as the title (but could just as easily be put in the notes section). He then puts in "3 Hours, 2 637's, 38 Loads at 24 cy per load" and saves the note. After doing more documentation and adding cost codes he saves the file and uploads it to AGTEK Access where the project manager, project engineer, and area superintendent can review his notes and graphics in Google Earth.
+**Other extensions**
+You could also see where we might want to be able to share these notes other than a KMZ.
+**Support Functionality**
+On the surface the interface for this is simple but it implies a support structure to edit/choose/make/download these lists. Access seems to be a natural choice as the download mechanism since we have interfaces written. The challenge is that lists are a global element for the country instead of being project specific. We'd like to have multiple lists available as well (implies a file extension?)
+Do we add a list management utility page under Preferences?
 Volumes returned from Lambda server against 3D ADF file based on kmz measurement area.
@@ Line 173: / Line 320: @@
-====== Story 4 ======
+====== Story 5 ======

AGTEK R & D Wiki

User Tools

Site Tools

Differences

Page Tools