android:smartdronertk:android_project_stories
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
android:smartdronertk:android_project_stories [2019/03/08 00:21] mikeclapp [Changes] |
android:smartdronertk:android_project_stories [2019/05/10 17:12] (current) mikeclapp [Changes from SmartGrade] |
||
|---|---|---|---|
| Line 82: | Line 82: | ||
| * 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. | * 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. | * 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. | ||
| + | |||
| + | |||
| + | |||
| + | ==== Save Dialog ==== | ||
| + | |||
| + | 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|http://dev.agtek.com/dokuwiki/doku.php?id=windows:export:export_revamp_2018_desktop]] | ||
| + | |||
| + | |||
| + | {{:ios_smartdirt_rtk:sdrtksavescreen.png?400|}} | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
android/smartdronertk/android_project_stories.1552004465.txt.gz ยท Last modified: 2019/03/08 00:21 by mikeclapp
Page Tools
