Designs for integrating platform maps/tracks from into CASEI front end

[heidimok]

Context

One challenge of visualizing platforms is that any given campaign can have many deployments with different platforms, instruments, and routes. Some are bigger scale, others are smaller scale. It's not easy to visualize this in a consistent way on the CASEI website.

This summer (2023), Anabelle (our summer intern) is tasked with assessing a platform maps/tracks methodology with the goal of identifying a consistent way to visualize this.

Problem

Once Anabelle has a proposed idea, it doesn't mean that it will be ready for production into the CASEI front end. We will still need a design process from a software perspective to figure out how to integrate the idea(s) and assess feasibility of implementation.

Acceptance Criteria

• [x] Reviewing methodology proposed by Anabelle (Likely @EJwalker13 @smwingo )
• [x] Extend those ideas by proposing how it might fit into the CASEI UI (likely @EJwalker13 and @heidimok). For example, is it a static image per deployment within the interactive timeline?
• [x] Proposed design with mockups (@heidimok)

[edkeeble]

Is this related to https://github.com/NASA-IMPACT/admg-casei/issues/414?

[heidimok]

Update cc @EJwalker13 @smwingo

• I met with @anabellebr22 to understand her flight maps and through that learned about how it might fit into the CASEI UI. Here is the mockup we worked on together. Link to prototype.

• Whereas I had initially thought the flight maps were based on campaign deployments, I learned that these are by platform (specifically planes), so to add it to the UI we'd likely want to show it in context of a platform.

[heidimok]

Closing this out as Anabelle completed the internship and shared outcomes in an IMPACT presentation (blog here)

In terms of the UI, this will be input into a FY24 feature for issue 414