Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tag <NetworkLinkControl> doesn't work with namespace xmlns:xal="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0" #22

Open
GoogleCodeExporter opened this issue Jun 29, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?

1. Marshal and launch a KML file that contains a NetworkLinkControl that 
performs an Update on another KML file.  By default, JAK will add the following 
namespace to the KML file: xmlns:xal="urn:oasis:names:tc:ciq:xsdschema:xAL:2.0"

2. The NetworkLinkControl will not update the other KML file unless the 
previously mentioned namespace is removed.

What is the expected output? What do you see instead?

I've reported problem as a bug to Google.  In the mean time, maybe JAK should 
allow the user to specify what namespaces they'd like to add to KML files 
during marshaling.

What version of the product are you using? On what operating system?

2.2.0 on Windows XP 32-bit

Please provide any additional information below.

Please see the attached file for the code snippet.  If the previously mentioned 
namespace is removed, then the other KML file is Updated correctly.

Google Earth bug report:
http://code.google.com/p/kml-samples/issues/detail?id=347

Original issue reported on code.google.com by mhrobin...@gmail.com on 29 Jun 2010 at 10:01

Attachments:

@GoogleCodeExporter
Copy link
Author

I solved this problem by downloading the project from the repository and 
removing the xal package and all references, both code and annotations, to xal. 
 While this is a brute force solution, it works for me since I'm only producing 
KML for Google Earth, which apparently doesn't support xAL.

Original comment by mhrobin...@gmail.com on 30 Jun 2010 at 7:36

@GoogleCodeExporter
Copy link
Author

I have the same issue.

I've created some examples. Have a look at the working example KMLs:
http://dl.dropbox.com/u/392709/KML%20Issue/works/Point-load.kml
http://dl.dropbox.com/u/392709/KML%20Issue/works/Update-load.kml

compared to:
http://dl.dropbox.com/u/392709/KML%20Issue/fails/Point-load.kml
http://dl.dropbox.com/u/392709/KML%20Issue/fails/Update-load.kml

the only difference is the namespace definitions in the kml element

Original comment by andrethe...@gmail.com on 29 Aug 2011 at 1:49

@GoogleCodeExporter
Copy link
Author

Any resolution on this?  

Original comment by barnett....@gmail.com on 27 Sep 2011 at 12:34

@GoogleCodeExporter
Copy link
Author

I just tested my example KMLs and it appears to be working now in Google Earth 
6.1.0.5001

Original comment by andrethe...@gmail.com on 21 Dec 2011 at 10:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant