Network Error In Google Earth
from GoogleSign inHidden fieldsSearch for groups or messages
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://stackoverflow.com/questions/26022446/google-earth-parse-error the company Business Learn more about hiring developers or posting ads with us Stack http://markmail.org/message/7tqdplgw32jxwiah Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Google Earth Parse Error up vote 1 down vote favorite I am unable to open my KML/KMZ network error file in Google Earth. The error I am getting is: parse error at line 1, column 4 not well-formed (invalid token) I have tried opening in Notepad++ and read everything but I cannot find how to fix the problem. I would greatly appreciate if anyone can help. I am able to send the file in necessary. kml google-earth parse-error kmz share|improve this question edited Jan 16 '15 at 8:46 Mario Kutlev 1,50132038 network error in asked Sep 24 '14 at 16:55 CoastalDavid 612 Can you post the first 2 lines of the KML file? –JasonM1 Sep 25 '14 at 16:48 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote Basically, to fix an invalid KML file you first need to make sure the KML file is a well-formed XML file. That means it follows the basic rules of XML such as the start tags and end tags must be match. If the file has a .kmz extension then you need to unzip the .kml file from the compressed KMZ file. (KMZ is just a .zip file). Given that the error is at line 1 should make fixing it simple. The valid KML file should start with the following lines:
search in one of my setsExclude this search from one of my sets 9 messages in com.googlegroups.earth-freeRe: Address search produces network e...FromSent OnAttachmentsOhmsMar 29, 2007 8:38 am simon_aMar 29, 2007 10:24 am OhmsMar 29, 2007 10:38 am NoisetteMar 29, 2007 12:10 pm OhmsMar 29, 2007 12:54 pm NoisetteMar 29, 2007 1:16 pm OhmsMar 30, 2007 5:10 am OhmsMar 30, 2007 7:45 am NoisetteMar 30, 2007 12:33 pm Subject:Re: Address search produces network error - SOLVEDFrom:Noisette ()Date:Mar 30, 2007 12:33:52 pmList:com.googlegroups.earth-freeGlad you got it sorted Ohms :) And thanks for the feedback, that's really interesting, it explains why you only had a problem with searching. On Mar 30, 4:45 pm, Ohms wrote: We Fixed our problem. Here is what I was told. Hope it helps someone else. Fixed Firewall / proxy issue. We use IWA for the firewall and since GE doesn't pass along IWA credentials we were not validating to use maps.google.com On Mar 30, 8:10 am, Ohms wrote: Here are some of my Stats. The reason I believe it's due to our Firewall is because it worked up until this week. It stopped working on all our PC's which have various setups and proccessors. Of course IT says "we didn't make any changes" Well someone did somewhere. lol When we figure it out I will be sure to post it. Thanks again. Google Earth 4.0.2742 Build Date Mar 13 2007 Renderer OpenGL Operating System Microsoft Windows XP (Service Pack 2) Video Driver Intel (00006.00014.00010.04410) Max Texture Size 2048x2048 Server kh.google.com User License Key pentium 4 -3.3MHZ Connection LAN -Cable IE7 and IE6 On Mar 29, 4:16 pm, Noisette wrote: Just to add, if you don't get it solved, could you read this and provide the information requested, plus the version of GE you're using:http://bbs.keyhole.com/ubb/showflat.php/Cat/0/Number/487722/an/0/page... On Mar 29, 9:54 pm, Ohms wrote: Thanks Noisette, I will get with our IT and look over the information. Appreciate it. On Mar 29, 3:10 pm, Noisette wrote: Hmm, this has come up before, but in one case it seemed to resolve itself, and in the other two cases there was no feedback. For what it's worth...http://bbs.keyhole.com/ubb/showflat.php/Cat/0/Number/778326/an/page/p...... Also, did you see the bottom of the p