The UAV photogrammetry project and the desire to match desktop and ConX interfaces has led us to investigate the next generation of UI layout. XAML has now opened up beyond C# code to support C++ which most of AGTEK's code is based on. The ability to reuse portions of the existing codebase is potentially a huge multiplier in effectiveness and speed to market.

Part of the thought here is to also use this as a platform for existing desktop products to run under but also to create modularity which allows us to go after different channels and markets. Selling an authoring tool for ADF for Leica instrument dealers for example. Selling just photogrammetry and mobile to environmental engineers, etc. There are lots of niches and sales channels that won't support or need a fullblown gradework that still have a need for simple applications particularly in the field. Our philosophy of tools for generalists is a winner beyond the narrow niche that we sell now.

One of the goals here is to create a hybrid desktop version that is much more web aware. A tight integration with cloud file systems (Access/ConX/Dropbox) and the desktop file system allows us to better organize the enormous number of files that customers now deal with. Add to that the syncing/publishing capability and map enablement allows us to potentially have the best of both worlds.

Look on the Microsoft Store for an application called XAML Controls Gallery. It contains all the native controls shipped with Windows 10 and available for our use.

• 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)
• Color schemes differing from ConX for branding. For example blue interface highlights instead of red

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

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

• 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.)

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.

The basic level of the framework is two-way connections to cloud services. Access, ConX and Dropbox come to mind although I know Box.net is also used by some companies. In general the ide

Probably need a snappier name, requires expansion of ADF to have KMZ attributes

Story Here: ADF Creation Module

The UAV workflow as previously defined.

Starting with SmartTrack as a base but then expanding reporting

Support for existing products like Gradework and Materials within the Framework

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?