This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
windows:xaml_nextgen_framework [2019/12/04 16:49] mikeclapp [Cloud Services] |
windows:xaml_nextgen_framework [2020/06/02 21:21] (current) mikeclapp [Controls needed] |
||
---|---|---|---|
Line 17: | Line 17: | ||
===== General thoughts on Interface and Workflow ===== | ===== General thoughts on Interface and Workflow ===== | ||
- | * Projects on maps (street, satellite, 3d for conx). Use opening screen as navigation tool, creation of projects | + | * Heavier emphasis of projects on maps (street, satellite, 3d for conx). Use opening screen as navigation tool, creation of projects |
* Using module icons as filters (should we highlight projects that have mobile data versus those that don't) | * Using module icons as filters (should we highlight projects that have mobile data versus those that don't) | ||
* Color schemes differing from ConX for branding. For example blue interface highlights instead of red | * Color schemes differing from ConX for branding. For example blue interface highlights instead of red | ||
+ | |||
+ | |||
+ | ==== Starting Screen Project Page ==== | ||
+ | |||
+ | In my mind the initial screen is the map view of projects. We should be state aware so a user who sets preferences has those saved so they can customize what they deem important and optimize their workflow. The ConX approach may be a 3D view | ||
+ | |||
+ | |||
+ | {{:windows:2020agtek_framework_rev_for_adf-uav_projects.png?800|}} | ||
+ | |||
+ | The expectation here is that all of the active projects are shown on the map which can also be a satellite view. | ||
+ | |||
+ | |||
+ | The Project page is the hub with the intention of showing all projects and key information that can be customized by user intent and the products they might have. Since part of the intention is to diversify our product line and appeal across many niches we must allow customization of the view | ||
+ | |||
+ | |||
+ | ==== Controls needed ===== | ||
+ | |||
+ | * New Project | ||
+ | * Rename | ||
+ | * Delete | ||
+ | * Settings - project boundaries, sharing, default projects, archived/inactive | ||
+ | * Sort/Filter - The order to show projects (Alpha, activity, direction) and filters (archived, georeferenced only.) | ||
+ | |||
+ | |||
+ | {{:windows:2020agtek_framework_rev_for_adf-uav_new_project_help.png?800|}} | ||
+ | |||
+ | |||
+ | From the overall screen we can go to a zoomed in view and display details like line overlays (KMZ style) pictures, mobile user tracks and notes. It also serves as a launching point to apps with files contained in the that project. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
Line 30: | Line 67: | ||
| | ||
| | ||
- | ==== ADF Creation ==== | + | ==== ADF Creation Module ==== |
Probably need a snappier name, requires expansion of ADF to have KMZ attributes | Probably need a snappier name, requires expansion of ADF to have KMZ attributes | ||
+ | |||
+ | |||
+ | Story Here: [[windows:ADF Creation Module]] | ||
==== Photogrammetry ==== | ==== Photogrammetry ==== | ||
Line 46: | Line 86: | ||
Support for existing products like Gradework and Materials within the Framework | Support for existing products like Gradework and Materials within the Framework | ||
+ | |||
+ | |||
+ | ==== Underground Takeoff ==== | ||
+ | |||
+ | |||
+ | ==== Basic Takeoff ==== | ||
+ | |||
+ | A subset of the current capabilities. Thoughts: | ||
+ | |||
+ | * PDF only, Sheet limit? | ||
+ | * Existing, Design, Subgrade, Stripped, strata surfaces only | ||
+ | * No Highway | ||
+ | * Very basic Materials integration? Area, lengths, counts, no phasing, classes | ||
+ | * More limited export? | ||
+ | * Limited Transform options/Map Projections | ||
+ | * How much georeferencing? | ||
+ | * In software temporary, permanent update to higher package for fee? | ||
+ | |||