S&T Import Wizard - are mapping errors uncorrected without warning?
Does the Streets & Trips Import Wizard sometimes leave mapping errors uncorrected without warning?

This image:

is a composite of sequential screen captures during importation of 66 addresses from an Excel file.
S&T2011 seemed to be unable to locate 5 addresses ("5 not mapped") but when it was done there were 66 pushpins in the new set. Also, a .GPX file exported from this does have Latitude & Longitude for all 66 addresses.

Normally the import process pauses when S&T encounters an address it cannot find, and provides a list of suggested alternatives, or if there is no alternative, you have to skip it and S&T puts that pushpin in the center of the matching ZIP code. I corrected 8 of those, but still see the message seen above, so I'm wondering if S&T actually did find those last 5 addresses in the final split second before the "Matching records to: Street Address" went away, or did it just put a pushpin down centered in the matching ZIP code without any warning?

Does anyone know?

Otherwise I guess I'll have to check each one of the 66 pushpins and try to make sure it's where it's supposed to be... and this could be a lot worse if importing a much larger address list.
Attached Images
The unmapped pins are in the pushpin set, but not located anywhere in the map. This is something we have to watch for when programming MapPoint: Looping through pushpins in a dataset will often encounter unmapped pins without valid locations. They are, however, marked as such in the internal data.
Thanks... OK, well the Latitude & Longitude is there for all 66 addresses in the GPX file. I'm going to click on each one in the list that shows up in "Find nearby Places" and see whether or not there's a pushpin on the map for each one. But I still wouldn't necessarily know it all are in the right place unless I spend a lot more time that I can spare.
Ken in Regina
It's actually even worse than Richard described. If there is something in the address the wizard can find it will use it and not warn you.

For example, if you have "123 Main St, Regina, SK", and if it cannot find the street address but can find a location for "Regina, SK" (typically a spot at approximately the geographic centre of the city), that's where it will locate the pushpin.

So, for any street addresses in "Regina, SK" that it cannot find, you will see them clustered at the centre of town.

And no warning that it could not find the street addresses nor that it has used some sort of "proximity" location instead.

I use an online site for bulk address searches. I stopped using the wizard, not because it was unreliable (it is), or unpredictable (it is), but because it gives you no warning of the oddball things it did.

Ken: At the programming level, there is a "matched by" parameter. I haven't done any tests, but one would expect such matches to be marked as "matched by city" (or zipcode, or even State) rather than address.

I guess that gives scope for a decent third party add-in to do a better job, but it would be a pain to code up. The user interface would have to be smooth and easier to use than the existing interface. And the user has 200+ unmatched or inadequately matched addresses, it will take them a while to fix them all.
Ken in Regina
Hi Richard,

Yes, that was clear to me that S&T will try to match on some part of the supplied address if it cannot find the exact address. In the use case I described it is providing the location of the city.

My issue with Microsoft is not the attempt to partially match on something, even though it might be useless. It's the fact that you get no notification. The process simply runs to completion with pushpins being created, locations being placed in the pushpins and the pushpins being placed on the map, even though their location has no relationship to the actual address, other than being in the designated city, and no warning.

Originally Posted by Ken in Regina
My issue with Microsoft is not the attempt to partially match on something, even though it might be useless. It's the fact that you get no notification.

And you have to watch it really, really carefully to even get a hint that something might be amiss.

It took me several attempts to get those screen captures, and that was using a slower computer to make it easier.
laptopgpsworld.com About