Hi Dave- Yes, you can do that all with JavaScript. Just remove the overlays (map.clearOverlays(), or map.removeOverlay() on each added overlay), then call your function that reads in the XML and adds the overlays.
- pamela On Tue, Dec 9, 2008 at 9:46 AM, David Raasch <[EMAIL PROTECTED]> wrote: > Pamela, > > Somebody from Google Maps Enterprise emailed me a short while ago, > apparently following up on a "first email" that they sent me (at work) and > which I never received. I asked him to send again... he said he did.... and > still nothing. So, we're working that out. > > Meanwhile, regarding your question about refreshing the entire page: I > need the map itself to remove all objects, reread the XML file, and > redraw... at a user-defined (a la cookie) refresh rate. I did it this way > originally two years ago in sort of a "test version" we had...which got > sidetracked and forgotten. And since we're now readdressing things, I had > not changed that core design. > > I'm assuming from your question that there must be a way for me to do this > without refreshing the page, eh? Just some sort of command to remove > everything and then an Ajax call to reload the XML? > > Frankly, all this Javascript, XML, etc. has ZERO to do with my regular > day-job, so I must confess that I've simply been modeling my Google > Maps-related code on code that other people have posted publicly.... and I > haven't found anything yet where somebody does an "erase, reread, redraw" at > regular intervals. > > > Thank you, > > Dave > > > ------------------------------ > *From:* [email protected] [mailto: > [EMAIL PROTECTED] *On Behalf Of *pamela (Google Employee) > *Sent:* Monday, December 08, 2008 4:31 AM > *To:* [email protected] > *Subject:* Re: Question about rate of queries involved with google maps > use > > Hi Dave- > Why are you refreshing the entire page? The typical architecture would be > to refresh just the content on the map, perhaps by adding new markers or > changing marker positions. That would be a completely client-side operation > and issue no queries to the Google servers. > > Regarding enterprise - please email me your contact info if you still > haven't heard from them. > > - pamela > > On Sun, Dec 7, 2008 at 2:51 AM, dr4296 <[EMAIL PROTECTED]> wrote: > >> >> Greetings All! >> >> OK, I'm still waiting for somebody from Google Maps Enterprise Sales >> Team to get back to me from my initial contact / form submission >> attempt from almost two weeks ago. (I just resubmitted the form >> again, in case they somehow didn't get it the first time.) >> >> Anyways, I was wondering if anybody knows or has studied how >> frequently and in what situations a Google Map application will >> actually query back to Google's servers... especially given the fact >> that I know the client browser will cache up a lot of the data? >> >> The application I've got basically loads a single Google map and then >> will autorefresh itself every, say, 90 seconds (although that can be >> adjusted). OK, with the initial load, I know we're going to fetch >> how-ever-many map tiles from Google... and we're going to fetch the >> javascript files from Google that make the map "work".... plus any pin >> images we may need. >> >> But, after that, if we just autorefresh the page, the browser >> shouldn't actually have to query Google again for anything, should >> it? Shouldn't everything still be in the cache? >> >> At what point do browsers decide to go try to fetch new info? (I know >> you can set this in a page header for the webpage that CONTAINS the >> Google Map... but I would think the map itself would be "treated >> differently" ??) >> >> I realize that if a user zooms out or in, then we're going to have to >> fetch a new set of map tiles. And of course, that would get cached >> by the browser too, at least for a while. >> >> I'm trying to get a better understanding of how often a single user of >> my application might actually be querying Google for information.... >> because I think I've read that Google Maps Enterprise charges a base >> fee, but then additional fees if the number of queries you make >> exceeds a certain level. That got me thinking: "what constitutes >> one query?" Well, probably the fetching of a single file? Or maybe >> the fetching of a single set of map tiles? Not sure. >> >> If anybody can shed a bit of light on this subject for me, I'd greatly >> appreciate it! It would help me prepare for talking with the folks at >> Google Enterprise, plus it would help me come up with some sort of >> "expected usage" estimates on my end. >> >> >> Thanks! >> >> -= Dave =- >> >> >> >> > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.176 / Virus Database: 270.9.15/1835 - Release Date: 12/7/2008 > 4:56 PM > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
