Yes I mean warp. And sorry, I misread that part about the scaling. What you are showing in your screenshot is exactly what I experienced before I wrote this tutorial. Are you sure you are warping to the right target CRS? It should be EPSG:3857 - WGS 84 / Pseudo-Mercator. But now that I think about it, I don't really remember if I solved it only by warping... Did you take a look at your .ASC file with a text editor? Does it look like the image I put in the tutorial? Maybe the cell size is wrong?
Yes, I did everything you mentioned. Anyway, instead of spending hours trying to find the error and then solve it for each of my 1,016 tiles, I decided to just redo the entire LiDAR process, this time following your tutorial instead of the masterclass which also was problematic last time.
I also used this video by ThatTrainGuy along the written tutorial of Lulon here. Important difference to take attention of (and the author forgot to explicitly mention) is that you can't use the EPSG code of 4326 he used in the video. This is the EPSG code for his Lidar data in Sydney, Australia. One user already did that wrong in the past following this video. And that's something new users quite often confuse. You need the correct EPSG code for your LIDAR data, not the EPSG code of someone else's project/Lidar data! You usually can find the EPSG code anywhere close where you got the Lidar data from. This is also something I think isn't exactly pointed out here in the written tutorial. So be careful of this.
Using Lidar is not mandatory for creating route? If lidar data not exists for my area, can I skip it and use SRTM instead?
Yes it just means your terrain will not have quite the same level of detail but there’s nothing to stop you modifying the landscape until you have it sculpted close enough to the real thing.
