4

Instead of using Photoshop, you can fix the problem directly on QGIS. Hillshade rendering (or any other raster rendering) happens individual layer by layer, as each layer know nothing about their neighbours. You can bundle the all 9 rasters in a single layer by creating a virtual raster. You have a tool to create the virtual raster in the processing toolbox. ...


3

There are two things going on here I think: there is a difference between relative and absolute paths: /tmp/ is an absolute path, relative to the root directory. results/... is relative to the directory you are in. This is the same as ./results indeed, you cannot store a file to a folder that doesn't exist yet. thread In stead, you should: create the ...


3

If I understand correctly: You loaded the DEMs into QGIS, you were happy with the styling You weren't happy with the artefacts, so you did some polishing in Photoshop When loading the polished-up rasters, the styling in QGIS is different from what it was originally. If that's the case, you should be able to apply the styling of your "old" layers ...


1

OK so after a lot of messing around with some GIS software, the simplest way to do this is to open a GeoTIFF in PhotoShop (or any other image software) and set the mode to "Indexed Color" instead of "RGB Color". This seems to preserve the mapping of GeoTIFF data exactly, so that in this case water which is specified as "60" in ...


1

So the issue was with how QGIS was displaying the range of the raster. As stated in this answer, QGIS, by default does not calculate the range of the entire dataset but estimates it instead. This can be seen in Properties > Symbology > Band Rendering > Min/Max settings. The default option for accuracy is Estimate(faster). You need to set it to ...


1

This seems to be the bug described here or something similar. It affects raster layers when the bounding box is bigger than the raster layer. When you zoom in, everythin is perfect. This behavior is common for my QGIS installations on different machines with EPSG:4326 as project CRS (not 3857 as in your case), see screenshot with rasters in the same CRS (...


1

Titiler (map tile server), is not able to generate PNG files based on float32 TIFF PNG is not able to encode Float32, it's not TiTiler fault. You need to rescale the data to bytes (0-255) or to use the Mapbox/Mapzen trick (https://github.com/mapbox/rio-rgbify or https://github.com/cogeotiff/rio-tiler/blob/master/rio_tiler/utils.py#L364-L378) to encode ...


Only top voted, non community-wiki answers of a minimum length are eligible