Messages

Seems that bicycle fast, bicycle short and foot work but car modes don't work.
Where does the text "moto_car" come from? Yes, I mean exactly the bad spelling which should obviously be "motor_car"!

Hi,

yes, you're right, there's a spelling-bug, it should be "motorcar", not "motocar". This is sent by locus.

The bike and foot-modes work fine for me as well, thanx Menion for putting that in.

However, there seems to be some confusion on the mechanism I'm using to handle the configuration. I could have made the quick-start easier by deploying a standard-mapping, but I decided not to do that because this flexibility in configuration is a main feature of brouter so it's important to realize that there is a mapping and that there is more configuration on the brouter side.

An important thing to notice is that also a list of nogo-points is part of that configuration. So if, before pressing the "server-mode" button, you confirmed one or more nogo-points, they will become part of the routing-modes you select in the next screen.

Hmm local http server is quite crazy idea, but it should work and should be quite easy then, to add it directly to locus.

Hi Menion,

no, local http doesn't really work because I don't have enough control on process lifecycle. Android is shutting down my service sometimes, limiting the usablility.

This idea is just one step towards integration, because it was easy to do. What I want to achieve is to define an offline routing interface that is open on both sides (=allows to exchange the router as well as the map tool), that fits into the android programming model (=router is started implictly by the requesting maptool, no lifecycle issues) and that transports more information (=router gets e.g. moving direction, map tool gets e.g. voice navigation hints in addition to plain track)

However, my Android knowledge ist still very limited, so any help is appreciated.

regards, Arndt