Support a normalize option on the GeoTIFF source #12836
Merged
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.
By default, we normalize values in GeoTIFF sources so that style expressions on the layer work with values between 0 and 1. This change makes it so the GeoTIFF source accepts a
normalize
option to control this behavior. Ifnormalize
is set tofalse
, then the raw GeoTIFF values will be make available to style expressions on the layer.The current implementation uses 8-bit values for normalized data and 32-bit otherwise. In the future, we may change this to support higher bit depth for normalized values as well. But this implementation detail is not exposed to users.
I haven't had any luck finding a CORS-friendly source of elevation data hosted as GeoTIFF. Both the AWS Terrain Tiles and Copernicus DEM data are not CORS-friendly. But here is a movie of a elevation tile from the Terrain Tiles with a CORS proxy in front:
Fixes #12834.