I have a Microsoft Access program that moves through a pushpin dataset to determine the matching method of each pushpin and print out a report of those pushpins that could not be matched to a specific street address. I believed that checking the MatchingMethod property would let me know if an exact street address match had been made by MapPoint. However, I have found two pushpins located in the same place on my map but in reality, the businesses are about 1/2 mile apart. Both pushpin dataset records show that the MatchingMethod was geoByStreetAddress but MapPoint 2004 does not apparently have the addresses in its database so it picked a location along the street and mapped both addresses at that point.

Is there a way to tell if a match was made by the numerical street address and not just by the name of the street. We want to give customers directions to businesses but we can't if we can not rely on the pushpins being mapped to an actual street address. Any assistance you can provide would be greatly appreciated. Thanks.

Jim Harbaugh
T.E.A.M.
Troy, MI

Hi,

I'm not sure if I understean the question very well, but:

two pushpins located in the same place on my map but in reality, the businesses are about 1/2 mile apar

How many decimals do you have ? If not enough you can easy get a resolution of 1/2 mile. 1 minute is exact 1 sea mile on latitude and on longitude on equator.

numerical street address and not just by the name of the street

If the street contains no number (which is sometimes), then the only method to check this (as far as I know), is to parse the returned streetaddress and check if there is a number in it.

I didn't think I had described my problem very well either so I'll try again:

I have a map that is linked to an Access database. In the Access database are a list of businesses that we work with. For most of the businesses, a pushpin is placed at the exact location of the business. However, I have found at least two businesses that have different addresses (they are approximately 1/2 mile apart; neither are located where MapPoint placed the pushpins) but MapPoint has their corresponding pushpins overlaying each other.

Upon closer examination, I found that the section of road that both businesses are located at does not have numerical addresses assigned to it by MapPoint. It appears that since MapPoint didn't know the numerical addresses, it placed the pushpins in the center of the unaddressed section of the road.

My question is this: I want to be able to write VBA code to read through the link dataset and based on the matching method used to place the pushpin, print a report of pushpins that are not in the correct location. However, the MatchingMethod property is 7 (geoByStreetAddress) for both correctly matched records and for records where the address couldn't be correctly located. Is there a different property I should be using to determine if the pushpin for the record was placed in the correct location or if MapPoint just placed the pushpin in the center of the unaddressed section of the road? If there isn't a property that will provide me with the information I want, is there another method that will tell me which pushpins were not mapped based on the numerical address?

I hope this clears up my question. Thanks for any assistance that anyone can provide.

Jim Harbaugh

Hi,

I'm still not sure I understeand fully but I like it to take step by step. If I sound silly please dont border me, Englisch is not my mothers tongue

two businesses that have different addresses (they are approximately 1/2 mile apart; neither are located where MapPoint placed the pushpins) but MapPoint has their corresponding pushpins overlaying each other.

So you make pushpins at different location, and Mappoint display them at same place ?

I think I understand and I'm having a similar problem - or I think I am.

I have a client test dataset with 1000+ pushpins. I think these have been imported and a handful haven't been matched. Perhaps MapPoint couldn't find the addresses.
When I try to measure a distance to them (eg. via Gilles' location finding code) I get an assertion. This is because the pushpin in question doesn't have a valid location. (cf. MapPoint help).

So is there a way that I can detect if a pushpin has been matched without a dummy call to DistanceTo (or Gilles location code) and trapping an assertion. Trapping an assertion is very ugly and slow - but might be the best way.

The help says there's a geoByNone value for the MatchingMethod properties.
Jim, you're saying this isn't being set!? Typical, isn't it?


Richard

For my own specific problem I have found the Recordset.IsMatched flag that looks to be working (I have a test running in the background).

I don't think this will work for two pushpins located at the same place, though.
Has the user 'helped' with the locating? You know when MapPoint can't find an exact address, but does find some possibles and asks the user?


Richard