Hackathon: 2024-03-05 #485
Replies: 3 comments 1 reply
-
Today, I started to design the modifications needed to return data on any services that are available for a collection per the mini roadmap comment found here. I started to implement a method in the earthaccess.results.DataCollections class called 'services' that returns a list of services and information associated with each service. I would like to query CMR to return information on a service such as (we can modify this later to better fit the plugins interface):
I also wanted to make sure I am adding in new functionality that is consistent with current usage of earthaccess. I think it makes sense to implement a child class of ServiceQuery from the Python CMR API as is done by the classes in the search.py file. Then the above 'services' method can use that class to query CMR for service data. I think it may make the most sense to include the ServiceQuery class in the search.py file but am open to feedback! |
Beta Was this translation helpful? Give feedback.
-
@JessicaS11 and I tried to reproduce #453 with no luck on my side. We'll keep working on this tomorrow with a new Python environment and a fresh install. @battistowx started to work on implementing automatic handling of
@itcarroll wroked on #330 and seems like a fix could be ready this week. @Rhys-L also worked with us on these issues! |
Beta Was this translation helpful? Give feedback.
-
@mfisher87, @chuckwondo, and I worked in a VS Code live session to add a skeleton of unit tests. The planned tests would mock parts of the Earthdata Login (EDL) and Common Metadata Repository (CMR) responses to check that the User Acceptance Testing (UAT) environment is being queried appropriately, for PR-426. The work-in-progress was captured in this commit. |
Beta Was this translation helpful? Give feedback.
-
Reporting out
Please create a new comment (at the very bottom, use the text box with a button that says "comment", not "reply") to write about what you did today!
Please include links to GitHub issues or pull requests relevant to your work, and use those issues or pull requests as the "source of truth" for documenting the work; this makes future readers jobs easier :) It's OK to duplicate some information while writing a summary here!
Use the "reply" feature to have a discussion under any given comment.
Beta Was this translation helpful? Give feedback.
All reactions