Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

Because you are using the ee.Image.and() method in your cost calculation, the resulting cost variable is binary. That is why the results seem non-sensical. The units of the output of ee.Image.cumulativeCost() are the cost input parameter's unit multiplied by a unit of meter. You can test this by examining the result of a unit cost input (script link). So to ...


The formulae in wikipedia and the R doc are identical, lets see what they say walking speed is on flat ground: > tobr = function(m){6 * exp(-3.5*abs(m+0.05))} > tobr(0) [1] 5.036742 About 5 units. Is that km/h or m/s? If it was 5 m/s that would be 5 * 3600/1000 = 18 km/h. That's a pretty quick running pace, never mind walking. So I think gdistance ...


The results of these functions are not trivial to mentally visualise as they are based on transition matrices, but consider this toy e.g.: N.B. i'm using a projected coordinate system, British National Grid, to simplify things a bit as geoCorrection will begin to take into account north/south & east/west distortions of latlong rasters by using great ...


I found two possible workarounds: Update to QGIS 3.4.1. For QGIS 2.18: In the r.walk.points tool, use "GRASS GIS 7 region extent" to manually select an area that is smaller than the input slope raster. However, I'll leave this question open in case someone finds a real answer.

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