m.neural_network.preparetraining: change vrts to relative paths #5
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 PR adapts the created .vrts such that they now contain relative paths. This allows for moving files around (if source and .vrt are moved altogether) and to have valid .vrts inside and outside of docker containers.
Unfortunately, creating relative paths in a .vrt is not part of the gdal.BuildVrtOptions, so in this PR, the relative paths are hacked into the existing .vrts afterwards.