"T i m" wrote in message
...
On Thu, 4 Feb 2016 16:30:08 +1100, "Rod Speed"
wrote:

snip

Go on tomtom and report it as an error.

Not for me to do is it,

Corse it is when its you that has to come out at 2am to avoid
them demolishing any more private cars getting out.

Well, it has been a dead end now for probably longer than domestic
GPS's have existed so I have no idea why they are ending up down here.

What's its name so I can look at it with google maps etc ?

The only reason I can think of (other than the lorry drivers not
reading the GPS correctly) is their map detail is sufficiently low
to not cover these sort of back roads accurately?

They shouldn't be looking at map at all, just following the
turn by turn instructions. Maybe that is misleading there,
I have sometimes found that when there are a couple of
turns close together that it is possible to turn down the
wrong one in the dark even with the recent approach of
saying the name of the street because the name means
nothing to you when its in the middle of a trip etc.

although I have a TomTom and think I've registered it so maybe I could?

You don't need to be a registered tomtom owner to do that.

So anyone could submit anything to them?

Yes, and they allow for that by checking whether
the amendment makes sense using other data etc.

So does google.

I find some changes happen almost instantly, so fast that
I kick myself for not checking the map more frequently.
Not such a problem now that they send you an email
when the change has happened and it often takes a
few hours before the change is visible on the map itself.

But sometimes it can take months for some reason.
Not at all clear to me why one took months. That one
was in fact a spelling mistake in the street name that
crept in somehow and took months to get fixed. It
used to be called Snaidero Rd, got mangled into
Snaldero Rd, took months before they changed it
back to the correct spelling, Snaidero Rd again.

Maybe that happened at the official level with the
local council doing the error and it took a long time
before that got fixed at the local level or something
because the error showed up on both google maps
and apple maps. And still hasn't been fixed on apple
maps.