We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Breaking this out of #19
Naming things is always a bit tricky, but following on from @Aariq 's suggestion on renaming some of the env vars, current thoughts are:
GEOTARGETS_GDAL_RASTER_DRIVER_NAME -- > GEOTARGETS_GDAL_RASTER_DRIVER
GEOTARGETS_GDAL_RASTER_DRIVER_NAME
GEOTARGETS_GDAL_RASTER_DRIVER
It's a small change but I think it's worthwhile to reduce typing where practical. On the GDAL website they are called "Raster drivers" too, so there's that?
The text was updated successfully, but these errors were encountered:
Totally agree with dropping "_NAME" from the option name, that is a great suggestion
I also agree with your point RE: "CREATION_OPTIONS" (#19 (comment)).
At a minimum we need to distinguish between options used to write/create a datasource vs. those used to read/open them.
Sorry, something went wrong.
tar_terra_vect()
closed in #30
No branches or pull requests
Breaking this out of #19
Naming things is always a bit tricky, but following on from @Aariq 's suggestion on renaming some of the env vars, current thoughts are:
GEOTARGETS_GDAL_RASTER_DRIVER_NAME
-- >GEOTARGETS_GDAL_RASTER_DRIVER
It's a small change but I think it's worthwhile to reduce typing where practical. On the GDAL website they are called "Raster drivers" too, so there's that?
The text was updated successfully, but these errors were encountered: