Who do I contact? Error in Map

 

This was actually told me by a neighbor... I'll post the entire story because it's that interesting.....

First, do a search to find this address on a GPS: 440 Crystal Tree Drive, Waynesville NC

If you then scan the map, you'll see that Crystal Tree Drive has 2 connections to Ned's Cove Road... One below us after 4 switchbacks, and one above us, off of Chipmunk Circle.

It's this upper connection of Crystal Tree Drive to Ned's Cove Road that is the issue:
IT DOESN'T EXIST!!! AND HASN'T FOR AT LEAST~20 Years!!!

History....
This road used to be a Fire Trail, before the Sub-division existed. It used to connect to the upper part of Ned's Cove Road, over a bridge over Beantown Creek on private land, and the lower entrance (With 4 switchbacks) didn't exist...

I'm being told that a 'Feud' Occurred with the owner of the lot where Crystal Tree Drive went over a private bridge over Beantown creek, to Ned's Cove Road, and the owner of the land that eventually became our development. The Feud got so intense that the owner of the bridge dynamited that bridge over the creek to prevent access to Ned's Cove Road, and the developer had to create the lower exit of Crystal Tree Drive to Ned's Cove Road via the 4 switchbacks.. !!!

No Such connection exists between the upper Crystal Tree Drive and Ned's Cove Road!!!!!

This is confirmed by Google Earth, but Garmin Maps say it's there ----- AND IT ISN'T!!

Now, with that story in place.... I'd like to submit it to the Map People to correct...... Who? Where?

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

Well ...

if you use BaseCamp there's a link to a map error form, or you can report it directly to HERE, who supply the Garmin maps

https://mapcreator.here.com/mapcreator/50.79289,-0.35507,10,...

or via

https://my.garmin.com/mapErrors/report.faces

(which is where you're taken from within BaseCamp)

--
Where there's a will ... there's a way ... DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20

Pain in the butt... They

Pain in the butt... They should let you post something without longitude, latitude, serial number, etc. I think I got through to support without serial number, which in my opinion, has no bearing on this whatsoever....

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

I submitted one email to

I submitted one email to Support for each of the GPS's I've seen it on.... 2689LMT, Nuvi 660, and Nuvi 50, and tried some emails from Garmin business site.

I think once before I tried to report a bug in maps, and gave up because of all the inconsequential information that they needed --- It was as if the Map People were trying to make it as hard as possible to submit something.....

If anyone has an email address I'd like to take the text from first post here, that explains it in detail, and email them directly.....

Thanks...

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

Map Creator

JanJ wrote:

This was actually told me by a neighbor... I'll post the entire story because it's that interesting.....

First, do a search to find this address: 440 Crystal Tree Drive, Waynesville NC

If you then scan the map, you'll see that Crystal Tree Drive has 2 connections to Ned's Cove Road... One below us after 4 switchbacks, and one above us, off of Chipmunk Circle.

It's this upper connection of Crystal Tree Drive to Ned's Cove Road that is the issue:
IT DOESN'T EXIST!!! AND HASN'T FOR AT LEAST~20 Years!!!

History....
This road used to be a Fire Trail, before the Sub-division existed. It used to connect to the upper part of Ned's Cove Road, over a bridge over Beantown Creek on private land, and the lower entrance (With 4 switchbacks) didn't exist...

I'm being told that a 'Feud' Occurred with the owner of the lot where Crystal Tree Drive went over a private bridge over Beantown creek, to Ned's Cove Road, and the owner of the land that eventually became our development. The Feud got so intense that the owner of the bridge dynamited that bridge over the creek to prevent access to Ned's Cove Road, and the developer had to create the lower exit of Crystal Tree Drive to Ned's Cove Road via the 4 switchbacks.. !!!

No Such connection exists between the upper Crystal Tree Drive and Ned's Cove Road!!!!!

This is confirmed by Google Earth, but Garmin Maps say it's there ----- AND IT ISN'T!!

Now, with that story in place.... I'd like to submit it to the Map People to correct...... Who? Where?

I live near Waynesville. I checked the Haywood County GIS and saw the location of what you are referring to. I fixed the north entrance of the road so it doesn't connect. It should show up on HERE.com's map in a couple of weeks.
Photo of the correction:
http://i347.photobucket.com/albums/p458/narvick81/crystaltre...

I fixed up the entrance and the switchbacks too.
The reason HERE maps had it connecting is because the Haywood County GIS shows it connecting. Usually, HERE gets its map data from local GIS sources. So in this case, it's the fault of the county smile (Apparently, they didn't take to kindly to the bridge being destroyed).

maybe got better

I submitted over twenty corrections years ago, during the Navteq period. They did not even move my submissions into the under consideration status. While a couple of the most grievous errors got corrected, I doubted it was in response to my submissions. But the web site appearance and behavior have changed a couple of times since Nokia bought the enterprise, and a change I submitted to here's mapcreator page early this year showed up on the online map within a couple of weeks, and actually showed up in a distributed Garmin map update one cycle later. As the error was a failure to show that you could cross over a divided road to get into a shopping center (stop light and all) and had persisted for many years, I'm pretty sure they responded to my fix.

Though I find the web site awkward, and not suitable for some types of corrections (don't bother with speed limits) I'm encouraged by some evidence that they are more likely to actually respond to corrections.

If you gave up years ago, try again, but make it something long-lasting and very clearly wrong.

I've not tried submitting error reports to Garmin.

--
personal GPS user since 1992

Map updated already at Google

Just looked at Google Maps and there is only one entrance to Crystal Tree Dr. on their map! One on the Southern end and NONE on the Northern end.

--
Metricman Nuvi 660, GTM-20 Traffic Receiver Nuvi 3597 GTM-60 Traffic Receiver Williamsburg, VA

Yes, that is exactly what I

Yes, that is exactly what I said!!!

Now look at same location on a Garmin GPS!!!

Thanks all for the input and help!!
This story was related to me by 'neighbor' a month ago when I picked up an 'uphill' neighbor and had GPS Destination loaded. This Neighbor told me the story, and it was 'un-belive-able'. I checked with another long time resident before posting... The bridge that was dynamited was said to be on 'private property', and it was that--that set off the feud. Road that became Crystal Tree Drive is a holdover from when it was a forestry road.... Or so I was told....
Truth is stranger than Fiction, isn't it?

If anything comes up from the sources I email'd and informed (some have bounced already!) I'll post...

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

Thanks so much!! (I'm new

Thanks so much!!

Could you explain what "Here" is? I thought Maps were Nav-something!

Also, may I ask what you fixed on Entrance and switchbacks? Is that why 'sometimes' GPS thinks I'm off road going up and down hill?

PS: I'm new in the area -- Purchased in 1998, moved here in 2015.

Now if we can get some rain... and get rid of those fires!!! The air here NOW is as bad as Chicago Air was!

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

a little history

JanJ wrote:

Could you explain what "Here" is? I thought Maps were Nav-something!

The Wikipedia history may be useful.
https://en.wikipedia.org/wiki/Here_(company)

To summarize
In the beginning Karlin & Collins
renamed Navigation Technologies Corp
renamed Navteq
Navteq was bought by Nokia, which named the operation Here.com
The Here.com operation was purchased by an automotive consortium including BMW, Audi, and Daimler without changing the name.

So you are right, but times and names moved on.

Not all Garmin mapping information, always, has come from this specific thread of companies, but they certainly have been the detailed US street map supplier to Garmin for quite a few years now, and much else besides.

--
personal GPS user since 1992

Info

JanJ wrote:

Thanks so much!!

Could you explain what "Here" is? I thought Maps were Nav-something!

Also, may I ask what you fixed on Entrance and switchbacks? Is that why 'sometimes' GPS thinks I'm off road going up and down hill?

PS: I'm new in the area -- Purchased in 1998, moved here in 2015.

Now if we can get some rain... and get rid of those fires!!! The air here NOW is as bad as Chicago Air was!

The wildfires over here are terrible because of the one burning at Lake Lure. It's so smoky!
Anyway, HERE (formerly Navteq) had the intersection of Crystal Tree as a 4-way with Ned Cove and Bugler's Trl, but the entrance to Crystal Tree is clearly *before* Bugler's.
(And - unlike the north entrance of Crystal Tree, this was HERE's fault as the Haywood County GIS had the intersection correct)
As far as the switchbacks go, the geometry was simply off a bit, so I corrected it to be more accurate. Yes, this may have been why the GPS sometimes thought you were a bit offroad, but after this correction gets integrated, you shouldn't have that problem anymore.

You're the Best!!!You know,

You're the Best!!!

You know, based on the "History" that I was told, I was a bit reluctant to post what I did -- the "History"... I wasn't certain that anyone would believe such a story!

Actually, this ex-Chicagoan has grown to love this area...

Now all we need is a good soaking rain... I had to pick up some contacts for wife in Silva recently, and there is something going on north of 74/23 by Silva.... Or the smoke from somewhere else was trapped in that area!

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

big and small

Every time you report error on map you have to remember, that it may take long time (even years) to see error disappear. Especially if it is some obscure, small street. They don't care that much. On the other hand all big roads are fixed quite fast, usually with next map update.

Well, maybe, but that

Well, maybe, but that doesn't prevent me from pointing out the problems, and trying to help!

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

I have reported problems...

...to Here (and Navteq) over the last several years. Some have been fixed fairly fast (I'm thinking about a state highway in KY that was incorrectly named) and a local street in my town that was incorrectly named. The local street didn't get taken care of for quite a while. It took probably three updates before it got taken care of; whereas, the state highway was taken care of in the next update. New ramps and that sort of thing on the interstates usually get on the next set of updates. Just kind of depends on how critical the map folks think it is.

--
It is impossible to rightly govern a nation without God and the Bible. ----George Washington

I just got the following email from Garmin!

From cartography@garmin.com !!!!

Location of Discrepancy:
Latitude: 35°34'32.5"N
Longitude: 83°03'35.4"W
Street Address: 942 Crystal Tree Drive
Nearest City: Waynesville
State: NC
Zip: 28785

Type of Discrepancy:
Error:

On City Navigator North America NT 2017.30. Northern end of Crystal Tree Drive shows connecting to Ned Cove Road in Waynesville NC. Crystal Tree Drive does not connect at the northern end to Ned Cove road and actually ends at about. 35°34'32.5"N 83°03'35.4"W nearest address via google 942 Crystal Tree Drive Waynesville NC 28785

Thank you for contacting Garmin International. I will be glad to assist you.

Sorry to hear about any inaccuracies in our mapping. I have submitted a map error report to correct this issue. Should you notice any other issues you can submit a map report using the link below or simply reply back with the information.

https://my.garmin.com/mapErrors/report.faces

With Best Regards,

Luis

Product Support - Automotive Team

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

.

I reported an error about 10 years ago. A local street that used to not be connected was finally connected. It's only half a block. That half block is still missing from the latest Garmin map update. It's not huge deal, but it messes up the routing because the GPS unit routes you around it thinking that it is not connected.

By the way, I replied to

By the way, I replied to Louis, the Garmin Guy who email'd me, with a copy of the post's from Narvick, so that they knew what other errors in that area were, and the repairs that he did.... and where he posted them...

--
A 2689LMT in both our cars that we love... and a Nuvi 660 with Lifetime Maps that we have had literally forever.... And a 2011 Ford Escape with Nav System that is totally ignored!

reporting a map error

Garmin has a web page to report map errors at https://my.garmin.com/mapErrors/report.faces

Yes

Already posted above smile

--
Where there's a will ... there's a way ... DriveSmart50LMT-D, Nuvi 2508LMT-D, 1490LMT, 1310, Montana 650T, Etrex 20

Let's See

Motorcycle Mama wrote:

I reported an error about 10 years ago. A local street that used to not be connected was finally connected. It's only half a block. That half block is still missing from the latest Garmin map update. It's not huge deal, but it messes up the routing because the GPS unit routes you around it thinking that it is not connected.

Where is this? Let's see if we can fix it like we did with the other one.

The Best Way

bsp131 wrote:

Garmin has a web page to report map errors at https://my.garmin.com/mapErrors/report.faces

The best way to fix errors is to join the HERE Map Creator community and correct the errors yourself. They will be corrected on the Garmin map within 1-2 map cycles (and on HERE.com much faster than that).
I think sending emails to Garmin (who doesn't even own the map data) is ultimately a waste of time for expediency.

Thanks to all

Good information to get errors corrected. Just reported a gap on the road not shown on GPS.

.

Narvick wrote:
Motorcycle Mama wrote:

I reported an error about 10 years ago. A local street that used to not be connected was finally connected. It's only half a block. That half block is still missing from the latest Garmin map update. It's not huge deal, but it messes up the routing because the GPS unit routes you around it thinking that it is not connected.

Where is this? Let's see if we can fix it like we did with the other one.

Virginia Avenue between Woodrow Street and Cleveland Street in Portsmouth, Virginia.

https://goo.gl/maps/myY2anqeeH62

As you can see in Google Maps, the street connects.

Done

Motorcycle Mama wrote:
Narvick wrote:
Motorcycle Mama wrote:

I reported an error about 10 years ago. A local street that used to not be connected was finally connected. It's only half a block. That half block is still missing from the latest Garmin map update. It's not huge deal, but it messes up the routing because the GPS unit routes you around it thinking that it is not connected.

Where is this? Let's see if we can fix it like we did with the other one.

Virginia Avenue between Woodrow Street and Cleveland Street in Portsmouth, Virginia.

https://goo.gl/maps/myY2anqeeH62

As you can see in Google Maps, the street connects.

Done.
Here is the area before:
http://i347.photobucket.com/albums/p458/narvick81/portsmouth...

And here is the area after correction.
http://i347.photobucket.com/albums/p458/narvick81/portsmouth...

Virginia Ave is connected. Also, there were corrections made to Harper Ave and Quebec St in the immediate area.
If we all work together here like this, maybe we can get these errors that have been bothering us corrected in a timely manner smile

Are there

Are there any other errors that need to be fixed that have been bugging anyone?