Help with cutom POI's

How are you searching for the custom POIs?

Custom POIs are in a different database then the built in POIs.

Where To -> Extras -> Custom POIs

Don't rush to any conclusions. You may have to dig a little deeper.

I found not one, but two, glaring issues with the geocoordinates in a couple of POI files just yesterday. One of them placed the Best Buy 7 miles north of its actual location. The other had my local Home Depot situated in another state...it's taken me months to figure out why nobody had added my very busy local store to the HD file.

I know Miss POI has been kind enough to address these errors already.

WOW! I see them now. Thanks so much ! I was getting worried that something was wrong.

Yea, It shows my Sonic and McDonalds two miles away. How do I correct this in my csv file without screwing it up.How do I get the coordinates without driving there and looking at my GPS ?

there are a couple of sites that handle the geocoordinate conversions for you. The link is on my other computer, sorry.

You simply punch in the correct address and it spits out the LAT/LON values.

You'd then edit columns A and column B in the Excel spreadsheet with the correct LAT and LON values.

If it's a .gpx file, you would have to have a GPX editor. Most of the files used here are Excel (.csv)

I use http://www.gpsvisualizer.com/ to produce the lat/lon info. Look for the link to geocoding. Exactly as you say, you put in the address and it spits out the information.

I think you can get it from Google Maps as well.

that the info 'Gps Visualizer' spits out may not be accurate when using batch geocoding. When geocoding an individual location, it gives the 'Result precision'; but doesn't when doing batch geocoding. In addition, if it can't find the address when doing a 'batch', it will give the street coordinates; if it can't find the street it will give the coordinates of the Zip; etc until it could be giving you the coordinates of the country. This happens often when geocoding new locations on new streets because 'visualizer' isn't aware that street exists.

RT