stackstac
xarray
| stackstac | xarray | |
|---|---|---|
| 1 | 11 | |
| 252 | 3,748 | |
| 0.4% | 1.5% | |
| 3.4 | 9.7 | |
| 8 months ago | 2 days ago | |
| Python | Python | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stackstac
-
Can you replace Geoserver with COG and MVT from a bucket?
Like they're doing here to access sentinel 2 images https://github.com/gjoseph92/stackstac
xarray
-
Show HN: NumPy+Jax Except with Named Axes
If this idea sounds inderesting, you might want to look at xarray for a more established project: https://github.com/pydata/xarray
-
Spectral Imaging Made Easy: A Powerful Python Library
Interesting - I'm curious whether you feel that Xarray covers these use cases already?
https://xarray.dev/
Especially as I've said before that Hyperspy shares so many features in common with Xarray that Hyperspy should just use Xarray under the hood.
https://github.com/hyperspy/hyperspy/discussions/3405
-
State of Python 3.13 Performance: Free-Threading
Sadly, several python projects do not use semantic versioning, for example xarray [0] and dask. Numpy can make backward incompatible changes after a warning for two releases[1]. In general, the python packaging docs do not really read as an endorsement of semantic versioning [2]:
> A majority of Python projects use a scheme that resembles semantic versioning. However, most projects, especially larger ones, do not strictly adhere to semantic versioning, since many changes are technically breaking changes but affect only a small fraction of users...
[0] https://github.com/pydata/xarray/issues/6176
- Xarray: N-D labeled arrays and datasets in Python
-
Request for Startups: Climate Tech
PyTorch and JAX are used heavily in climate science on the ML side. For more general analytics, not so much. Many of our users like to use Xarray as a high-level API. There has been some work to integrate Xarray with PyTorch (https://github.com/pydata/xarray/issues/3232) but we're not there yet.
The Python Array API standard should help align these different back-ends: https://data-apis.org/array-api/latest/
-
Python for Data Analysis, 3rd Edition – The Open Access Version Online
Does polars have N-D labelled arrays, and if so can it perform computations on them quickly? I've been thinking of moving from pandas to xarray [0], but might consider poplars too if it has some of that functionality.
[0] https://xarray.dev/
-
What is lacking in Julia ecosystem?
https://xarray.dev
-
How we found and helped fix 24
bugs in 24 hours (in Tensorflow, Sentry, V8, PyTorch, Hue, and more)
Pydata's xarray
- Xarray awarded a support grant from NASA
- xarray: N-Dimensional labeled arrays and datasets in Python
What are some alternatives?
zen3geo - The 🌏 data science library you've been waiting for~
iris - A powerful, format-agnostic, and community-driven Python package for analysing and visualising Earth science data
rio-toa - Top Of Atmosphere (TOA) calculations for Landsat 8
fugue - A unified interface for distributed computing. Fugue executes SQL, Python, Pandas, and Polars code on Spark, Dask and Ray without any rewrites.
titiler - Build your own Raster dynamic map tile services
dask-awkward - Native Dask collection for awkward arrays, and the library to use it.