[Flight tracks sprint 2] Add 5 campaign flight maps to CASEI

[heidimok]

Goal

To add visual flight maps to CASEI campaigns in increments of 5

• Help refine the flight maps workflow https://github.com/NASA-IMPACT/ADMG-project/issues/950
• Balance efforts each sprint as it'll require support from curators

Campaigns

(referring to this campaign list that @als0076 helped put together last PI)

These all have 1 deployment:

1. ASHOE - Data Location - ESPO
2. CPEX-AW - Data Location - GHRC
3. CPEX-CV - Data Location - GHRC
4. CR-AVE - Data Location - ESPO
5. CRYSTAL-FACE - Data Location ESPO

^NOTE THAT WE ENDED UP FOCUSING ON 5 DIFFERENT CAMPAIGNS

Current Workflow Steps

Note that Actual development issues will exist in the admg-casei repo. Developers to create PR in the right repos, and link any progress in this issue in the comments.

1. Identify campaigns to visual (above)
2. Get data for each campaign
   • Tracks data - Apply query to automate identify as much of the tracks data for each campaign as possible (reference automated download issue). Create a user-friendly way to gather what requires help/curation (e.g. data type) @praveenphatate
   • Tracks data - Help fill in addition information that we could not automate @als0076
   • Tracks data - Create a yaml file in casei-data-pipeline repo https://github.com/NASA-IMPACT/casei-data-pipeline/tree/main/campaigns @praveenphatate or maybe @willemarcel
   • Static data - Add static locations to existing CSV https://docs.google.com/spreadsheets/d/17v-ZfeWoPZoCAVSs57Y3Q1gKUe6S49fZ8rC2KOO_myY/edit#gid=1924471089 @als0076
3. Visualize data on campaign page above timeline @willemarcel
4. Showcase visual with ADMG team member to confirm accuracy of visualization @willemarcel to @smwingo @als0076
5. Deploy visualization view to production @willemarcel

[heidimok]

Update Feb 8

• @praveenphatate trying to get updated data dump for access campaigns, but blocked by having access. Need to coordinate (ongoing). We can remove this blocker by focusing on campaigns we do have data for now.
• @praveenphatate to get data based on what he has now (not what is in the epic), share with @als0076 and narrow down to ~5 to focus on for this sprint. And then go through process to get to YAML file for Wille by Monday.
• @willemarcel to receive data and create flight maps, share on staging, and deploy to production.

[heidimok]

Update Feb 15

• We will focus on 1 flight track this sprint, because there were data format issues for the others
• @willemarcel to share image of the new visualization and push to production
• @willemarcel to comment on the campaigns with data issues. These will be worked on after Wille's vacation (second week of Sprint 4)

[willemarcel]

The GOES-R PLT was the only campaign with a data format that matches with the pattern we found in the previous sprints. It's already published to production https://impact.earthdata.nasa.gov/casei/campaign/GOES-R%20PLT

I created pull requests with the other campaigns yaml files, so we can merge it when we can deal with the different data formats.

https://github.com/NASA-IMPACT/casei-data-pipeline/pull/4 https://github.com/NASA-IMPACT/casei-data-pipeline/pull/3 https://github.com/NASA-IMPACT/casei-data-pipeline/pull/2 https://github.com/NASA-IMPACT/casei-data-pipeline/pull/1

[heidimok]

Closing this issue with just the 1 campaign deployed.