(Hint: first read, then install. Maybe you won't need this tool at all)
Since my last holidays again resulted in tons of gpx-logs, I once more looked for a way to reduce the time I spend tracing them. Last year I tried Average tracks but wasn't too satisfied although I can't recall now exact reasons.
Nevermind, this year I remembered having read on the german weekly OSM notices about osm-makeroads.
The readme seems helpful at the first sight but (at least for me) there were some traps. Since R complained about some missing stuff, I had to install additionally libproj-dev and gfortran. The installation of tools at debian is the following: apt-get install libproj-dev gfortran r-cran-maptools gpsbabel libgdal-dev
The command of the readme to install the R-libraries did not work on my system. I figured out I could successfully install them as user by opening the R shell (by typing "R" in a terminal emulator) and installing the libraries one by one with these commands:
install.packages("princurve",dependencies = TRUE)
install.packages("rgdal",dependencies = TRUE)
install.packages("geosphere",dependencies = TRUE)
Now I could run the script. Only - how...?
First, I saved the files in a folder where I store binaries and scripts, let it be /bin here.
A bit googling and guessing gave me the line with which the script starts:
R -e "source('/bin/process.R')"
Now it complaints that it cannot find makeroads.R, so I substituted the path to the location of makeroads.R
Now I could finally run the program. Yeah! But I was a little surprised to find out it calculates only ways it can fetch for a defined bounding box from OSM. (Yes, you may call me an unalert manual reader.) Since the calculated result looked good I decided to go on since I invested quite some time already.
In process.R there is also defined the bounding box for which the script fetches the gpx data. One region with untraced logs was near Logatec. To get the four coordinates I took the changeset url, but the export-tab is just as useful. Be aware that in the file the order of the coordinates is not the OSM default left-top-right-bottom.
osm-makeroads needs quite some time to calculate average ways. Multithreading is not possible. For the above mentioned bounding box the calculation took about 18(!) hours with a AMD Phenom II X2 550 Processor - and then there was a power outage. sigh
I will not give it a second try.
Conclusion: osm-makeroads is for me not really helpful.
(edit) As I wrote this entry the bounding box contained 2,9 MB of gpx data with 22342 trackpoints. Here the file with that data.