Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - michaelbechtold

#1246
Even my old HTC Desire running Froyo can now run Locus again. Incl. vector maps of Germany. Well done.
#1247
@silber1: Locus allows more than one directory with maps, on internal and external SD. I have four of them I think. For .map files and sqlbd.
Go to map management - there you find "add map" function with navigation
#1248
Hi Menion,
I followed a GPX track of about 80km. Worked so far. However, the estimated time oscillated between 500 and 600 hours. While avarage speed was about 60km/h
No good maths :-)

edit
Another thing: traveling without data connection, searching for cities, towns and villages is a complete mess.
In particular as you cannot rely on bigger places being shown in a map (mapsforge problem I read somewhere else).
I recall you wanted to work on the POI DB stuff this summer.
So I hope you will include all Cities, Towns and Villages into your POI DBs. Perfect would be to include Streets, to. But that may become too big of a data set then.
#1249
@togtog: klappt es denn jetzt ?
Ich habe mir vor einem Jahr oder so BRouter einmal reingetan, aber irgendwann zur Seite gelegt.
Die v0.99, und vor allem der Artikel (link bei gynta-Post) haben mich bewogen es wieder zu probieren. Läuft wie geschmiert. Punkt zu Punkt (mit dem Routing aus Locus), aber auch mit via1 ... n, Ausschluss vor Gebiet etc. (mit speziellen POIs im POI-Ordner brouter, wie im Artikel beschrieben).
Letzteres ist vom Komplett-Handling hakelig, aber das wäre nur zu beseitigen, wenn die SW-technische Integration von beiden Seiten intensiver und enger wäre. Da aber beide Entwickler genug anderes zu tun haben, sage ich mir: das ist erst einmal eine Gewohnheitssache. Und von der Gesamtzeit einer Unternehmung / Reise ist das Routing ein minimaler Anteil.
Soweit meine Erfahrungen und Einstellung zum Thema. (Auch wenn ich mit Arndt beim Naming NICHT einer Meinung bin ;-)
#1250
Two remarks:
- I (well, my Galaxy Note) saw Locus Free / Beta update yesterday night in GooglePlay (so it must have been uploaded and available in principle), and update-all never came back (liky Gynta saw it, too). This morning it did work, though.
- I advise to tell in OFFICAL place IN CAPITAL, BOLD LETTERS, that in GooglePlay, YOU CANNOT FIGURE OUT IF YOU HAVE Beta in front of you. No current beta APK date, nothing. It is all hidden and implicit. And only AFTER install, you can find out what you got.

Once I got beyond that initially, last week, the updates work just fine.

Cheers
Michael
#1251
Hi all with beta trouble: I went through same issues myself, but in the end I got the beta to my Android:
1) register in thsi G+
2) wait to get admission to the beta program (!!)
3) then go to Google Play - but what you see looks foolish - it is old version from April 8th, HOWEVER
4) once I got it installed, it was in fact the desired beta version, 
5) the information pane shows v 2.20.2.2, but News only shows old, original April 8th version info
6) no ads, with Pro functionality until May 30th
Hopefully you can reproduce above.
Good luck
Michael
#1253
Navigation & Guidance / Re: BRouter Version 0.9.4 +
October 26, 2013, 12:45:56
It seems you broke the Locus integration. When starting the App, it requests from Orux stuff. Even after I gave the base directory with all brouter files in it (profile etc.)
Not good !
#1254
Hmm, I never enable Autoloading - but still I see no caching - let us double check the directory where caches should reside:
Locus/cache/images - containing files without extension, right ?

Quote from: menion on October 15, 2013, 07:36:41
that's correct, no caching if you have enabled "Auto loading". Anyway question wasn't if map are slow (we all know they're in certain levels), but question is whether they're slower then in previous version as @alex_dd wrote. I hope not
#1255
@Menion: On levels 9 to 13 Vector maps are still pretty slow. In particular as there seems to be NO caching for ALL of those levels.

Quote from: menion on October 14, 2013, 23:39:10
...
@alex_dd: online maps will be almost always little faster, mainly if you have area already cached. Anyway there should not be any slowdown of vector maps in last versions. Anyone experiencing some problems with speed of vector maps?
...
#1256
Navigation & Guidance / Re: BRouter Version 0.9.4 +
October 12, 2013, 21:40:08
WOOOWWWW !
You set the bar high for brenche ;-) !!

Quote from: KaHeMu on October 12, 2013, 17:01:16
Normally you're right. But next year I'll do a very long hike (about 2000 kms) and first I have to do is looking for a good and interesting way with some fix points for sightseeing or another things. The breaks or accommodation places I'll see from day to day.
Looking for the generally trek is a job where brouter and locus could help.

Kind regards,
KaHeMu
#1257
Navigation & Guidance / Re: BRouter Version 0.9.4 +
October 12, 2013, 15:43:07
I go by all three ;-)
My failed situation was > 500 km, and in all fairness, neither walking nor bicycle will allow 500 km IN ONE GO.
Even 200 km is pretty extreme for both, again, without a "via" target. You would typically target some place in between, right ? Drink, food ?
While for car, going to a place 100s of km away where you need directions is not unusual.
There are workarounds, yes. But why not have a proper solution rather than a workaround.
And why using yet another app in addition when it can be in one solution (Locus+brouter) ?
Cheers
Michael


Quote from: KaHeMu on October 12, 2013, 13:39:44
Quote from: michaelbechtold on October 12, 2013, 12:24:32
...

And for bicycle and foot path search, such single long distance searches do not make sense anyway (and you do not need to optimize for irrelevant use cases). For motorcar, the relevance is obvious. though.
TXs
Michael



This applies only for that people they aren't moving without a car. For car navigation there are special apps or devices to do very good job.
But there are many people outside which are moving by foot or by bike, often for long distances (>200 kms).

Just my 2 pence,
KaHeMu
#1258
Navigation & Guidance / Re: BRouter Version 0.9.4 +
October 12, 2013, 12:24:32
Well, one more question then: does brouter have a notion of highways ? So this partitioning would be INSIDE your app, not manual ! I.e. first search highway connections only near to start and end points, then get from those points to/from the valid entries to the highway system. Do not mind about "optimal" connections - this is an NP-complete problem beyond reach on smartphones ... ? By above searchtimes will really collapse automatically. For motorcar search.

And for bicycle and foot path search, such single long distance searches do not make sense anyway (and you do not need to optimize for irrelevant use cases). For motorcar, the relevance is obvious. though.
TXs
Michael

Quote from: abrensch on October 07, 2013, 13:32:32
Quote from: michaelbechtold on October 07, 2013, 12:21:30
Not sure if somebody reported already that 60000 ms (1s) are a too short timeout for brouter.
Just tried with a route from Frankfurt to Praha -> Locus timeout ...

Maybe you could make it a something like: timeout = (geo distance) * (configurable factor)

The timeout is important to protect the device. 60 seconds is the default, but there's a parameter in the aidl-interface, so it can be changed from outside.

However, the long-distance solution I am working on is "fast-partial-recalculation": the idea is that if a route to the same destination-point and for the same routing-profile is already known, a partial recalculation is done and the result is a combination of the old and the new calculation. This way you can do a long-distance calculation by starting the brouter-app, but then have fast recalulations if you follow the route and get off the track.
#1259
Navigation & Guidance / Re: BRouter Version 0.9.4 +
October 07, 2013, 12:21:30
Not sure if somebody reported already that 60000 ms (1s) are a too short timeout for brouter.
Just tried with a route from Frankfurt to Praha -> Locus timeout ...

Maybe you could make it a something like: timeout = (geo distance) * (configurable factor)

All this is brand new, and nobody knows yet, so this would allow to gain experience.
#1260
Navigation & Guidance / Re: BRouter Version 0.9.4 +
October 06, 2013, 23:03:43
All three modes documented above do work for me - however, bicycles and walkers are all sent to use HIGHWAYS ...
As Menion confirms he relays the selected mode to brouter via API, this should be a brouter problem then. I will try to report it to brouter support.