thanks again for the feedback.
@menion: thanks for making this open source! I've added a link to the code in the Android section, maybe we get someone interested in this too:https://github.com/graphhopper/graphhopper/blob/master/docs/android/index.md#locus-add-on
> my major problem is compiling of add-on
Sorry I'm not deep into Android or gradle
> inability to route over more files
That is already known but not on our soonish todo list:https://github.com/graphhopper/graphhopper/issues/293
> 4. one last big issue for me as user ... I see here solution by creating own FlagEncoder with possibility to dynamically enable/disable certain osm tags.
That is our top prio issue after 0.5 release and we'll hopefully have it in ~October
> Anybody succeeded to run graphopper.sh on Windows?
This should be possible via cygwin. See e.g.https://github.com/graphhopper/graphhopper/issues/449
And yes, the most things are known and we have to do a proper queuing
For example the turn instruction are currently too simplistic and only show up when some street properties change but this heuristic could create also too many instructions. But we have this on the high prio list!
> using own data set it took about 15minutes compared to menion's set which took about 5 minutes.
Maybe you disabled the speed mode? (prepare.chWeighting=no)
Without the speed mode the queries for routing can take longer BUT 5 minutes is definitely too long! E.g. through whole Germany it should be a few seconds even without the speed-mode, make sure you use the in-memory settings for higher speed (taking more RAM)