intake / intake/intake-stac

Revamp at STAC sprint

Open
#159 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Python
Stars
113
Forks
25
PR merge metrics
No merged PRs in 30d

Description

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:

- Triage open issues
- Triage open PRs
- Bring linters/actions/deps uptodate
- Check the geopandas read logic vs what's in https://github.com/TomAugspurger/staccontainers
- Remove dependency on intake-xarray
- Switch the xarray read to just use xpystac (which delegates stacking to stackstac or odc-stac)

Just wanted to put this up in case it's not a good time for some reason (maybe because of https://github.com/intake/intake/pull/737 @martindurant)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.