I'm not familiar with WMS services, and I didn't really understand why
you can't use the "rand=12345" method for forcing the browser to re-
request the image. You say that it always serves "[url]/wms.png". So
what?

What matters is forcing the browser to re-query for the image. Without
the random param, the browser never even tries to re-query the image.
If you view your example with the Chrome developer panel, it looks
like the browser never bothers to "call" the server a second time to
check if the image has changed. This is not a google maps feature,
it's a browser feature.

So.... Did you actually try to add the random param to the query and
see it fail, or are you just assuming it's not possible?

Again, maybe I'm way off, but something here doesn't make sense to me.

On Jun 1, 7:17 pm, mninoruiz <[email protected]> wrote:
> Hi everyone!
> I have the following challenge, and wondered if anyone could suggest a
> workaorund...
> My clear example is here:http://ccviz.sli.unimelb.edu.au/testMaps3.html
>
> I need to refresh a map image on request, my challenge is that this
> image is given as a WMS service response from Geoserver (for ease in
> testing, I put another image available on internet that refreshes
> every minute, you can try it in your browser on separate window).
> Geoserver, like this example, will always give the image the same name
> (i.e. same url). That's why I can't use something like
>  var url='http://www.meteorologica.info/lightning/lightning.jpg?rand='
> + Math.floor(Math.random() * 99999);
> Which works, but geoserver, as per WMS specification, will always
> serve a "[url]/wms.png" image.
>
> I haven't found a way for google Maps to reload that image as a
> GroundOverlay. I also tried with a kml with networklink
> refreshInterval set. Again, because the kml produced by geoserver has
> a link to that wms image (is a raster map). No matter how many new
> javascript objects do I create, it seems that gmaps caches the same
> image url to the same name, even if the actual image has changed or
> the javascript object is new.
>
> Just in case I tried with the previous google Maps, but same thing
> happens (http://ccviz.sli.unimelb.edu.au/testMaps2.html)
> I'll appreciate any suggestions, best regards,
> Marcos

-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.

Reply via email to