PDA

View Full Version : MP 2004 IS SHOWING PUSHPINS IN WRONG LOCATION



MAKAZA
11-05-2005, 07:32 AM
I am new to MP 2004 and have imported 1016 customer addresses from excel to MP. 840 of the addresses are shown correctly but the remaining addresses are all shown in one location some 200 miles distant from the correct location. Can anyone offer any advice as to why this is happening and how to correct it?

Any help would be appreciated
Makaza

Eric Frost
11-05-2005, 07:53 AM
It depends on the specific addresses.. try tweaking the address including city and zip code on the ones that don't match to figure out if you can make the match, otherwise your best bet would just be to place them manually.
Eric

Chris_Taverrner
11-20-2005, 07:48 AM
If you are not using addresses, but Lat Lon co-ordinates: Check to see whether the lat or lon is negative. This will apply in UK especially. If you are using a variable type other than double to store the lat lon, it can result in a variation of a few hundred miles easily. (Trust me I've made that mistake a hundred times). :shock:

Winwaed
11-20-2005, 11:11 AM
If coordinates (lat,long), or OS Grid References are being used, then errors of "200 metres" could easily be a geoid problem.

MapPoint uses WGS94.

MapPoint 2002 has a bug that uses the wrong geoid for OSGR coords.
This is fixed in MapPoint 2004.
(OSGRs use Airy '36, but Microsoft accidentally used WGS84 in MapPoint 2002)


Richard

Wilfried
11-20-2005, 01:32 PM
Hi,


Trust me I've made that mistake a hundred times :shock:

Me only 10 times. But I only have 10 customars in UK driving around the meridian 8)

Wilfried
11-20-2005, 01:34 PM
Hi Richard,



MapPoint uses WGS94.

Euh I hope this is typo and you mean WGS84 ?

Winwaed
11-20-2005, 03:39 PM
Yes :)

Richard

brianmcg
11-22-2005, 02:47 PM
Hi Makaza,

Based on your description (that all error locations are being shown at the same location), it sounds like the addresses are being validated based on the State or Postal/Zip Code or some other high level address part. You might try manually checking the bad locations to see if there's a consistent pattern (spelling errors, etc.) that could be corrected in the base data.

Hope this helps.