TransWikia.com

Cell Size and nonsensical results from GRASS r.walk

Geographic Information Systems Asked by ipsofactoid on May 29, 2021

I’ve been wrestling with two main problems the past six hours. I am using 30m resolution aster/srtm merged dem. When I use the r.walk function to calculate a walking time surface from a point, the output looks good, but when I check the values, they make no sense. That is, the time it takes to travel is way underestimated, often by a factor of 3 or more. I am assuming that the results are in seconds, so I divide that by 3600 to get the value in hours. Actually, given the terrain (Andes), the times are impossible because the velocity implied by the results is way more than 5km/hr (about 20km an hour). I tried using just the dem and setting lambda to 0 for the friction. I tried using a reclassed slope as the friction surface. Both yield similar results.

The second issue is that when I zoom in to check the cell size, it’s about 1.5km on each side! I don’t know how that’s determined because all the raster inputs are 30m resolution. The extent of the GRASS region isn’t that big, either. Maybe 150 by 150km. I can’t find any resources that address this issue.

One Answer

Ok, after hours of troubleshooting, I solved the issue. I started with a clean slate and made sure to set the region as the same extent as the DEM to begin with. The default values for the cell size resolution should be maintained.

Answered by ipsofactoid on May 29, 2021

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP