Reporting wrong coordinates?

 

I've been searching (perhaps with the wrong terms) but I couldn't find a form or post indicating how to report a wrong or absent location in a poi file. Sorry if this has been posted before, but couldn't find it in search.

I noticed 2 cvs pharmacies on my way, one is reported too far from the actual location and the other one is just not there. I have also noticed wrong locations with a couple of McDonalds along my route and a couple of Napa stores. Any way to update the poi files? Do I need to submit the actual coordinates from my GPS? Is this my unit's fault? I understand many of these files are done with the reported address and not the actual coordinate, which may be different.

I found something similar when I went to visit a friend. He gave me the address, which I entered in my nuvi but it wasn't the actual location when I got there. The actual address was 1/2 block down from what the nuvi reported as the destination. Obviously, I setup THAT location as my friend's location, saved it and deleted the one found in the search.

--
Garmin nuvi 1300LM with 4GB SD card Garmin nuvi 200W with 4GB SD card Garmin nuvi 260W with 4GB SD card r.i.p.

Contact the poster of the file

On the POI page, the poster's name is highlighted at the top. Drop them a line. They may not even know.

--
Striving to make the NYC Metro area project the best.

We can correct only the ones that we create

The poi's that are generated on the poi-factory are only as good as the forum members make them. Most are considered very accurate. Those that need correction can only be done so by the members that find the errors and report them to the poi administrator. we welcome those corrections so that we can have accurate files.

The administrator will be looking for the location (address) and the correct latitude and longitude from you.

--
Nuvi 2460LMT.

Correcting coordinates

Corrections should be sent to the file maintainer. The name can be found at the top of the file download page just below the edit,view,logbook tabs. Click on the name and that brings up a page that allows you to send an input to the maintainer. If you are not able to send the comment to the maintainer, just send it to poifactory.
In the case of the McDonalds and the NAPA files please send them to mahoney.
You can click on my name at the top of this comment.

Good files get better

Thanos_of_MW wrote:

I've been searching (perhaps with the wrong terms) but I couldn't find a form or post indicating how to report a wrong or absent location in a poi file. ...
I found something similar when I went to visit a friend. He gave me the address, which I entered in my nuvi but it wasn't the actual location when I got there. The actual address was 1/2 block down from what the nuvi reported as the destination. ...

As others have mentioned, send a note to the maintainer of the specific file. In some cases there is a discussion thread associated with that file and it is often appropriate to post the corrections there. Be specific: List the incorrect location along with the good coordinates so the maintainer can fix the proper record. It is helpful if you use decimal notation, e.g. -97.12345, 33.12345 as an example for a random location in the U.S. I would also verify the coordinates you have with Google Earth just to be sure.

If there is no discussion thread, click on the member's name that is connected with the file in question and send an email through the Connect button. Some are right on top of these things and others may check in now and then. If there is no response in a few weeks, send a copy to Miss POI as the listed maintainer may have moved on to other things and she can fix it.

The reason the files are so good here are that most take the time to get it right, or to make it right when we provide corrections.

Navteq is the source of maps for Garmin and other GPSr manufacturers. Often the errors you see as when you plugged in a friend's address and ended up at the other end of the block are not uncommon. In some cases there is an error in their maps where the house numbers run the opposite direction from actual or the block has address going from 1-16 but the way Navteq set it up there are address 1-100 so all the real address are scrunched up at one end of the block. The geocoding process where addresses are converted to physical coordinates is not yet perfect.

When using a GPSr to locate an address, be happy when it take you to a place where you can see your destination.

--
"There's no substitute for local knowledge" nüvi 750, nüvi 3597

Fooled me

TXRVer wrote:

xxxxxxxxxproper record. It is helpful if you use decimal notation, e.g. -97.12345, 33.12345 as an example for a random location in the U.S. I would also verify the coordinates you have with Google Earth just to be sure.

If there is no

when I read your post, the way it was formatted on the page had the minus sign on one line ahd the 97.12345 on the next line.

I think I have your quote formated so that it looks like it did in your original post.

I thought "97.12345, 33.12345" is somewhere in China. I really had to look hard to see the "-"

Thank you

Thanks everyone. I'll contact them with the correct coordinates (according to my unit) for the listed and missing pois.

--
Garmin nuvi 1300LM with 4GB SD card Garmin nuvi 200W with 4GB SD card Garmin nuvi 260W with 4GB SD card r.i.p.

Font Size?

jgermann wrote:
TXRVer wrote:

xxxxxxxxxproper record. It is helpful if you use decimal notation, e.g. -97.12345, 33.12345 as an example for a random location in the U.S. I would also verify the coordinates you have with Google Earth just to be sure.

If there is no

when I read your post, the way it was formatted on the page had the minus sign on one line ahd the 97.12345 on the next line.

I think I have your quote formated so that it looks like it did in your original post.

I thought "97.12345, 33.12345" is somewhere in China. I really had to look hard to see the "-"

Must have something to do with our default font/text size for our browsers. The -97. was okay for me, but I can see how the line might split differently if the font was different and the line wrapped just after the -

--
"There's no substitute for local knowledge" nüvi 750, nüvi 3597