Well, thank you and I appreciate your help. I will remove the address ;).
So, does google itself use a different method to geocode? Because, every one that I search for on their site is always right on the money, but none of mine have been so far. It just seems odd. Anyway, I'm still open to opinions, though I do appreciate yours.. Regards, Kevin Cornett On Sep 7, 6:50 pm, "maps.huge.info [Maps API Guru]" <[EMAIL PROTECTED]> wrote: > I put a test on for a known address and it works fine. The problem may > be in the geocoding itself, not in how you're storing and recalling > the addresses. > > Geocoding is more art than science, so having a lot of potential > errors is just common. What you might want to do is something similar > to this: > > http://maps.huge.info/pinpointaddress.htm > > This gives a user a second chance to move the marker to the right spot > before submitting it to storage. This double checks the address and > gives you a much higher confidence that what you're storing is an > actual, valid location. Also, if the location isn't found, the user > can find it for you. > > Maybe some day geocoding will be better but right now it's sort of in > the "Spirit of St. Louis" era. > > You might want to remove the "test" address I added. No public potty > there. > > -John Coryat > > http://maps.huge.info > > http://www.usnaviguide.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
