On Jan 24, 8:33 pm, dvancouver <[email protected]> wrote: > Thanks I will look into it but I know there is an easier way.
Sooner or later (probably already) one of your users will give you a bum address that can't be geocoded. It's up to you how to deal with that. One method, which is more work for you, is to geocode at the point of data entry. If the user supplied address geocodes okay, that's fine, store it (and you don't need to geocode every time you retrieve it). If the user supllied address fails, you enter a "did you mean" routine. An alternative method is to accept rubbish into your database, and invent a method of dealing with the situation when you retrieve some or all results that are rubbish. If you want help with that, you may have to reveal the URL of your super-secret webpage. (you've spent hours looking, so you must have read the posting guidelines somewhere along the way and chosen to ignore them - http://groups.google.com/group/Google-Maps-API/web/suggested-posting-guidelines ) For example, showadress() is a function that you have defined in your own webpage, and no-one else here has any idea what it does. cheers, Ross K. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
