-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support raster overviews #140
Merged
Merged
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
* alpha band should not be masked when read * if alpha is not Byte rasterio read(masked=True) doesn't work correctly * default nodata wasn't being set in metadata * add per band band_nodata as string * excluded masked/nodata values from stats * add some stats and combine stats in updates
jgoizueta
approved these changes
Jun 5, 2024
ie. avoid decimal point in integers
Jesus89
reviewed
Jun 21, 2024
raster_loader/io/common.py
Outdated
"name": e["band_name"], | ||
"stats": e["stats"], | ||
"colorinterp": e["colorinterp"], | ||
"band_nodata": e["band_nodata"], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would go for nodata
name for consistency
Changes:
|
Jesus89
approved these changes
Jun 21, 2024
Merged
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.
Proposed Changes
Pull Request Checklist
Additional Information
We used different examples to test a variety of general cases.
Note the number of overviews can be seen in metadata from the difference between
maxresolution
andminresolution
values, as is defined as following:cartocog_3byte_60cm_small.tif (1.3MB)
Trying to upload the file:
We get an error:
Error uploading to BigQuery: The input raster must be a GoogleMapsCompatible raster.
So we need to pre-process the file with
gdalwarp
, using the recommended options:Then uploading the resulting file works fine:
Visualizing with deck.gl:
Using this for the layer config:
cartocog_3byte_30cm_small_pixel.tif (2.7MB)
Process the file with gdalwarp including recommended options:
Then upload the results with
raster-loader
:Raise an error:
Error: Error uploading to BigQuery: Input raster pixel resolution exceeds the max supported resolution of 26.
So remapping with
-co ZOOM_LEVEL=17
option it works fine:Using in this case:
cartocog_byte_10km_MOD12Q1_Land_Cover_Type2.tif (512KB)
With:
cartocog_byte_76m_20240216_N700Coverage_NSA.tif (13.7MB)
With:
lonlat_wgs84_float32_28m_borneo.tif
With: