[GraphHopper] Looking for an engine for horse (and hiking) routing

[Nop]

Hi!

> Ah, ok. Also putting parsing and storing the edges into two threads (+ a
> queue) could speed things up.

Yes, about 20-40% in my experience.

> Yes, that would be an option (for CH it won't work).

CH seems to be pretty cool, but maybe a slower algorithm will do for my 
usecase. For horse routes, the distance will never be more than 50km, 
more realistically are 30km between start and destination. What is the 
second best algorithm in your experience?

> Nice, have fun :) ! I've also created this contributing file:
> https://github.com/graphhopper/graphhopper/blob/master/CONTRIBUTING.md
>
> Let me know if you have questions!

I do! The issue #46 is fixed in my fork. I even read your info and 
extended the oneWay test to cover it. Actually, understanding the test 
was the hardest part. :-)

Unfortunately, 3 of the routing tests are failing now. I checked one of 
them, the input data contains several of the reverse oneways. So I 
believe that actually the test case was broken until now and the routing 
is got fixed.

But as I never looked at routing and don't have any way to visualize or 
check those routing tests, I can't fix the test cases. I guess I need 
your help for that.

Other than that I'd be ready to hand in the first fix. :-)


Oh, and I need help from you as list admin. I disabled the mails from 
the list to read at Nabble, but my posts from Nabble do not arrive at 
the list. Can you please reactivate the mails? I can't find the list 
settings, it only asks me to subscribe. :-(

bye, Nop