Messages

> PS: Ich habe gerade entdeckt, das im Car-Modus sogar die Abbiegevorschriften beachtet werden.

Achtung: im speed modus nicht, im flexibility modus aber schon (setCHEnable(false)). Auf Android kommt aber eigentlich der speed modus zur Anwendung d.h. es sollte eigentlich gar nicht funzen ...

Achso, 'fastest' ist tatsächlich etwas missverständlich. Generell ist es nicht unbedingt 'schnellste' sondern eher 'best guess' er nimmt auch infos über offizielle Radwege mit rein und versucht da lang zu routen auch wenn es etwas Umweg ist. Und wenn man Höhendaten mit reinnimmt vermeidet er noch Berge (aber das ist ja auch 'schnell'

Bei Fuß ist das ähnlich.

Eine pure 'schnellste' könnte man aber leicht bauen ...

Was genau kannst Du nicht nachvollziehen?

Diese Route hier?

https://graphhopper.com/maps/?point=52.414566%2C13.648453&point=52.501594%2C13.246078&locale=de&vehicle=bike&weighting=fastest&elevation=true&layer=TF%20Cycle

Just keep in mind: the master on github is 0.6 but is unstable and you should use the stable 0.5 and switch only 0.6 if you know what you do or for a development version of the add-on or similar

@menion: it looks like the compilation needs more memory, I got similar problems on a dev machine although enough RAM was available. Try MAVEN_OPTS=-Xmx200m or more MB

> Locus force closes when using GH (0.1.7) for navigation.

It is important that you create the data with the same GraphHopper version that is used for the locus add-on.

GraphHopper 0.5 released a few days ago and this is incompatible with older versions. You should try to switch to the 0.4 branch to create data for the locus add-on I guess, or update the add on to the latest version (it is open source too).

Try:

Code Select Expand


git checkout 0.4
./graphhopper.sh clean
./graphhopper.sh import your-area.pbf


> Schade, daß sowohl GraphHopper als auch BRouter die Android device möglichkeiten eher als Nebenprodukt sehen.

Also wenn Ihr uns das finanziert ändere ich meinen Fokus sofort
Nein, also im Ernst. Android bzw. mobile generell vernachlässigen wir nur sehr ungern, Aber es ist aus resourcenmangel leider notwendig.

> Um so schöner zu lesen, daß Du anscheinend doch ein wenig Zeit und ein offenes Ohr hast um Dir ein Bild machen zu wollen.

Also auf der Mailingliste sind wir immer offen und mit mehreren Ohren an mehreren Orten zu lauschen ist ein bisschen schwierig, aber ich hoffe mal ich schaffe das halbwegs. Es gibt ja auch noch stackoverflow, osm help, osm forum, issue tracker etc

> Da ich in der Nähe der holländischen Grenze wohne, wäre es wünschenswert,
> wenn die Routenberechnung auch über die Grenzen des jeweiligen Routingfiles von Graphhopper möglich wäre.

Das geht aktuell nur wenn Du die beiden Gebiete ausschneidest und GraphHopper beim Import 'zeitgleich' vorlegst. Siehe https://github.com/graphhopper/graphhopper/issues/293

Hmmh, someone moved too many replies into a separate thread. Here is the link for reference: http://forum.locusmap.eu/index.php?topic=4742.0

For elevation nothing is necessary, just include srtm enabling in the config.properties. See
https://github.com/graphhopper/graphhopper/blob/master/docs/core/elevation.md

Peter

> osmreader.bytesForFlags is no more used

Where do you see this old option?

> but crashes during compilation due to no space on disk.

What do you mean with compilation? Compilation should be possible on <100MB easily
be it RAM or disc. GraphHopper is designed to be space efficient.

Or do you mean the import?

On the phone this is not surprising. Again: either switch profiles to speed mode (using latest version) and disable turn costs for car. Then even longer roads should take less than 20 seconds. Or vote for our very first issue here:
https://github.com/graphhopper/graphhopper/issues/1

> prepare.chWeighting=no

Yes, you are using the flexibility mode, probably to support turn restrictions for car and multiple vehicles. Still strange that it takes 15 minutes - or is it on the mobile device?

The good news is that we've released the first release candidate yesterday for 0.5 which supports multiple vehicles in the speed mode (but still no turn costs).

Hi,

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)


Regards,
Peter

Hi together,

author of GraphHopper here. I really need to read through this whole thread here now, but first of all: thanks to @menion for making this happen and for the others that you provided feedback etc!

Now regarding some points:
* indeed offline was not the main focus for me but this does not mean that you should not focus on it
* offline maps generation should be updated more often, more areas? I still cannot promise something here, sorry
* more profiles, different vehicles: we are working on this. E.g. more profiles are now possible with the speed-mode in a dev branch

@menion is your work open source or how others usually contribute to this? Regarding the some technically points: Do you start a web server on the device to serve JSON or how does this work?

I would really like to see this add-on for a broader audience, even more integrated and easier to setup. We've an Android demo which e.g. allows one to easily download certain maps, see the apk here: https://graphhopper.com/#community

How else do you think could we improve the installation procedure? And what are the 3 main pain points for you or most wanted features?

Regards,
Peter

[edit]

Hallo gynta,
bin der GraphHopper Autor.
Wie funktioniert das technisch, startest Du lokal auf dem device einen Server?
Und verwendest Du mit CH oder ohne? Z.B. sollte mit CH eine Tour über 250km schon funktionieren, dauert bei meinem älteren Gerät dann nur ein biscchen.
Auch wird es in der neuen Version mehrere Profile mit CH geben:
https://github.com/graphhopper/graphhopper/issues/464
Was wären Deine größten 3 Wünsche fürs on-device routing ?
Grüße

edit
Ah, da gibts ja noch nen größeren englischen Thread und menion ist der Autor des add-ons. Hab da auch mal nen reply verfasst...