SmartDrone strips a lot of modes (Stake, Progress Topo, measure/stockpile). This simplifies the dataflow. The path looks like this:

1. Start Program, login, get key (key to SmartDirt for now)
2. On the file screen you can choose a file, go to Access for a file, or select New.

Removes the Measure option on the Action Bar.

• Select New from File action bar. Begin initializing instrument like we do in SmartGrade and go to the New/Grade screen. Our initial coordinate system has to be 5000, 5000, 100 just like it is in SmartGrade. In Story 2 I will want to do the State Plane Transformation on shooting of the second benchmark/GCP.

• Create Benchmarks/GCPs for at least two points. LL is put on points. Move create benchmarks up in order to toolbar (over 3D) (First version is an arbitrary system for prototype. We really want this to transform to State Planes after the second benchmark is set.)
• Add a Set Elevation to the menu. Set Elevation will change all collected data in the file based on the offset calculated. This should use the Benchmark shot collection routine to give the best possible GPS elevation result
• The user can either use the Shoot button or streaming points button to collect other survey data when fixed (as in SmartGrade). For the shoot button point collection I'd like to actually use three point samples to calculate the point captured as I'm seeing enough variation in elevation for single shots compared to benchmarks to want a little more rigour in our point capture. With a shoot button shot I've likely bubbled up the rod and at 5-10hz taking a couple more points collected should not affect speed much if at all.
• Save on a new should use the lead text of “GCP”Dateunique number similar to what we do now using “Survey” but to distinguish the purpose of the data. It also uploads to Access. We do not need to include AGT in this situation because unless we extend the format multiple places we cannot capture the important values of lat-long which is one of the primary requirements.

Since we're getting rid of progress topo we're also removing the ability to save and close this file and then reopen it in a “New” state as we do in SmartGrade. This is ok for the use case here and if in this situation the user needs to select the saved file and go through the alignment process.

• Select the ADF file through the file screen or choose from access
• Initialize the instrument and and go to the Shoot Benchmarks or Recover screen.
• Shoot benchmarks just like we do in SmartGrade and display the deviation. Allow them to reshoot as necessary, etc. identical to what we currently do in SmartGrade.
• There is only one mode for this (no stake) so get rid of the screen that asks which mode and just go to what acts like Grade mode for this program

• Create Benchmarks/GCPs for at least two points and as needed. LL is always put on Benchmarks/GCP points regardless of whether they already had values (this is different but critical). Move create benchmarks up in order to toolbar (over 3D)

• The user can either use the Shoot button or streaming points button to collect other survey data when fixed (as in SmartGrade). For the shoot button point collection I'd like to actually use three point samples to calculate the point captured as I'm seeing enough variation in elevation for single shots compared to benchmarks to want a little more rigour in our point capture. With a shoot button shot I've likely bubbled up the rod and at 5-10hz taking a couple more points collected should not affect speed much if at all.
• Save should save to the selected file but should also save a separate file using the lead text of “GCP”Dateunique number similar to what we do now using “Survey” but to distinguish the purpose of the data. Tis file contains just the added data, not the job data as part of the base ADF. It also uploads to Access. We do not need to include AGT in this situation because unless we extend the format multiple places we cannot capture the important values of lat-long which is one of the primary requirements.

Set Elevation is different than we've previously done with monuments and correcting for elevation differences measured versus shot. The screen that shows when Set Elevation is picked is shown below:

I derived it from the Monument setting page but it has several important differences and applications. Besides being moved up in the hierarchy to a menu setting it affects the survey data past and future whereas Monument only affects future survey data.

The use case is this. When laying out GCP points for drones you often don't have a known elevation yet. You put a pin/stake in the ground and spray paint marks then shoot a GCP/BM on top of it. You do this several places and then fly the drone which only captures those points in images. As soon as you find a known elevation you want to be able to shoot it relative to the other points and then move the old points and any points shot in the future to match. I'd find grade stakes and use one to adjust and then check it against others. If I ended up find conflicting grades I'd likely want to repeat the process.

This also goes for any areas I surveyed to create registration areas for adjusting the point cloud models later.

• Space and make the Northing, Easting display at the top wider and use commas in the strings. We operate in State Planes a lot for this and that means big numbers.
• We don't have labeling other than Benchmarks and GCP creation and can't pick in this mode (should we?) so I think we can lose the line label for sure.
• We don't need to show the mode we're in since there's only grade so we can eliminate that text in the upper right.
• When using the Shoot button (not the track/streaming) button to create a survey point I'd like to take 3-5 actual shots and derive the elevation in a similar way to what we do benchmarks albeit fewer shots so it's a little faster. When shooting benchmarks and just a single shot there often can be more elevation variation than you'd think. Since the shooting aspect of this is to create registration areas that we'll use to correct point cloud models for elevation, I think it's worth sampling a little more when doing so.

We'll need to have an explicit save but I'm not interested in necessarily saving all of the existing ADF data and them the added survey data. My general thought is that we maintain the existing object database of photos, notes and tracks along the RTK information as new objects (RTK tracks and benchmarks). We keep uploading the KMZ file as we do now but when the user does an explicit save we actually create an ADF file with GCP as part of the name along with all the other RTK elements created including saved Benchmark recovery data and upload that to access.

A new file would default to GCP - Date. An existing file would default to GCP - Filename.adf

Added to that is the ability to export GCPs of the chosen format and save/share/Export them as a separate item not necessarily tied to Access. The GCP output is just the Benchmarks/GCPs shot and does not include other survey data. This format is a text file in CSV format that varies depending on the format. Typically once a user sets this value they're not going to change it so it should be remembered. For a list of the formats see here under Gory details of file types Exports http://dev.agtek.com/dokuwiki/doku.php?id=windows:export:export_revamp_2018_desktop