O no! Everybody who cares is most welcome! :-)) > Am 15.05.2020 um 09:02 schrieb Alexandre Neto <[email protected]>: > > Ah, sorry. I misread it. :-) > > A quinta, 14/05/2020, 23:43, Priv.-Doz. Dr. Maria Shinoto > <[email protected]> escreveu: > Dear Alexander, > > Thank you for looking into it. As I said, there is no projection on the fly, > my layer and the file are in EPSG:6670, as is the project. > > I will try with a selection from the large layer today!. > > Best, > Maria > > > > Am 14.05.2020 um 23:15 schrieb Alexandre Neto <[email protected]>: > > > > If the project is in one CRS, and the layer is in another, then the raster > > is transformed on-the-fly for sure. > > > > Give it a try. > > > > A quinta, 14/05/2020, 08:47, Priv.-Doz. Dr. Maria Shinoto > > <[email protected]> escreveu: > > Hi, > > > > > So the problem occurs only when creating a Hillshade, from a DEM, using > > > the hillshade symbology? > > > > well, I did not try hillshade in any other case yet, so, yes. > > > > > Have you chosen the correct a factor value? > > > > What is that? Perhaps there is something I miss? > > > > > Try to use the same projection in the project and in the layer so that > > > you have no reprojection going on. > > > > The project is set to EPSG:6670, and the Raster layer is not projected on > > the fly, but from a file that is in EPSG:6670. So I think, reprojection is > > not the problem here. > > > > Thanks for checking this up, if you have an explanation about the factor > > value, that might help. > > > > Best, > > Maria Shinoto > > > > > > > > Nicolas Cadieux > > > Ça va bien aller! > > > > > >> Le 13 mai 2020 à 04:31, Priv.-Doz. Dr. Maria Shinoto > > >> <[email protected]> a écrit : > > >> > > >> Hi, > > >> > > >> Today I tried making a hillshade from the raster data you helped me out > > >> today -- after filling empty pixels, everything looks great. > > >> > > >> Now, when trying to set the layer symbology to hillshade, I got > > >> artifacts with the default setting and the recommend bilinear with > > >> medium. Looking for a solution, I found this conservation about the same > > >> issue (I think) from about 3 years ago; it seems to be a problem still > > >> today (working with QGIS 3.12). > > >> > > >> https://github.com/qgis/QGIS/issues/23859 > > >> > > >> So I tried the hillshade tool from GDAL in the Processing toolbox with > > >> identical setting, and everything looks great. > > >> > > >> I think that the flawed hillshade in the easily accessible Symbology > > >> dialogue needs some work or a hint to the GDAL tool in the Processing > > >> toolbox. It is frustrating for someone who is new. > > >> > > >> I add screenshots from the bad results in the Properties > Symbology > > >> dialogue and the raster image from which I started. > > >> > > >> Anyway, it was great to have a solution easily at hand ;-) > > >> > > >> Best, > > >> Maria > > >> > > >> > > >> <Bildschirmfoto 2020-05-13 um 13.58.59.jpeg> > > >> > > >> <Bildschirmfoto 2020-05-13 um 14.08.53.jpeg> > > >> > > >> <Bildschirmfoto 2020-05-13 um 13.59.30.jpeg> > > >> > > >> > > >> > > >> > > >> > > >> _______________________________________________ > > >> Qgis-user mailing list > > >> [email protected] > > >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > > >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user > > > > _______________________________________________ > > Qgis-user mailing list > > [email protected] > > List info: https://lists.osgeo.org/mailman/listinfo/qgis-user > > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user >
_______________________________________________ Qgis-user mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
