Plans for forky
Dear Sebastiaan, dear Francesco, dear all,
I would like to share with you my plans for new packages that I would
like to add to debian-gis during the forky cycle.
I do it before starting the actual job and before filing ITPs to have a
chance to have a discussion, if needed, and to get feedback from you.
Please consider that I plan to maintain the packages myself, but as a
DM, I could need some help, from time to time, from a DD.
For sure I will need support for the first upload.
The fist group of packages that I plan to include is mostly a collection
of (optional) dependencies of packages that are already in debian-gis:
* s3fs: https://github.com/fsspec/s3fs (needed by satpy, stac-asset and
zarr)
* universal-pathlib: https://github.com/fsspec/universal_pathlib (needed
by zarr and satpy)
* google-crc32c: https://pypi.org/project/google-crc32c (needed by zarr)
* cql2: https://github.com/developmentseed/cql2-rs (needed by pystac-client)
* stac-pydantic: https://github.com/stac-utils/stac-pydantic (needed by
stac-validator and stac-check)
* obstore: https://github.com/developmentseed/obstore (needed by zarr)
Please note that some of them are written in RUST, but I still think
that it is a good idea to have them in debian-gis.
The only exception could be obstore. It is a general purpose package
providing access to S3, so, maybe, it could make sense to have it in the
python or rust teams.
The second group of packages has to purpose of improving our STAC
(https://stacspec.org) ecosystem:
* stackstac: https://github.com/gjoseph92/stackstac
* xstac: https://github.com/stac-utils/xstac
* stac-asset: https://github.com/stac-utils/stac-asset
* stac-vrt: https://github.com/stac-utils/stac-vrt
* fields: https://github.com/stac-api-extensions/fields
* rio-stac: https://github.com/developmentseed/rio-stac
A third group is for packages linked to the new Copernicus EOPF
(https://eopf.copernicus.eu) framework, being developed by ESA for data
processing/access:
* xarray-eopf: https://github.com/EOPF-Sample-Service/xarray-eopf
* eopf-stac: https://github.com/EOPF-Sample-Service/eopf-stac
* GDAL-ZARR-EOPF: https://github.com/EOPF-Sample-Service/GDAL-ZARR-EOPF
* eopf-cpm: https://gitlab.eopf.copernicus.eu/cpm/eopf-cpm
* xcube-eopf: https://github.com/EOPF-Sample-Service/xcube-eopf
Also some data processor could be added to the list as soon as it
becomes openly accessible.
Finally a small group of packages more directly related to the
remotesensing task:
* python-polsarpro: https://github.com/satim-co/PolSARpro
* eofetch: https://github.com/stcorp/eofetch
* sentineleof: https://github.com/scottstanie/sentineleof
* cf-xarray: https://github.com/xarray-contrib/cf-xarray
* pyais: https://github.com/M0r13n/pyais
* sarpy: https://github.com/ngageoint/sarpy
* sarkit-convert: https://github.com/ValkyrieSystems/sarkit-convert
* xarray-ceos-alos2: https://github.com/umr-lops/xarray-ceos-alos2
Of course it is a lot of packages and each of them could need some
additional dependencies, so I could not be able to complete the job.
My plan is just to start working on the ones that look more
interesting/important and see how it proceeds.
I would really appreciate any comment / suggestion, especially if you
think that some of the listed packages are not relevant enough to be
include din Debian.
Please feel free to add to the list package that could be related to the
one indicated bu not included in the list.
kind regards
--
Antonio Valentino
Reply to: