feat(landing): Add Config Debug for screenshot elevation data. #3174
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
reviewed
Mar 12, 2024
blacha
reviewed
Mar 13, 2024
blacha
approved these changes
Mar 13, 2024
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.
Motivation
As we want to screenshot some elevation map for smoke tests. We need enable the debug urls for it.
Modification
debug.layerfor screenshot different output.debug.layerdebug.terrainfor screenshot map with terrain on.debug.terrainupdateVisibleLayers, date range slider is not been used atm. This is cause problematic by automatically adding aerial layers.Checklist
If not applicable, provide explanation of why.