-
Notifications
You must be signed in to change notification settings - Fork 32
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
Move Docker image to the standard gdal base #324
Conversation
6c30555
to
2827f87
Compare
sqlalchemy==1.3.20 | ||
click<8.0.0 | ||
eodatasets3>=0.17.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's appropriate minimum versions in the dependencies now, I believe. So I removed these.
It's less maintenance than the geo-base one (fixing the current scan issue), and brings us in-line with datacube-alchemist and eodatasets.
... and can't require an ODC config on build.
The test is broken on newer docker container -- built-in WKT strings are slightly different. Strangely, it was sorting ascending and picking the first. ... so the least good match? But this worked because the test data used a completely different capitalisation to the real CRS, so they didn't match at all. Changed them to: 1. Compare without case sensitivity. 2. Compare total matches, rather than ratio. WKTs are very diff. lengths, and we want to match their strings of names/numbers, not penalize for missing sections (which is common). 3. Pick the best match, not the least
16e7d52
to
b86cd9b
Compare
Their dict return type changes too often. Suddenly our error messages are incorrect as we aren't looking for the right key names.
Codecov Report
@@ Coverage Diff @@
## develop #324 +/- ##
========================================
Coverage 86.18% 86.19%
========================================
Files 25 25
Lines 3048 3049 +1
========================================
+ Hits 2627 2628 +1
Misses 421 421
Continue to review full report at Codecov.
|
It's less maintenance than the geo-base one, and brings us in-line with datacube-alchemist and eodatasets.
It also fixes the current security-scan failure.