(old-number-93) Ability to use NetworkLink ID in <targetHref> instead of URL (in <Update>...</Update>) to allow <Change> of NetworkLink elements, including it's URL

[GoogleCodeExporter]

Example:
<NetworkLinkControl>
 <Update>
 <targetHref>#network_link_id_1</targetHref>
 <Change>
 <NetworkLink targetId="network_link_id_1">
 <Link>
 <href>new_URL</href>
 </Link>
 </Change>
 </Update>
</NetworkLinkControl>

Requestor: GG

Original issue reported on code.google.com by api.pame...@gtempaccount.com on 14 Aug 2008 at 6:18

[GoogleCodeExporter]

I think this is doable in KML right now.. can you post this to the KML 
discusison group:

http://groups.google.com/group/kml-support

Original comment by api.roman.public@gmail.com on 3 Feb 2009 at 2:33

• Changed state: WontFix

[GoogleCodeExporter]

will do, thanks for all your contributions. i thought you were a bot at first. i
haven't been able to get it working but i'll search forums more and try again. 
you'd
definitely know better than me. i'm not sure if it was a fix in 5.0 but we're 
still
running an older version of EC.

my original reasoning for this was because when you do a view-based refresh, it
appends the BBOX to the query string and the URL, so your targetHref has to 
match the
new URL and be aware of the updated BBOX. interestingly enough, appending to a 
url
using <cookie> does not modify the URL when it comes to <targetHref>. if the 
problem
turns out to be valid, passing in the BBOX params the same way you pass the 
cookie
(without modifying the actual URL) would be a perfect solution. same goes for
<httpQuery>. 

Original comment by rajni...@gmail.com on 3 Feb 2009 at 2:51

[GoogleCodeExporter]

probably not the best place to post this, and i'll have to talk to follow up 
with
whoever manages the "strategic partnership" we have with Google, but i figured 
you
might read this.

is there any way we can get some sort of project timeline as far as features 
from the
development team? i spent a pretty good amount of time getting animated 
simulations
working over networklinks and networklinkcontrols, only to have an kml schema
extension support it a month later. at the very least you'd have a great bunch 
of
alpha testers.

- api.roman.public@raj.otherinbox.com

Original comment by rajni...@gmail.com on 3 Feb 2009 at 3:03

[GoogleCodeExporter]

Yep, you'll likely want to talk to whoever your current point of contact is 
about the
roadmap; we don't publish public roadmaps for a variety of reasons, but there 
may be
other options with regards to beta testing.

Original comment by api.roman.public@gmail.com on 3 Feb 2009 at 3:16