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
Author Name: Etienne Tourigny (@etiennesky) Original Redmine Issue: 9460 Affected QGIS version: 2.0.1
Assignee: Etienne Tourigny
GdalTools should rely on commandline tools only for complex operations, not basic dataset info.
The SRS and extent query methods rely on gdalinfo, which is fragile as reported by Even Rouault:
#d63104ae50dcd45ddf50dfe31ea6803530a64b26#commitcomment-5218484
Just an outsider point of view : why using GDAL utilties and risky output parsing to get the SRS and not just plain Python GDAL API...
I have a pull request to fix this, but I am hesitant to apply this to master now. Any input would be appreciated.
The text was updated successfully, but these errors were encountered:
Author Name: Etienne Tourigny (@etiennesky)
see pull request #1129
Sorry, something went wrong.
Author Name: Giuseppe Sucameli (@brushtyler)
Fixed in changeset "58faa5b4ad113860e798f2b5fdeb0741bb864e09".
Merged, thanks Etienne.
No branches or pull requests
Author Name: Etienne Tourigny (@etiennesky)
Original Redmine Issue: 9460
Affected QGIS version: 2.0.1
Assignee: Etienne Tourigny
GdalTools should rely on commandline tools only for complex operations, not basic dataset info.
The SRS and extent query methods rely on gdalinfo, which is fragile as reported by Even Rouault:
#d63104ae50dcd45ddf50dfe31ea6803530a64b26#commitcomment-5218484
I have a pull request to fix this, but I am hesitant to apply this to master now. Any input would be appreciated.
The text was updated successfully, but these errors were encountered: