-
Notifications
You must be signed in to change notification settings - Fork 1
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
add support for reading from remote resources #18
Labels
enhancement
New feature or request
Comments
davemfish
added a commit
to davemfish/geometamaker
that referenced
this issue
Mar 6, 2024
davemfish
added a commit
to davemfish/geometamaker
that referenced
this issue
Mar 6, 2024
davemfish
added a commit
to davemfish/geometamaker
that referenced
this issue
Mar 7, 2024
davemfish
added a commit
to davemfish/geometamaker
that referenced
this issue
Mar 7, 2024
davemfish
added a commit
to davemfish/geometamaker
that referenced
this issue
Mar 7, 2024
davemfish
added a commit
to davemfish/geometamaker
that referenced
this issue
Mar 7, 2024
davemfish
added a commit
to davemfish/geometamaker
that referenced
this issue
Mar 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's common that someone will want to create metadata for a dataset that is already stored remotely somewhere. So geometamaker should be able to open a dataset at a remote URL, read file metadata (e.g.
gdalinfo
stuff), and read any existing MCF.GDAL (and for the most part pygeoprocessing) can already do this. So added functionality we need from
geometamaker
is the ability to read an existing remote MCF.The text was updated successfully, but these errors were encountered: