[Flight tracks sprint 1] 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 (@als0076 on the dev side we are open to seeing how much effort this requires for curators and we can adjust the number of campaigns from there).

Campaigns

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

These all have 1 deployment:

1. DC3 - Data location ASDC
2. ACEPOL - Data Location - ASDC
3. ACES - Data Location GHRC
4. Aeolus Cal/Val - Data Location ASDC
5. ARISE - Data Location ASDC

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]

List of possible name filters https://docs.google.com/spreadsheets/d/1RWYbaMlXr8T6aCrrVv99HLCo3yEsR50O6FyPvf8qQE4/edit#gid=0

[heidimok]

Current progress and steps of this week:

Current

• We have a list of possible filters, with some gaps.

Next

• Based on the query params (shared in GoogleSheet above), get a files list that Ashlyn can review. For platforms where you need to filter by file names get all the results from the API (we can filter it later). We can later investigate more about the API but let's keep this aside this sprint and focus cobbling together what we can.
• Ashlyn to review the CSV or YAML (but perhaps CSV in GoogleSheets is the most accessible for now)
• Once reviewed, Praveen to give Wille list of files
• Wille to visualize and deply from there.

[willemarcel]

We have already 4 campaigns available for visualization on staging: http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/Aeolus%20Cal/Val http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/DC3 http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/ARISE http://admg-inventory-staging.s3-website-us-east-1.amazonaws.com/casei/campaign/ACEPOL

The ACES campaign has a different file format, so we decided to postpone this one.

[heidimok]

Thank you @willemarcel - for the Aeolus one, how should we be linking to that (since there is a / in the name)? I'm not able to link there.

@als0076 would you be able to take a quick look at these to flag if any of the visual seem off?

Once we have it confirmed I will close out the issue, and @willemarcel can deploy from staging to production.

[als0076]

All 4 campaigns look great to me.

[heidimok]

Awesome. I will close this issue and pass to @willemarcel to take the deployment steps.

We can do a retro at the deep dive today for this first set.

[willemarcel]

Thank you @willemarcel - for the Aeolus one, how should we be linking to that (since there is a / in the name)? I'm not able to link there.

I edited my comment and fixed the link!

[heidimok]

Retro Notes:

• First drawback was that the Earthdata website was down, could not figure out a way to automate the whole process, had to do it manually.
• Question - For Platforms & Instruments on the CASEI UI, what are the short names we are using? Praveen's script takes a platform's short name.
• We need the long name, not the short name. There was some discrepancy in the file Praveen sent to Wille with the name of the deployment. Praveen got the name from the backend CSV. When we add it to the map, we need the name the same way as it is on the website or else the filter is wrong.
• For Ashlyn reviewing the spreadsheet went well, not real issues finding the static issues.
• For Wille it was good, faster to process campaigns. The challenge was a campaign with / caused problems in code which required some change.
• For some platforms, one campaign had falcon and gc8 where the names of the columns they used to store date, lon, lat were different so that also required changes in code to deal with column names. We might continue to have variations in the future which will still require interventions.

[als0076]

@smwingo flight track map from last sprint