You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hope you've been having a good week. In our 4th session we explored Earthdata Access from the Cloud with the earthdata Python package, and met the team from Element 84 who will be providing support during the next two months. Next week each team will present their work-in-progress Pathways in our final structured Cohort Call. Below is a light digest of Call 04.
Cheers,
The NASA-Openscapes Mentors
@NASA-Openscapes/mentors-2021 @erinmr@jules32
Digest: Cohort Call 04 [ 2022-nasa-champions ]
Cohort Folder - contains agendas, video recordings, pathways folder
Goals: We explored Earthdata Access from the Cloud with the earthdata Python package, and met the team from Element 84 who will be providing support during the next two months
Task:
Task for next time: Prepare your Pathways presentation
Have a Seaside Chat with your research group
Prepare to present your Pathway on Call 5
Each group has 5 minutes to share their pathway: (3min present + 2min Qs)
Skills, expertise, the data you want to use - what do you need
Share Pathway Doc in our PathwayShare folder before Call 5
earthdata is a Python library that abstracts the required operations to access or download datasets from NASA.
A few lines from shared notes in the Agenda doc:
Interested in today's session and accessing data in the cloud - first time experience today
It's interesting that people always say that python promotes reproducible science but there are still lots of issues with using other people's notebooks due to dependency issues +1+1
Skillsets to find your way since in these early days there are different ways to access data, hopefully will get more consistent. "Early adopter friction". Skillset is less a single tool than a whole process
yes and this group is so important for helping us smooth that friction
We need a genuine problem to have to move into the cloud, it's still too abstract
What is a "concept_id" -
Makhan: It is a unique identifier for a dataset, that changes with dataset version revisions even if the dataset name stays the same
Luis: in my opinion the preferred way to access a data set
What is a granule?
Granule = single data files (geotiff, netcdf, hdd, etc)
My interpretation is a geospatial data chunk
Co-working topic requests:
The idea of efficient (server-side) spatial subsetting has caught people's interest
Some techniques might rely on cloud-optimized formats
NASA specific tools? Harmony API?
How to set-up environments so that workflows are more reproducible
How to effectively use dask to process in parallel ... daskhub architecture, auto-scaling and how to effectively choose targets to trigger scaling/de-scaling
The text was updated successfully, but these errors were encountered:
Hi @NASA-Openscapes/2022-nasa-champions-team ,
Hope you've been having a good week. In our 4th session we explored Earthdata Access from the Cloud with the
earthdata
Python package, and met the team from Element 84 who will be providing support during the next two months. Next week each team will present their work-in-progress Pathways in our final structured Cohort Call. Below is a light digest of Call 04.Cheers,
The NASA-Openscapes Mentors
@NASA-Openscapes/mentors-2021 @erinmr @jules32
Digest: Cohort Call 04 [ 2022-nasa-champions ]
Cohort Folder - contains agendas, video recordings, pathways folder
Cohort webpage: https://nasa-openscapes.github.io/2022-nasa-champions
Goals: We explored Earthdata Access from the Cloud with the
earthdata
Python package, and met the team from Element 84 who will be providing support during the next two monthsTask:
Task for next time: Prepare your Pathways presentation
Have a Seaside Chat with your research group
Prepare to present your Pathway on Call 5
Each group has 5 minutes to share their pathway: (3min present + 2min Qs)
Skills, expertise, the data you want to use - what do you need
Share Pathway Doc in our PathwayShare folder before Call 5
Notebook: (Luis Lopez)
https://nasa-openscapes.github.io/earthdata-cloud-cookbook/examples/earthdata-access-demo
earthdata is a Python library that abstracts the required operations to access or download datasets from NASA.
A few lines from shared notes in the Agenda doc:
Interested in today's session and accessing data in the cloud - first time experience today
It's interesting that people always say that python promotes reproducible science but there are still lots of issues with using other people's notebooks due to dependency issues +1+1
Skillsets to find your way since in these early days there are different ways to access data, hopefully will get more consistent. "Early adopter friction". Skillset is less a single tool than a whole process
We need a genuine problem to have to move into the cloud, it's still too abstract
What is a "concept_id" -
Makhan: It is a unique identifier for a dataset, that changes with dataset version revisions even if the dataset name stays the same
Luis: in my opinion the preferred way to access a data set
What is a granule?
Granule = single data files (geotiff, netcdf, hdd, etc)
My interpretation is a geospatial data chunk
Co-working topic requests:
The idea of efficient (server-side) spatial subsetting has caught people's interest
Some techniques might rely on cloud-optimized formats
NASA specific tools? Harmony API?
How to set-up environments so that workflows are more reproducible
How to effectively use dask to process in parallel ... daskhub architecture, auto-scaling and how to effectively choose targets to trigger scaling/de-scaling
The text was updated successfully, but these errors were encountered: