Advantages of Desktop

  Don't have to upload and download lots of files over sketchy connections in the field. Upload is typically slow on most connections
  Faster response on some sites
  Visibility of flight holes and mistakes
  Fast map rendering/ uploading downsampled results rather than huge files
  
Advantages of web
 Deferred processing without interaction
 Modern
 Doesn't require a fast computer/ could even be a phone or tablet
 

• Fewer choices required of user = Simpler
• Using Existing AGTEK data for feedback prior to processing or after
• Changes in order and optimization of data flow.
  • Give the user an orthomap first instead of last even if it's not as efficient.
  • Make assumptions on RTK quality for creating fast picture and uploading to SmartDirt fast
  • Selective downsampling and use of jpg for orthos for size and speed
  • Better control of GCP process/autopopulating/lining up with local coordinates
• Less vulnerable to vendor changes or miss steps
• Adjusting for elevation better than GCPs

What to charge - Subscription

Web equivalent and possible interchangability of data between sources

• New - Name here or later?

• Load Pictures - display on map/with plansheets/takeoff (what other info needed. Coverage approximation vs perimeters?

• Set Units, State Plane coordinates system from LL on picture plus user choice on units.

• Feed GCP(s) for either alignment or elevation point or Elevation Registration area/ allows non-RTK workflow

• Press Process

• Do overall quick ortho Map first for visuals, then do steps for surfaces, adjustments for reg areas

• Upload results in background or update ADF Files in background, Simplified data structure storage.

• Save project results allow for reprocessing saved to different location

1. Start Program (new or Existing flight file)
2. New - Ask for their pictures (probably at folder level only so they don't have to shift pick and make a choice)
3. Display photos over map. From Exif data figure out whether it's RTK or not, and if most are below 1 meter accuracy display as big red dots photos not meeting under that spec (float, auto, etc). Ask if they want to include them only if found.
4. Allow reading in of AGTEK files (esw, esw, adf, kmz, kml) as background files
   1. Note: if the takeoff is in local coordinates we can greatly simplify that process by using the georeferenced takeoff or ADF file for the GCP tagging necessary to move into local coordinates. This is expensive and difficult in DD (10K) and time consuming and complicated in pix 4D. By having the takeoff with two benchmarks with LL even close I have a much easier time tagging GCPs with no processing up front. The save transformation could even be used for subsequent flight to keep it close. Especially with RTK.
5. Press Go and prompt for the filename and location of saved outputs (ortho, LAS). Confirm units and auto Stateplanes here?

GCP's might be optional for RTK and especially in StatePlane but that can be an optional wizard step of tagging GCPs. It could be a written file or from benchmarks/GCP files from the background file. Show each one on the screen with the pictures we think contain the spot. Showing the dot on the map/takeoff on the same screen as the pictures to tag would give the user more feedback. Choosing checkpoints versus RTK with 3 GCP's as check, or multiple GCP's for a phantom 4 would be an option that we could lead the user down based on the Exif on the photos. You would not have to do this step.

Graphical mockup to follow. This could be so simple and the advantage of the takeoff file, especially roughly georeferenced would make locals way simpler. We could even use the LL on the two BM to have a good idea of whether the job was in State Planes or not. Most of it would be overrideable but not in the main flow.