Skip to content
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

Proposal: remove pygeoprocessing as a dependency #56

Open
davemfish opened this issue Nov 25, 2024 · 0 comments
Open

Proposal: remove pygeoprocessing as a dependency #56

davemfish opened this issue Nov 25, 2024 · 0 comments
Labels
on hold there's a reason we aren't working on this yet

Comments

@davemfish
Copy link
Collaborator

davemfish commented Nov 25, 2024

We're using a few convenient pygeoprocessing functions right now,

pygeoprocessing.get_gis_type
pygeoprocessing.get_vector_info
pygeoprocessing.get_raster_info

Each are called one time. It's convenient to have them, but perhaps not worth including the whole of pygeoprocessing as a dependency. We could replace these by using the GDAL API directly. It might result in some code being basically duplicated in geometamaker and pygeoprocessing. We miss out on beneficial updates to these functions in pygeoprocessing, but we get the benefit of potentially customizing them to the needs of geometamaker without needing upstream changes.

See also #46

@davemfish davemfish added the on hold there's a reason we aren't working on this yet label Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
on hold there's a reason we aren't working on this yet
Projects
None yet
Development

No branches or pull requests

1 participant