Map frame resize #215
Open
Map frame resize #215
Conversation
This file contains hidden or 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
mhhd2020
approved these changes
Feb 24, 2023
…ted GeoTIFFs for A0 maps
matthiasschaub
force-pushed
the
map-frame-resize
branch
from
0de046b to
9e926f4
Compare
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 PR is meant as a proposal how we could reduce the map frame size. This size is later also used to determine (and heavily influence) the resource capacity needed for the processing tasks (especially the openCV tasks).
Open ToDos:
map_framein database still has the correct ratio and looks alright.max_length(maximum number of pixel on either height or width for saved map frame)