fixed using raster files with block size other than default value

CartoDB / raster-loader

https://raster-loader.readthedocs.io

Other

15 stars 4 forks source link

fixed using raster files with block size other than default value #130

Closed volaya closed 8 months ago

volaya commented 8 months ago

This PR fixes the case of using a raster layer with a block size other than the default one (256). In that case, the resolutions where not being correctly computed. This is fixed with these changes

shortcut-integration[bot] commented 8 months ago

This pull request has been linked to Shortcut Story #394409: Review raster tables with non-default block size.

volaya commented 8 months ago

The issue should be fixed now

Jesus89 commented 8 months ago

Cool! The issue is fixed now (It makes sense that the corrected resolution needs to be applied to both data and metadata).

The only thing I noticed is that in the exploded pixels, there are more nodata values than in QGIS.

nodata: empty
0: yellow

Could you check that please?

volaya commented 8 months ago

Here is how the map looks when rendered, which seems to be correct. The above image was probably due to the rendering configuration in the Maps API, as @Jesus89 points out