Closed kylebarron closed 4 years ago
Oops, this was my fault, I left messy async
code in my fork and I forgot to pass **kwargs
through.
Back to high res :D
Note with @2x images that the largest elective source of time cost is the color correction, which costs 900ms on each 512x512 image.
Note: @vincentsarago before you debug anything let me make sure I didn't accidentally modify important code while profiling.
As I mentioned on Slack, since switching back to GDAL 2.4, my mosaic got blurrier:
It turns out that the blurriness is actually because I told Mapbox GL JS that the
tilesize
was 512, while it's actually 256. Correctly telling Mapbox GL JS that thetilesize
is 256 makes it acceptable:Still, I'd prefer to actually serve 512x512 high res tiles. You can see from these two links that both
@2x.jpg
and@2x.png
https://naip-lambda.kylebarron.dev/7610d6d77fca346802fb21b89668cb12ef3162a31eb71734a8aaf5de/15/5241/12663@2x.jpg?color_ops=sigmoidal+RGB+4+0.5%2C+saturation+1.25 https://naip-lambda.kylebarron.dev/7610d6d77fca346802fb21b89668cb12ef3162a31eb71734a8aaf5de/15/5241/12663@2x.png?color_ops=sigmoidal+RGB+4+0.5%2C+saturation+1.25So I need to debug further where the
tilesize
isn't being passed on correctly