Team: Zach Rouse, Parker Coleman, Yancy Matherne
Concept: When military planners doing an Analysis Of Alternatives (AOA) for a particular mission, weather impacts must be considered. Weather can impact decisions such as where to place assets, what are the right assets to deploy, what is the best traversal route, etc. The problem is missions are temporal, in that they occur of a span of time. During the course of a mission, weather conditions will change and affect the planning for that mission. This mad dash was to develop a tool that allows mission planners to quickly visualize the environmental impacts predicted for various transit routes and velocities.
Approach: Our approach was to allow mission planners to import, create, or modify planned routes and speeds and then automatically synchronize the routes’ positions and times with the display of the appropriate weather forecast. We provided slider bars and animation capabilities to display the position of assets along multiple alternative tracks at each available forecast time. The animation and sliders provide a visual representation of the weather conditions mashed with asset locations for all forecast data points along the mission. This allows the mission planners to visualize the weather conditions across the span of the mission execution (forecast data permitting).
Design: Geocent utilized several existing capabilities developed during other projects and mad dashes. OGC standards were used to overlay the weather data using Web Map Services (WMS) that expose forecast data stored in NetCDF or GRIB files. We utilized Web Feature Service Transaction (WFS-T) based data input tools previously developed for our OpenCOP system as the user interface to manipulate the mission tracks. We then developed interpolation algorithms to identify specific point locations of assets at each forecast time within the forecast data set. All of this information was integrated and then displayed using animation tools in our OpenCOP platform as well as other Common Operation Pictures.
Retrospective: This dash was successful because we were able to leverage many of the existing tools and services to build a new capability in a short amount of time. This is really a success story for the development of services and capabilities that can be rapidly integrated to create new capabilities quickly. It is also a success story for the use of standardized OGC services to allow rapid integration of disparate data sources.