-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revamp at STAC sprint #159
Comments
For reference here is the STAC catalog implementation and here the search for Intake 2 - largely copied from the code in this repo. I have not really been aware of the other changes in the STAC sphere. I am thoroughly in favour of improving the intake side of things, and I think we have an important part to play. Come to next wee'k pangeo talk to see what my plans are for Intake 2. |
Nice (https://cloudnativegeo.org/blog/2023/07/stac-sprint-8)! A lot of intake-stac development definitely happened at previous STAC sprints. @jsignell I just added you as a maintainer in case you do want to work on this at the sprint.
I think this is the key piece to rekindle development - articulating (maybe through short examples) where intake-stac can simplify workflows compared to directly working with those libraries that it would delegate to. |
Well as you might have guessed. This didn't end up happening at the STAC sprint 😞 but I am still optimistic that I'll be able to chip away at it this fall. |
I still think intake-stac serves an interesting role. Intake is domain-agnostic and python-specific whereas STAC is geo-specific and language-agnostic. So it is totally reasonable that someone might be more comfortable accessing all their data geo and non-geo via intake.
This repo has been a little neglected over the past year or so and the ecosystem has come a long way. There is a STAC sprint next week and it might be a good opportunity to tidy things up. These are the things I am thinking of:
Just wanted to put this up in case it's not a good time for some reason (maybe because of intake/intake#737 @martindurant)
The text was updated successfully, but these errors were encountered: