Paul In particular I envision there being a prominent tool window for "tactical insights" or "spatial analysis" or something of the like, which offers functionality referencing different layers/systems. Such as, computing distance from point (could be cursor point, or GPS point, etc) to some vector feature. E.g., for tropical layers, I thought of a tool where rolling over a point shows a line to the nearest forecast track point, distance, and closest approach time. Similar concepts could be applied to the GPS point and other path information, such as MST, L3 cell vectors, or NWS warning vectors. Some variations on this concept could apply to static mapping data, e.g., distance to coastline, max elevation in radial distance, etc.
I am aware of the heightened requirements associated with building tactical-grade software for the first time. Right now that only manifests in performance-oriented development, but once the engine is done, it will manifest in the creation of specific embedded functionalities which cross-reference separate systems and data objects. This is a very exciting set of concepts, but one I can only sit down to fully expatiate once most of the data assets are already integrated. In this way, I expect perhaps some of the best new features will come very late in 2025 in the very final pre-release stages, only when all the base data is in and working, and I can step-back and critically analyze opportunities for interactions between systems and data.