yea thats exactly what i did, so basicly it always waits for one geocode request to complete before moving to another request. I have to look into the possibility of storing the points for addresses for corresponding "profiles" in database to make it more efficient if there are lots of addresses to be geocoded. Thanks for the tip, sorta overlooked that possibility.
On 20 maalis, 01:24, pamela fox <[email protected]> wrote: > Hi Kalma- > > Generally, we don't recommend geocoding multiple addresses in a loop - > if you know the addresses ahead of time, then you should geocode them > and store them in a database. > If you absolutely have to geocode multiple addresses, then you can > wrap the geocoding call in a function with an inlined callback > function, and then you'll know what address it corresponds to. > > - pamela > > > > On Fri, Mar 20, 2009 at 2:30 AM, Kalma <[email protected]> wrote: > > > The reason was in using https instead http, so that one got fixed. > > > Sorta on the same subject, the service im building is using multiple > > geocode requests to popuplate markers on the map. > > After some workarounds i managed to get the synchronize the outcoming > > requests o returning points when populating the map. > > I'de like to suggest that you tag the requests with ID's if possible > > to simplify this in the future. Atleast i wasnt able > > to find anything on the geocode API for this purpose.- Piilota siteerattu > > teksti - > > - Näytä siteerattu teksti - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" 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-for-flash?hl=en -~----------~----~----~----~------~----~------~--~---
