FWIW... I don't disagree with you in that they should make it much more obvious when they give you an address that isn't a pretty exact[1] match for what you typed but it does seem like you had the street name wrong - I am pretty sure the place you were trying to get to was 52 Brooks St. Mapquest has better behavior than google in this case, if you ask Mapquest for 52 Brook St in Brighton, you get 52 Brooks St (not 52 Brook St in Brookline) and also "We did not find the exact location you entered" although the way in which it presents that text is a bit subtle... but at least it's there. I also tried bing maps and they give the same answer as mapquest does but, like google, don't tell you that what they gave you didn't match what you asked for.
[1] The matching could be a little fuzzy but not too fuzzy. For example, if you ask for "25 First St" and it gives "25 1st St" or vice-versa, it probably shouldn't warn. There are other cases where it would probably have to warn even when the address is perfectly right, e.g. if you say "Chestnut Hill" and the address is in Newton, Brookline, or Boston but within the right boundaries.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2011-04-09 12:41 pm (UTC)[1] The matching could be a little fuzzy but not too fuzzy. For example, if you ask for "25 First St" and it gives "25 1st St" or vice-versa, it probably shouldn't warn. There are other cases where it would probably have to warn even when the address is perfectly right, e.g. if you say "Chestnut Hill" and the address is in Newton, Brookline, or Boston but within the right boundaries.