ability to fully remove KML loaded by fetchKml()

[GoogleCodeExporter]

KML loaded by fetchKml cant be removed, only hidden. If you reload the same kml 
in the same browser session you get duplicated data. See this thread, this 
thread, this thread, or this thread

Requested by: Fraser

Supported by: sylehc, bFlood, scorpi , jan.wischnat, ITS4IP, plomari

Original issue reported on code.google.com by api.roman.public@gmail.com on 12 Aug 2008 at 8:45

[GoogleCodeExporter]

Is this a duplicate of issue 72?
http://code.google.com/p/earth-api-samples/issues/detail?id=72

Original comment by api.roman.public@gmail.com on 23 Dec 2008 at 6:09

[GoogleCodeExporter]

I would say not exactly.  Issue 72 appears to be an issue with using fetchKML 
to grab
'dynamic' script-generated KML but if a 2nd fetchKML call is made to the same 
URL
within a certain time, no 2nd fetch is actually made, rather the original KML 
is kept
via the cache.

This issue is the matter of being able to wait long enough to get past the cache
limit so in this case, fetchKML grab's a 2nd full copy and assigns it a new DOM 
node
(and thus duplicate content rather than replacing the old content).  

Original comment by vzetterl...@gmail.com on 23 Dec 2008 at 6:15

[GoogleCodeExporter]

Hm, fetchKml isn't supposed to replace any objects; by design, it creates new
objects. To replace KML via fetchKml, you need to first remove the old objects. 

Original comment by api.roman.public@gmail.com on 23 Dec 2008 at 7:18

[GoogleCodeExporter]

I'm marking this as a dup of 72.. I believe this is one and the same core 
problem. If
anyone begs to differ, let's start up a thread in the discussion group.

Original comment by api.roman.public@gmail.com on 5 Feb 2009 at 8:29

• Changed state: Duplicate

[GoogleCodeExporter]

This issue is requesting the ability to remove kml.  issue #72 has to do with 
caching.

Original comment by tre...@trevorcroft.com on 27 Jul 2011 at 11:29