Yes the sethwadleyford.com domain is working now because I had to take out the number of the street address they are located at. I've been able to confirm this is the problem with a couple of other website that this is all of a sudden happening to. I'm not sure I understand the logic behind this. I mean why does Google have to mess with it if it works already.
So from what you are saying is I have to place the geo-codes in now instead of the street address we want to send the person to? Google should address this. We have half our sites up and running just fine (and this is the way we've always had our integrated google maps) and the other half seem to be down. Based on updating a few of the sites that are down with the removal of the address I'd say this is a hickup on Google's side. It is unfortunate that the data would pull inconsistently in this manner. I can image I'm not the only one having the frustration at the moment. On Sep 10, 4:03 pm, Andrew Leach <[email protected]> wrote: > On 10 September 2010 23:31, macrunning <[email protected]> wrote: > > > I've been able to duplicate this same thing on another account. For > > some reason removing the address number on the street appears to make > > the api call work, but if I leave the number of the address in, it > > will not work. > > None of your sites fail at the moment. > > I *guess* that you are finding that an address which used to work as > one end of the directions no longer does, and (when it fails) it's > coming up with a message like "I can't geocode one of the addresses". > > Geocoders change from time to time as they are updated. Generally, > things improve. Sometimes they don't. > > For directions to a known location, don't get the directions service > to geocode your destination. You already know where that should be, so > tell the directions service exactly where to arrive. Use an @ sign, > like > 2109 W Grant Avenue, Pauls Valley [email protected],-97.258796 > -- that will probably be interpreted as an email address and acquire > some dots, but you should get the idea. There shouldn't be spaces > either side of the @. You can use any string on the left of the @, and > that's what will appear in the directions panel. > > If I've guessed wrong, you're going to have to tell us what "will not > work" actually means. What should happen? What are you seeing instead? -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
