I don't like Waze at all. But that's personal. But when I use Google maps and Android auto I get weird routes sometimes.
I too have recently recieved daft route plans in rural areas via Google Maps - both when going on holiday in the SW and more locally when looking for cycling routes in East Anglia.
These included:
1. Taking me down single track (but unrestricted for speed limit) farm tracks.country lanes for the holiday trip when there was no way I could (safely) do 60mph on such road;
2. A cycling trip that the mapping said I couldn't cycle down a road I've gone down several times, yet you can drive down it (it's a reasonable and reasonbly safe B road through a small village). However much I try and force Google Maps to take me down teh road, it diverts the route or doubles back.
Sounds like the OP's Waze mapping service is either using similar software or both using bad data. On the other hand, my otherwise 'defunct' (no traffic levels/accidents/dealsy info available) satnav app on my 'old' Windows Phone, HERE Drive (Maps) still gives the route as it should.
The roads in the area haven't changed in a long time, so that can't be used as an excuse for the satnav providers.
|
|
<< Taking me down single track (but unrestricted for speed limit) farm tracks.country lanes for the holiday trip when there was no way I could (safely) do 60mph on such road >>
Andy, it is silly of you to suggest that the lack of a speed limit could imply that it might be possible to drive at the NSL. Limits were originally intended to protect urban areas (and have recently expanded to cover main roads almost anywhere) but it was never suggested that the posted speed might be sustainable. The limit merely shows that you might be penalised for exceeding it.
Doing 60mph on single-track country lanes would be looking for serious difficulty IMHO ?
|
<< Taking me down single track (but unrestricted for speed limit) farm tracks.country lanes for the holiday trip when there was no way I could (safely) do 60mph on such road >>
Andy, it is silly of you to suggest that the lack of a speed limit could imply that it might be possible to drive at the NSL. Limits were originally intended to protect urban areas (and have recently expanded to cover main roads almost anywhere) but it was never suggested that the posted speed might be sustainable. The limit merely shows that you might be penalised for exceeding it.
Doing 60mph on single-track country lanes would be looking for serious difficulty IMHO ?
Before you make such remarks, I'd strongly suggest you re-read my comments first.
I was saying precisely that there was no way I could safely do 60mph despite the road being derestricted (i.e. legally allowed to do up to 60) meant that the shorter length of that route was more than offset by the much slower speed I ended up doing to be safe.
Given Google Maps did not know that (it's 'just a road' to it's software) meant that the calculation did not give a realistic journey time, nor did it account for knock-on problems like damage via having to squeeze up against hedges, branches from trees, etc in order to let oncoming vehicles pass.
Some country roads are wide enough (the start of this one was) to safely allow high-er speeds, but the I wrongly assumed the software knew this when obviously it didn't and was just guessing. I had no time to check its validity, especially as my 'run-through' before stting off hours earlier had not directed me that way. I assumed it was because of some incident ahead, but apparently there was none.
|
|
I've found both Waze and Google Maps very accurate for journey time estimates although dramatic congestion impacts change them of course.
I infer they are both fairly smart regarding average speeds on routes and don't just assume e.g. that all NSLs can be driven at 60/70.
Of the two I prefer Google. Both are usually super reliable but deteriorate significantly without a good data connection. Recently Waze was acting the goat and I switched to Google which was also slow and intermittently unresponsive, I always have offline maps installed for Google but there's only so much it can do without traffic and road closure data.
|
|
|
|
These included:
1. Taking me down single track (but unrestricted for speed limit) farm tracks.country lanes for the holiday trip when there was no way I could (safely) do 60mph on such road;
Google maps won't expect you to do 60mph on the road - it will know the average speed on that section of road. Usually on roads like that you can cathc up time if you can (safely) push on with your journey.
|
These included:
1. Taking me down single track (but unrestricted for speed limit) farm tracks.country lanes for the holiday trip when there was no way I could (safely) do 60mph on such road;
Google maps won't expect you to do 60mph on the road - it will know the average speed on that section of road.
How? I'd never used it before and it took slightly longer (time-wise) than the route I otherwise would've taken, because of having to slow up significantly for sharp, blind bends, oncoming vehicles, sheep grazing near to the road on open fields, etc, etc. I probably averaged 30 or less over it.
Usually on roads like that you can cathc up time if you can (safely) push on with your journey.
Google Maps has never once tried to divert me down that road until this year, despite me going the same route (past it) over many years whilst going on holiday.
Hopefully it was just a 'trial run' that got false readings from someone who first tried it after being diverted off because of a traffic jam ahead on the normal route, and through my (bad) experience (and others, I suspect) learned not to do so again.
Of course, it didn't know, at least until I gave 'feedback' on the journey as 'directed', that my car now has a few more scratches on it as a result.
|
These included:
1. Taking me down single track (but unrestricted for speed limit) farm tracks.country lanes for the holiday trip when there was no way I could (safely) do 60mph on such road;
Google maps won't expect you to do 60mph on the road - it will know the average speed on that section of road.
How? I'd never used it before and it took slightly longer (time-wise) than the route I otherwise would've taken, because of having to slow up significantly for sharp, blind bends, oncoming vehicles, sheep grazing near to the road on open fields, etc, etc. I probably averaged 30 or less over it.
Usually on roads like that you can cathc up time if you can (safely) push on with your journey.
Google Maps has never once tried to divert me down that road until this year, despite me going the same route (past it) over many years whilst going on holiday.
Hopefully it was just a 'trial run' that got false readings from someone who first tried it after being diverted off because of a traffic jam ahead on the normal route, and through my (bad) experience (and others, I suspect) learned not to do so again.
Of course, it didn't know, at least until I gave 'feedback' on the journey as 'directed', that my car now has a few more scratches on it as a result.
How will Google know the average speed on that road? They get data from everyone who drives down that road with Google Maps and have allowed tracking. I would have thought the road you used before was busy so Google Maps diverted you - so would have been quicker than had you stayed on the route. It does not need to wait until it has feedback from you though so will have known...it's how they work, they don't need to rely on manual feedback from a user.
|
These included:
1. Taking me down single track (but unrestricted for speed limit) farm tracks.country lanes for the holiday trip when there was no way I could (safely) do 60mph on such road;
Google maps won't expect you to do 60mph on the road - it will know the average speed on that section of road.
How? I'd never used it before and it took slightly longer (time-wise) than the route I otherwise would've taken, because of having to slow up significantly for sharp, blind bends, oncoming vehicles, sheep grazing near to the road on open fields, etc, etc. I probably averaged 30 or less over it.
Usually on roads like that you can cathc up time if you can (safely) push on with your journey.
Google Maps has never once tried to divert me down that road until this year, despite me going the same route (past it) over many years whilst going on holiday.
Hopefully it was just a 'trial run' that got false readings from someone who first tried it after being diverted off because of a traffic jam ahead on the normal route, and through my (bad) experience (and others, I suspect) learned not to do so again.
Of course, it didn't know, at least until I gave 'feedback' on the journey as 'directed', that my car now has a few more scratches on it as a result.
How will Google know the average speed on that road? They get data from everyone who drives down that road with Google Maps and have allowed tracking. I would have thought the road you used before was busy so Google Maps diverted you - so would have been quicker than had you stayed on the route. It does not need to wait until it has feedback from you though so will have known...it's how they work, they don't need to rely on manual feedback from a user.
Presumably at some point someone had to be the first user down that road and to the destination I was going to. That could've easily been me. The 'delay' on the normal route was minor roadworks that weren't delaying traffic much as it was well after the slip-off from the main dual carriageway onto the local road to join the trunk road going the other way. Ironically I was also 'delayed' when rejoining the main trunk road via the 'short cut' because of the normal traffic level and speed of vehicles on that road.
There's a junction where occasionally a slow vehicle at the front cannot get onto the faster moving road and may have contributed to a 'delay' that in reality was intermittant. There's also a local alternative route that only adds a minute to the journey. Because of the extra danger and my unfamiliarity of the mapping route, the Google Maps route took me longer than I have done via the normal route in the past.
Hopefully Google Maps learned from my experience, one way or the other. Hopefully all satnav systems learn, though I suppose it's more difficult when driving on spa***ly used roads, especially if locals (including those operating farm vehicles and [say] riding horses) are using satnavs and thus the system has no idea why a delay has occurred, or whether the driver was driving at a safe speed for the road/conditions.
|
|
|
|
|
|
