[FY24.4 Sprint 2] Add 3-6 additional flight maps to CASEI

[heidimok]

This issue follows https://github.com/NASA-IMPACT/admg-casei/issues/634

Context

Back in FY24.1, we started visualizing flight paths for campaigns on CASEI. We started with 5 (see epic: https://github.com/NASA-IMPACT/admg-casei/issues/576) and have since expanded to ~8 (see YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR).

Example of a flight map for a campaign

As of FY24.3, we have published 27 campaign flight paths.

Known Challenges

We learned through past efforts in trying to automate the data collection and visualization process that currently it is NOT possible to fully automate this process for these reasons:

• Inconsistent data formats as in NASA's case airborne data ownership is split across 12 DAACs that all do things a bit differently
• Different ways to define measurement variable names. This might not seem like a big deal but it really makes it hard/slow to get buy-in when building out features quickly as terminology is for queries and UI filters gets challenged back and forth. There are initiatives on streamlining language, for example the official GCMD science keywords (which is a string of keywords) but each DAAC also has their own views and it’s an ongoing discussion.
• Incomplete data. To get the full set of historical data to even visualize flights (let along instruments on each flight deployment), in many cases you’ll need to manually look for data that’s lock in PDFs still or old canned films for example that are not digitized. This is what the ADMG data curators have been doing and filling in for CASEI

Goal

• We will continue to collect and visualize campaigns in batches (of around 3-6) because each campaign may need some manual data fixes.
• We will incorporate fixes to common data issues along the way, and continue to learn about the extent to which we can still create a pipeline for visualizing nav data in the cloud without having to do it locally and save out GeoJSON files

Acceptance Criteria

1. 3-6 additional nav data sets saved as YAML files https://drive.google.com/drive/u/0/folders/1R92_4YxYTo8oml0NHMCLFYJ-t-dHaWIR
2. Static locations for those campaigns https://docs.google.com/spreadsheets/d/17v-ZfeWoPZoCAVSs57Y3Q1gKUe6S49fZ8rC2KOO_myY/edit#gid=1924471089
3. 3-6 flight tracks visualized and deployed to CASEI in staging
4. Deploy from staging to production

[heidimok]

Future note for @LanesGood to move this issue out of backlog and label the correct PI Iteration and PI Sprint once the team has set up the project board for the next PI.