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

[Nop]

Hi!

Some progress. I got the import to run in IntelliJ on Windows and I'm 
watching how it is building the graph. Did not get around to look at 
routing. But here's the first questions: :-)

1. What level of refinement does the OSMReader have? I think I spotted 
some potential for optimization and I might have some suggestions to 
speed up parsing from the experience with my own compiler.

2. It seems that nodes are only stored as lat/lon combinations. There 
are many route-blocking barriers like gate, lift_gate, cycle_barrier or 
bollard in the OSM data. Are they ignored or am I missing something?

3. Osm also marks Reversed Oneways with oneway=-1. Weird concept, but 
used over 120000 times. It appears that the AcceptWay does not recognize 
this?

4. The speed value is determined when creating the graph. Usually I 
would expect to have different speed profiles e.g. for trucks or cars 
that can be selected at runtime. Determining speed for horses is even 
more dynamic. Does it have to be encoded into the graph or is it also 
possible to calculate it at a later time?

5. How would you start adding elevation data? I noted that there is a 3D 
Graph class, but it looks like a stub. It appears that the Graph is 
intended to be built in one pass so the information would have to be 
integrated immediately, correct? Also added a comment to the issue #43

6. If I want to contribute some code, how would I do that? Please 
remember that I have no idea how GIT works, and I don't want to start by 
breaking things.


bye, Nop