On Thu, Feb 14, 2019, 09:20 JeCh Just check https://www.waze.com/cs/livemap and you can see how wrong you
> are. The traffic information is available almost everywhere, if you have a
> good mobile connection.
>
This makes it unusable in most of the Americas, even in the US.
>
--
You received
Dne čtvrtek 14. února 2019 15:50:27 UTC+1 Paul Johnson napsal(a):
>
>
>
> On Thu, Feb 14, 2019, 03:45 JeCh
> wrote:
>
>> Osmand is perfect for bike and walking, can serve also in a car for very
>> short distances. But it doesn't make much sense to use it as a regular car
>> navigation. There
On Thu, Feb 14, 2019, 03:45 JeCh Osmand is perfect for bike and walking, can serve also in a car for very
> short distances. But it doesn't make much sense to use it as a regular car
> navigation. There are much better navigation apps.
>
I dunno about better. Certainly faster. But it is
Am 14.02.19 um 15:03 schrieb 'Xavier' via Osmand:
> On Thu, Feb 14, 2019 at 01:45:35AM -0800, JeCh wrote:
>> If you need an offline navigation, the best free option is Mapfactor
>> Navigator.
>
> FWIW, I looked at it on the GPlay store. The listing also includes this
> text: "Contains ads".
>
>
On Thu, Feb 14, 2019 at 01:45:35AM -0800, JeCh wrote:
If you need an offline navigation, the best free option is Mapfactor
Navigator.
FWIW, I looked at it on the GPlay store. The listing also includes
this text: "Contains ads".
For me, at least, that is a huge "I will not touch it" red
Osmand is perfect for bike and walking, can serve also in a car for very
short distances. But it doesn't make much sense to use it as a regular car
navigation. There are much better navigation apps.
If you can use data, there is nothing better then Waze. It doesn't make
sense to think about
It depends on where you are and how active the local community is. Locally,
you can usually find new streets and addresses in OSM (and in OsmAnd) first.
On Saturday, 26 January 2019 15:00:20 UTC+1, Tom Norton wrote:
>
> OP here. Yep I have to agree about addresses. It seems like we can only
>
I wouldn't give up my Garmin Nuvi. Information is more accurate, substantially
quicker to use to find an address. Address information in Garmin is generally
spot-on, same cannot be said for Openstreet mapping.
Garmin speed alerts are so useful if you miss a speed sign, or in case you are
IMHO:-
1. For off-road (Walking/River/etc), or for on-road cycling, or for
driving in rural areas where traffic is not a factor, OsmAnd absolutely
wins hands down every time.
Why? - (a) Map detail, (b) map currency, (c) works offline, (d) uses
less battery, (e) more customisable
On Tue, Jan 15, 2019 at 08:59:53AM -0800, Leo wrote:
1, changing lanes,
AndOSM+ has sort of lane directions, but not accurate, not prompt
This can also be due to lack of detail in the OpenStreetMap data for
the particular road. And, if that is the case, you can add the data to
OpenStreetMap
You must mean OSMAnd+, not AndOSM+ .. :-)
OSMAnd navigation is designed as offline navigation
and cannot be in real-time aspects fairly compared to online navigations
with realtime features, like Google maps or Waze.
Even its 3rd party online routing services do not provide real time
Have AndOSM+ / iGo + Here maps / Oruxmap in US, installed in the same
Andoid phone
For car navigation, AndOSM+ has improved a lot, seems to be very promising.
I guess it'll take 1-2 years to catch iGo.
1, changing lanes,
AndOSM+ has sort of lane directions, but not accurate, not prompt
iGo and
Strange...my last response got deleted somehow.
Anyway, in routing.xml, I find these entries:
select value="$maxspeed:practical" t="maxspeed:practical"
select value="$maxspeed:advisory" t="maxspeed:advisory"
select value="$maxspeed" t="maxspeed"
I interpret those to mean that maxspeed:practical
It's been several months since I last looked at the routing.xml file, but
as I recall, it appeared to recognize maxspeed:advisory=* and
maxspeed:advised=* if and only if maxspeed=* was absent.
IIRC, it also recognized maxsped:practical=* but I don't recall if that was
only in the absence of
For some reason, my replies to this thread are being deleted
In routing.xml, I see maxspeed:practical, maxspeed:advisory, and maxspeed.
My take is that OsmAnd uses them in that order, with the later ones taking
precedence over an earlier one.
jack
--
You received this message because
Paul Johnson writes:
> On Fri, Dec 7, 2018, 09:27 Greg Troxel
>> Paul Johnson writes:
>>
>> I see maxspeed:typical as being for the flow of mixed traffic that is
>> being reasonable.
>
> Not sure this is a tag we even need in this case, since it can be inferred
> automatically from the GPX
"'Xavier' via Osmand" writes:
> On Fri, Dec 07, 2018 at 10:01:15AM -0500, Greg Troxel wrote:
>>Then there is maxspeed:typical.
>
> The OSM wiki has no reference for maxspeed:typical. It does have
> maxspeed:practical
> (https://wiki.openstreetmap.org/wiki/Key:maxspeed:practical). Perhaps
>
On Fri, Dec 07, 2018 at 10:01:15AM -0500, Greg Troxel wrote:
Jack Burke writes:
OsmAnd does use maxspeed:advisory when just plain maxspeed=* is
absent. Has used it for a while now.
But what about when both are present?
In the US, we have the situation where on ramps (link roads, slip
Paul Johnson writes:
> Seems like for route planning, the safe bet would be worst case scenario,
> lowest speed of the three possible maxspeed values. For example, a
> mountain road that (mostly motorcycle) traffic typically whips through
> curves at 70-90 km/h in a 110 km/h zone and have
Seems like for route planning, the safe bet would be worst case scenario,
lowest speed of the three possible maxspeed values. For example, a
mountain road that (mostly motorcycle) traffic typically whips through
curves at 70-90 km/h in a 110 km/h zone and have advisories (which are set
assuming
Jack Burke writes:
> OsmAnd does use maxspeed:advisory when just plain maxspeed=* is
> absent. Has used it for a while now.
But what about when both are present?
In the US, we have the situation where on ramps (link roads, slip roads)
the regulatory white sign will be the one from the highway
OsmAnd does use maxspeed:advisory when just plain maxspeed=* is absent. Has
used it for a while now.
-jack
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I was a hold out for quite a while.
Finally got a smart phone last year.
One of the first apps I fell in love with is OsmAnd 2.8.2.
The app is now up to 3.2.6.
And lately I've experimented with Cruiser 1.4.30.
Cruiser is interesting in that it answers the question
of how simple can an app be and
> offlist since this is getting to nits.
Sorry; the list appears to be seriously misconfigured :-(
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
"'Xavier' via Osmand" writes:
>> But, my point is that for a motorway_link, for routing purposes, it
>> is not reasonable to assume 65 mph as the speed. 30 mph is a far
>> better assumption in terms of causing the chosen routes to be sane.
>
> Agreed. Doing nothing more than using maxspeed/2
Are eventual extra Garmin features never used ?
Is the way OSMand works
preferred to Garmin one ?
If both answers are yes for you
then the answer to your question for yourself can be yes.
The answer depends on personal preferences.
I guess the word totally is overused these days
and its
On Tue, Nov 20, 2018 at 06:49:01PM -0800, A Thompson wrote:
I can compare OsmAnd with TomTom (not Garmin) and lots of Android
apps. In the UK I still need TomTom because it gives very good
guidance on what lane to be in when you're in an unfamiliar place.
It's not OsmAnd's problem:
I can compare OsmAnd with TomTom (not Garmin) and lots of Android apps. In
the UK I still need TomTom because it gives very good guidance on what lane
to be in when you're in an unfamiliar place. It's not OsmAnd's problem:
OpenStreetMap mappers for many UK places haven't described the lanes in
On Tue, Nov 20, 2018 at 06:01:21PM -0500, Greg Troxel wrote:
"'Xavier' via Osmand" writes:
On Tue, Nov 20, 2018 at 04:59:42PM -0500, Greg Troxel wrote:
Relative to a Nuvi, negatives for OSMand are:
- some goofy routing, due to wrong assumptions in osmand about how
long things take.
"'Xavier' via Osmand" writes:
> On Tue, Nov 20, 2018 at 04:59:42PM -0500, Greg Troxel wrote:
>>Relative to a Nuvi, negatives for OSMand are:
>>
>> - some goofy routing, due to wrong assumptions in osmand about how
>>long things take. Specifically:
>>
>>* some issues where _link roads
On Tue, Nov 20, 2018 at 04:59:42PM -0500, Greg Troxel wrote:
Relative to a Nuvi, negatives for OSMand are:
- some goofy routing, due to wrong assumptions in osmand about how
long things take. Specifically:
* some issues where _link roads without an explicit speed get
treated at
I used to use a low-end Nuvi in the car, and have switched to using
osmand, even though I still have the nuvi (with osm via mkgmap)
someplace.
Relative to a Nuvi, negatives for OSMand are:
- no way to get traffic data (or if so I don't understand how)
- some goofy routing, due to wrong
Op 20-11-18 om 21:41 schreef Tom Norton:
I guess the Subject says it all! Just wondering.
Absolutely. The power and flexibility of OsmAnd are awesome and
unchallenged.
From ergonomic point of view, strictly for car use only, I'd prefer a
"Go Home" button. Now you have to dig into your
I guess the Subject says it all! Just wondering.
--
You received this message because you are subscribed to the Google Groups
"Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to osmand+unsubscr...@googlegroups.com.
For more options, visit
34 matches
Mail list logo
