Messages

thanks jusc. It's interesting that with mobac author, they discuss in just normal way. When someone from OSM discuss with me, it's usually with angry tone. Usually because Locus is also paid app and mobac no. Never mind, as I wrote before. I disabled direct downloading from OSM Classic. No other choice.

I was also (about a month ago) trying to set own tile server, but current server I use for vector map generating and rendering is not enough powerful for this task. I have to think about it a little and maybe I'll buy for locus users some more powerful tile server ...

jo děkuju . když mapy pojemuješ x.osm.map tak to bude ok. jinak opraveno a v další verzi to už bude správně. díky

viewtopic.php?f=10&t=1166

these maps are in some location map projection (together with specific url to tiles) so this is not possible to simply add to Locus. Question is also terms of use of this map. If they offer WMS server, that's best way how to add special maps

fine, donation to OSM sended http://donate.openstreetmap.org/comments/, downloading OSM classic disabled, now contact someone from admins ...

ah damn, thanks, that's it. I'm simulating it at home with some constant speed ... thanks

I don't know how this can be possible ...

http://grant.dev.openstreetmap.org/tmp/ ... ek-20k.txt

but locus is still in top ten downloaders from osm server. So since next version downloading from base osm server will be removed. this is not a problem. For downloading are much better servers. Mainly MapQuest

yes, I'll write to some OSM admin. Hope that someone cracked locus and download with this version more then is limit ...

hmm nice ... from irc.openstreetmaps.org, I went to http://wiki.openstreetmap.org/wiki/Blocked_applications .. Locus in list, ach ... what the ..

Discovered an error in the new navigation status line with the two user selectable fields:
- If I select "Time of arrival", it displays "Unknown" until I reach the destination whereupon it displays a time that makes no sense to me.
- If I select "Time to target", it displays "Unknown" until I reach the destination whereupon it displays a huge integer number with more than 8 digits.

I am assuming these fields are supposed to display the estimated time of arrival, not the actual time spent calculated after arrival.

What is the estimated arrival time based upon - speed limit on the streets chosen in the calculated route or an actual average speed the last minutes? The first one is what is used in other navigation apps. In that way you get a time even before you have started moving.

hmm, when I'm trying it home, I cannot achieve weird values! As I wrote before, unknown values are there because speed information aren't in data from MapQuest (but are in Cloudmade - damn). What can I do to get this error? Did this happen to you only when you're out?

ok guys, I'll try to optimize it in some way (hmm don't know if this will be possible ... we'll see)

at delam co delam, nepadne ... takze logcat nebo vypozorovat duvod

Sent from my GT-I9100 using Tapatalk

no zoom 16 je dostupný jen v Praze, jinde ne. To musím napravit protože "neznámý problém" je špatně vypsaný text, mělo by tam být neexistuje. Můžeš to srovnat se zéémy přímo na cykloserveru, kde to bude to samé. Pro verze v tomhle směru tedy určitě nepomůže ...

that surely not. There is no chance to reduce some computation. It's just one test ...

is there so big difference between navigation and track recording in battery life?

svart: there are some missing info in MapQuest data and some in CloudMade, that's why you see 'Unknown' text. But thanks, I'll look at it. It have to show correct value for whole navigation

tusor: no, compare is not yet ready but will be. For now, you have to check on your own. Main difference is that every server use different algorithm to compute route, so if should navigate you on other ways

stebu: please share with me start and end location and type of navigation (car fast, etc..). Small mistakes are also important so I have to check if this is problem in locus or in data

and about autozoom ... .. I know that it need some improvements to be fully functional also during navigation. In future for sure!