feat: optimise cutline handling by only using the cutline if required #258
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blacha
commented
Dec 12, 2022
| return None | ||
|
|
||
| # Not asked to optimize the cutline | ||
| if not optimize: |
There was a problem hiding this comment.
I have left this disabled for now, as it needs more testing and just by ignoring the cutline for most tiles should significantly speed up the process
|
This logic can be removed once OSGeo/gdal#6905 is released. |
paulfouquet
approved these changes
Dec 14, 2022
|
|
||
| # osgeo is embbed in the Docker image | ||
| from osgeo import gdal # pylint: disable=import-error | ||
| from osgeo import Geometry, Layer, ogr # pylint: disable=import-error |
There was a problem hiding this comment.
You could import everything from osgeo in the same line
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.