Gather tracks and stationary data for 5 Campaigns

[heidimok]

Context

EPIC: Visualize aircraft flight path for 3 Campaigns in CASEI https://github.com/NASA-IMPACT/admg-casei/issues/576

In the previous issue, https://github.com/NASA-IMPACT/admg-casei/issues/577, we identified the 5 Campaigns that we will create flight path maps for: OLYMPEX, CAMP2Ex, ACTIVATE, HS3, IMPACTS. Now we need to actually download/access the data.

Goal

In order to start visualizing flights, we need to actually access the data - in whatever format and volume it exists in - in a common way/place. This isn't a straightforward process. Given that the data isn't all in a consistent format, some will require manual download, while others can be directly accessed online.

• Stationary data will need to be manually downloaded
• Many flight paths will have large data files where it might not make sense to directly download so a URL to the data is the best option.

Steps

This is going to be a shared task between @als0076 @willemarcel and @heidimok as Ashlyn has more domain knowledge and understand the data a bit more, but Wille can step in when it just doesn't make sense to manually download datasets.

• [x] For each of the platforms each select Campaign in this spreadsheet, provide a url link to where the data is @als0076
• [x] Where we cannot find specific data, or the process is going to take a long time, make a note so that we design around it instead of waiting @als0076
• [x] Where it makes sense, or is the only option, manually download and save the data to a shared folder. @als0076
• [x] Where it doesn't make sense to manually download the data, mark it in the spreadsheet so that @willemarcel can support the access using the url. @willemarcel

Acceptance Criteria

• [x] Data ready for prototyping for OLYMPEX
• [x] Data ready for prototyping for CAMP2Ex
• [x] Data ready for prototyping for ACTIVATE
• [x] Data ready for prototyping for HS3
• [x] Data ready for prototyping for IMPACTS

[smwingo]

discussions/work session should include: Ashlyn, Praveen, Willie

notify Steph if need additional input/guidance :)

[heidimok]

Given that there is A LOT of data associated with these campaign deployments, I asked @alukach for some advice on how he sees us being able to scope some technical work for @praveenphatate around data gathering to ensure that @willemarcel can successfully then render a flight path for that deployment.

Anthony wrote this quick gist doc that could be great support/food for thought on tasks. https://gist.github.com/alukach/09ee48378096e75b8f21779bb7183e35

---

Some things we can look into/discuss during Deep Dive beyond downloading the data:

• How to efficiently download data across EarthData search for deployments where we need flight tracks @praveenphatate I know you might have started exploring this
• How to condense that data - @willemarcel may already have ideas on this, but @praveenphatate you might also be able to think about this as well. Somehow we will need to download and condense all the flight track data for every single campaign deployment into a single file.
• How to submit each file into the ADMG backend for each Campaign. There is actually a field for both Ground sites map and Flight tracks for deployment drafts.
• Finally, how to render that as interactive maps on the UI @willemarcel

[heidimok]

Closing this general data gathering issue because we have done a thorough job of documenting data in this spreadsheet: https://docs.google.com/spreadsheets/d/14vleSOggRQFfyT_wgvCGGlVpkpwzGiKM-ZPYE7xFjkQ/edit#gid=1224749507

As @willemarcel works to actually prototype each campaign, he'll be able to reference the data sourced.