outsourced and restructured DEM preparation functionality #18
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
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.
This restructures the DEM and WBM preparation functionalities into a new dedicated module
dem.The module contains two functions:
dem.prepare: download DEM tiles and convert them into the MGRS tiling schemedem.mosaic: scene-specific mosaicking based on the output ofdem_prepareThe created folder structure stays the same. A larger change is that the tiles are no longer downloaded for the whole bounding box of all scene geometries (which would download a lot of data for larger scene selections). Instead, only tiles covering individual scenes (plus a buffer) are downloaded. This requires repeated access to the DEM storage servers.