What steps will reproduce the problem? parseKml will fail on a large string (262064 bytes)
What is the expected output or behavior? What do you see instead?
What version of the plug-in are you using? On what operating system? In which browser? All versions, all browsers
Please provide any additional information (code snippets/links) below.
Comment #1
Posted on Sep 23, 2008 by Happy MonkeyComment deleted
Comment #2
Posted on Apr 2, 2009 by Quick ElephantFor our company, this is becoming a serious issue, which is leading us to consider other solutions.
We do want to load on-the-fly generated kmls, and having to code explicit splitters for our kmls is becoming cumbersome. And no, we do not want to post these kmls on a server.
Still, great api with tons of eye candy ;)
Comment #3
Posted on Apr 2, 2009 by Grumpy PandaI think this is fixed in the new release:
http://code.google.com/apis/earth/documentation/releasenotes.html
Comment #4
Posted on Apr 2, 2009 by Happy MonkeyFixed as of 5.0.11655.6079
http://code.google.com/apis/earth/documentation/releasenotes.html#2009-03-31
Status: Fixed
Labels:
Type-Defect
Priority-Medium
Internal-1375413