Indeed, after a little of brain working, I managed and find a good
compromise solution.
Now, you can see from 
http://www.arbea.basilicata.it/index.php?option=com_wrapper&view=wrapper&Itemid=168
all functions (and, well, Progressbar counting also).
I use a PHP script which builds a JavaScript.
It attempts and recover lat-lng fields from db; if it finds, it simple
add a marker; if it DOESN'T find, it calls another PHP script, a proxy
for Google HTTP geocoding, which retrieves coordinates, and add them
to db.
Not to complicate things, first PHP script in this case also use
GClientGeocoder and render another marker.
I added my db table a trigger: if "address" field changes, "lat" and
"lng" fields are set to NULL.
Next execution, my script will populate it; so I also solved problems,
of maintaning my db management easy.
Thank you all for your answer; you drove me learning a lot about
Google geocoding.



On Dec 7, 10:47 pm, "Björn Brala" <[EMAIL PROTECTED]> wrote:
> How about updating the control even when a geocode fails? That was it shows
> operations, not markers. Then when all work is done remove it.
>
> In my system i use the control for counting the adding and removing of
> items, so the count is just a count of operations, no indication of the
> amount of items in the map.
>
> http://demo.geostart.nl/
>
> 2008/12/7 borzoi <[EMAIL PROTECTED]>
>
>
>
>
>
> > > But your locations all need geocoding, and some geocodes fail of
> > > course - too quick, too many, unrecognised.  How many markers get
> > > rendered isn't the same as how many locations you started with.
>
> > This is a second order of problem.
> > Just to afford it, as a temporary solution, if you look at JS code,
> > you note updating ProgressBar is done OUTSIDE the "if" condition to
> > process response from getLocations().
> > So, independently you get a 200, a 620 or what, updating function is
> > called 90 time, with EXACTLY the same count locations parameter.
> > This is NOT a question.
>
> > About removing ProgressBar: Google Maps API executes in delayed mode.
> > This is a TRUE GOOD thing for a lot of reasons; but in this case,
> > should I call remove(), even after loadMap() function, even after an
> > artificial delay, ProgressBar will NEVER be showed.
>
> --
> Bjorn Brala
> ----------------
> GeoStart.nl- Google maps - Swis Webdesign
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to