KMZ/KML Parse error.

[boukeceelen]

I've read the Faq on the parse error, but i'm a bit confused.
Last night I put up a lot of placemarks, used some tekst of other people from the community, and saved my places, and also saved to my desktop as a backup. I use the last beta version of GE.
Totday when I wanted to continue my work, I got a parse error??

Can anyone help me to resolve this problem.... I really don't want to start all over...
I've posted the file with this topic. They're places I've been to over the years.

PS: I'm totally unfamiliar with the KML language.

thx

[lowtech189]

I repaired your kmz file for you. Just make backups from now on before you make changes, that way you still have a working copy.

[boukeceelen]

Wow, thx mate! I had backups but for one reason or the other it just wouldn't work! but from now on i'll backup everything 3 times... haha

anyway thanks again!

[bnicosia]

lowtech189, is there any way you might be able to help me out as well...

[ink_polaroid]

How did you corrupt your myplaces? Can you give me more detailed reproduction steps?

If you looked at other bbs file, which ones did you load?

[lschwartz777]

I think I may be having a similar problem... can anyone help? I have talked with Google Support and they suggested I look for help here.

I started a file in the Free Beta 4.0 version, then I got Pro Trial 3.0 version and continued working on the file. I have been working out of Temporary Places and periodically selecting Save As and creating a new file. After I close out I go back and open the most recently saved file. This has always worked until now :-( My most recent set of saves will not open - Google Support thinks they may be corrupted. I get a Parse Error. I tried downloaded Pro Trial 4.0 version, but now even older files that I could open before won't open. Any ideas??? I want to purchase the Google Earth Pro either 3.0 or 4.0, but I want to make sure I can fix this first. I have a lot of hours invested so far in this project.

I have a PC, Microsoft Windows 2000 Professional.

Thank you to anyone who can give me advice!!!

[ink_polaroid]

the file you have attached has several images and an empty kml document.

can you attach one that you saved from 4 and won't open again in either 3 or 4?

[lschwartz777]

Hi ink_polaroid - thanks for looking at this. That was my most recent save and what I am hoping can be recovered (all I did was add the folders and placemarkers, but a lot of them!) - I saved that in Pro Version 3 and I can't view it at all now. What does empty KML document mean? Pls forgive my ignorance - I am new at this!

I will attach here the last save I had from Free Version 4 if that will be helpful for you to see. I can open this without a problem.

Thnx, ~L

[ink_polaroid]

if you load this file into 3 and save it back out, can you view the saved file in 4?

[petetw9]

I seem to have a similar problem that is not resolved by any of the suggestions in these pages. I have four layers in .kml that I place in 'temporary places'. Generally I can load two and then the third will give a 'parse error'. If I then remove the first and add the third (the one that generated the error), the layer loads fine (no error). If I then try to reload the first, I get the parse error again. It really seems to be unrelated to the data. To circumvent this drama I then merged all the layers into one. If I open Google Earth and try and load it into 'temporary places' I get the parse error. If I load a small layer first and then remove it before loading the merged layer, I don't get the error message. Unfortunately my patience is somewhat limited so I am not sure if the layer will load into 'temporary places', I don't get an error message but I get an hour glass. The longest I have stared at the screen waiting for something to happen is 2hrs and then my lack of patience got the better of me. I will try and let it go over the weekend and see if it does load.

Does anyone have any suggestions as to how I can speed this up and/or avoid the parse error? What is the parse error message trying to say?

Thanks

Pete t

[ManoM]

Hi petetw9,

Have you tried upgrading to the latest beta? Can you post your kml file so we can try to replicate the problem and figure out what's going on?

ManoM

[petetw9]

I do have the latest Beta Version, downloaded last week. Here is a layer that I have been waiting for it to load into temporary places all since lunchtime Friday. This morning (Monday) I gave up and stopped the process.

[tekgergedan]

Hi Pete

What do you mean by "layer"?

[ManoM]

Hi petetw9,

There was nothing attached to your post, did you mean to attach something?

By "layer", I assume you mean a KMZ file, right? Technically, "layer" refers to the Layers section of the control pane to the left, which only Google has control over.

ManoM

[petetw9]

Sorry, I'm using the term layer in the GIS manner (for want of a better term). There are about 150 000 "places" so I called it a layer since all the polygons are in the same kml despite it not being in the "layer" section of G.E.

[petetw9]

Yes I did attach a kml file.
I will try again. I am just using the standard post attachment function on the reply page. Let me know if it doesn't work and I will send you a smaller one.

[tekgergedan]

I dont see the attachment, Pete. When you attach, it will show up as in boukeceelen's post (the first post) in this thread. You can attach 20,000,000 bytes, btw.

[petetw9]

Yes it would be a size issue. The file I was trying to attach is 411 772kb and all the other files that I have received the "Parse error: o at line 1, column:0" are in excess of the 20 000 000 bytes. They are 103 396kb, 206 826kb, 32 000kb, and 92 570kb. As a result of this I won't be able to attach any of the ones that have given me trouble (and remember I can generally load a couple before problems arise, and if one fails I can remove another and then successfully load the failed file). I will therefore send a small one that hasn't given me trouble yet, but it is the same type of content and the same method of construction as the others, so presumably it could fail in a similar manner.

[petetw9]

I seem to be having troubles with attachments. The file I tried to attach to the last response of mine was only 8 908kb so I thought it would work but I can't see any evidence that it is attached. During the attachment process I did get an error message "cannot continue, all fields not complete, use the 'back' key to return to the previous page and complete".
This seemed odd to me because I couldn't find and 'required' feilds to be completed. I wrote text in the text box, put in an icon, browsed to and attched the file in the attachment box, and then clicked "ok, submit".
What else does it want??

[petetw9]

I will try to attach it again!!!

[ManoM]

Hi petetw9,

When I downloaded the attachment, it's an empty file, nothing at all in it. Is it that way before you attach it?

If your KML file is small enough, you can try copying it and pasting it into your message.

ManoM

[petetw9]

The attachment did contain data. I will try again.

[petetw9]

I seem to be having a great deal of trouble attaching anything. I keep trying and if it doesn't result in an emplty file I get the error message, "cannot proceed. required fields have not been completed".
BUT THEY HAVE!
I tried on several occasions to copy/paste the kml but it just crashed Internet explorer. I will try the attachment method again here but don't hold your breath.........!!!!!!!?!?!?!?!!

[petetw9]

Trying Again!!!

[petetw9]

And Again!!!
This is ridiculous!!!!

[petetw9]

Does this work?

[petetw9]

Help!!!
How do you get this attachment thing working!!!!!!!!!!!!!

[petetw9]

How's this?? Functioning????

[petetw9]

[petetw9]

If this doesn't work I will give up with this bucket of c....p!!!!

[petetw9]

<?xml version="1.0" encoding="windows-1252"?>
<kml xmlns="http://earth.google.com/kml/2.0">

<Document>
<visibility>1</visibility> <Style id="KMLSTYLER">
<IconStyle>
<scale>0.8</scale><color>ffbf8080</color><colorMode>normal</colorMode> </IconStyle>
<balloonStyle>
</balloonStyle>
<LineStyle>
<color>ffbf8080</color><colorMode>normal</colorMode> </LineStyle>
<LabelStyle>
<scale>1.0</scale> </LabelStyle>
<PolyStyle>
<color>ffbf8080</color><colorMode>normal</colorMode> </PolyStyle>
</Style>
<Style id="kml_FT_Strttn_Ftprnts_style">
<IconStyle>
</IconStyle>
<balloonStyle>
</balloonStyle>
<LineStyle>
</LineStyle>
<LabelStyle>
</LabelStyle>
<PolyStyle>
</PolyStyle>
</Style>
<Folder>
<name>Strttn_Ftprnts </name> <Placemark>
<description><!CDATA[<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor='#E3E3F3'><th>Shape_Length</th><td>56.6266921024666</td></tr><tr bgcolor=''><th>BASE_MAX</th><td>66.08139084</td></tr><tr bgcolor='#E3E3F3'><th>Z_AVE</th><td>67.2</td></tr><tr bgcolor=''><th>ZMIN</th><td>67.1</td></tr><tr bgcolor='#E3E3F3'><th>BULDNG_HGT</th><td>2.5</td></tr><tr bgcolor=''><th>ZMAX</th><td>67.3</td></tr><tr bgcolor='#E3E3F3'><th>BASE_AVE</th><td>65.53334162</td></tr><tr bgcolor=''><th>CAPT_DATE</th><td>22/11/2001</td></tr><tr bgcolor='#E3E3F3'><th>geodb_oid</th><td>1</td></tr><tr bgcolor=''><th>OBJECTID</th><td>1</td></tr><tr bgcolor='#E3E3F3'><th>QUALITY</th><td>1</td></tr><tr bgcolor=''><th>PIN</th><td>190434</td></tr><tr bgcolor='#E3E3F3'><th>POLY_TYPE</th><td>footprint</td></tr><tr bgcolor=''><th>BASE_MIN</th><td>64.9852924</td></tr><tr bgcolor='#E3E3F3'><th>Shape_Area</th><td>149.233586408832</td></tr></table></center>]]></description><Snippet></Snippet> <styleUrl>#KMLSTYLER</styleUrl><Polygon>
<outerBoundaryIs><LinearRing><coordinates>116.052043506423,-31.8806200847451,2.5 116.052047702731,-31.8806217299504,2.5 116.052048079143,-31.8806218764291,2.5 116.052048649324,-31.8806221009777,2.5 116.052062158765,-31.8806273962509,2.5 116.052062559398,-31.8806275524883,2.5 116.052062660024,-31.8806275915511,2.5 116.052075731567,-31.8806327159404,2.5 116.052078077553,-31.8806336353736,2.5 116.052083999355,-31.8806359559309,2.5 116.052088721144,-31.8806378061938,2.5 116.052089093815,-31.8806379526444,2.5 116.052110479738,-31.8806463349271,2.5 116.052110921347,-31.8806465090298,2.5 116.052111232529,-31.8806466310767,2.5 116.052127589208,-31.8806530426718,2.5 116.052177242519,-31.8806725036868,2.5 116.052175865402,-31.8806750779169,2.5 116.05214493514,-31.88073293704,2.5 116.052135930353,-31.8807497800805,2.5 116.052133702517,-31.8807539475141,2.5 116.052133347732,-31.8807546121448,2.5 116.052133048276,-31.8807551718287,2.5 116.052132738948,-31.8807550513921,2.5 116.052123570798,-31.880751491806,2.5 116.052123334134,-31.8807514006455,2.5 116.052118194753,-31.8807494051947,2.5 116.052104574821,-31.8807441186816,2.5 116.052090168523,-31.880738526189,2.5 116.052078475405,-31.8807339867669,2.5 116.052076598923,-31.8807332576081,2.5 116.05205722654,-31.8807257379982,2.5 116.052062520208,-31.8807155911349,2.5 116.052068010416,-31.8807050689973,2.5 116.052060799964,-31.8807021641426,2.5 116.052060101276,-31.8807018827634,2.5 116.052054862059,-31.8806997716281,2.5 116.05204237514,-31.8806947393956,2.5 116.052033903337,-31.8806913254748,2.5 116.052030544049,-31.880689972258,2.5 116.052026946274,-31.880688523078,2.5 116.052021558008,-31.8806984074322,2.5 116.052009834258,-31.8806937544344,2.5 116.052006225096,-31.8806923211323,2.5 116.051995028665,-31.8806878763988,2.5 116.051987663128,-31.8806849528235,2.5 116.051985130921,-31.8806839489896,2.5 116.051975229469,-31.8806800183592,2.5 116.051975826723,-31.8806788782272,2.5 116.051987082477,-31.8806574385203,2.5 116.052005419146,-31.8806225065497,2.5 116.052011521716,-31.8806248955053,2.5 116.052024457299,-31.8806299598209,2.5 116.052027092117,-31.8806309915572,2.5 116.052035704659,-31.8806343634264,2.5 116.052035958078,-31.8806344626937,2.5 116.052036389294,-31.8806336421904,2.5 116.052043506423,-31.8806200847451,2.5</coordinates></LinearRing></outerBoundaryIs></Polygon> </Placemark>
<Placemark>
<description><!CDATA[<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor='#E3E3F3'><th>Shape_Length</th><td>53.4955355620131</td></tr><tr bgcolor=''><th>BASE_MAX</th><td>64.72186352</td></tr><tr bgcolor='#E3E3F3'><th>Z_AVE</th><td>66.35</td></tr><tr bgcolor=''><th>ZMIN</th><td>66.3</td></tr><tr bgcolor='#E3E3F3'><th>BULDNG_HGT</th><td>2.5</td></tr><tr bgcolor=''><th>ZMAX</th><td>66.4</td></tr><tr bgcolor='#E3E3F3'><th>BASE_AVE</th><td>64.402596285</td></tr><tr bgcolor=''><th>CAPT_DATE</th><td>22/11/2001</td></tr><tr bgcolor='#E3E3F3'><th>geodb_oid</th><td>2</td></tr><tr bgcolor=''><th>OBJECTID</th><td>2</td></tr><tr bgcolor='#E3E3F3'><th>QUALITY</th><td>1</td></tr><tr bgcolor=''><th>PIN</th><td>190434</td></tr><tr bgcolor='#E3E3F3'><th>POLY_TYPE</th><td>footprint</td></tr><tr bgcolor=''><th>BASE_MIN</th><td>64.08332905</td></tr><tr bgcolor='#E3E3F3'><th>Shape_Area</th><td>147.386089290631</td></tr></table></center>]]></description><Snippet></Snippet> <styleUrl>#KMLSTYLER</styleUrl><Polygon>
<outerBoundaryIs><LinearRing><coordinates>116.051599946587,-31.8805716682418,2.5 116.051584490824,-31.8806014941556,2.5 116.051558963444,-31.8806507523751,2.5 116.051544294265,-31.8806452584301,2.5 116.051538606256,-31.8806431279619,2.5 116.051527310386,-31.8806388963569,2.5 116.05151960212,-31.8806360101066,2.5 116.051506800379,-31.8806312149261,2.5 116.051501205564,-31.8806291186749,2.5 116.051494481337,-31.8806266005411,2.5 116.051489384121,-31.8806246915828,2.5 116.051474178215,-31.8806189956772,2.5 116.051457900678,-31.8806128990709,2.5 116.051454055868,-31.8806114592059,2.5 116.051441880336,-31.8806068985664,2.5 116.051426255097,-31.8806010462762,2.5 116.05142760624,-31.8805984527044,2.5 116.051437634913,-31.8805791956855,2.5 116.051441739894,-31.8805713131875,2.5 116.05144239447,-31.8805700569518,2.5 116.051443087228,-31.8805687259724,2.5 116.051451060525,-31.8805534173635,2.5 116.051450972913,-31.8805533863791,2.5 116.051439226676,-31.8805491067081,2.5 116.05143232656,-31.8805465920477,2.5 116.051425780571,-31.8805442077377,2.5 116.051431313227,-31.8805332006531,2.5 116.051445208798,-31.8805055597001,2.5 116.051464590097,-31.8805127474273,2.5 116.051474003979,-31.8805162386544,2.5 116.051486923606,-31.8805210299286,2.5 116.051494384268,-31.8805237962032,2.5 116.051499675493,-31.8805257592885,2.5 116.051501425576,-31.880526407695,2.5 116.051503196155,-31.8805270642361,2.5 116.051514723553,-31.8805313390757,2.5 116.051512891543,-31.8805353993031,2.5 116.051511478753,-31.8805385319837,2.5 116.051515508058,-31.8805400418666,2.5 116.051523294591,-31.8805429574355,2.5 116.051528786905,-31.8805450146084,2.5 116.051545219115,-31.8805511698284,2.5 116.051552027209,-31.880553718916,2.5 116.051558388003,-31.8805561018379,2.5 116.051560520061,-31.8805569015543,2.5 116.051563334262,-31.8805579537948,2.5 116.051580467229,-31.8805643712514,2.5 116.051585415327,-31.8805662264138,2.5 116.051588395384,-31.8805673421489,2.5 116.05159276203,-31.8805689774654,2.5 116.051599946587,-31.8805716682418,2.5</coordinates></LinearRing></outerBoundaryIs></Polygon> </Placemark>
<Placemark>
<description><!CDATA[<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor='#E3E3F3'><th>Shape_Length</th><td>52.0334446426319</td></tr><tr bgcolor=''><th>BASE_MAX</th><td>40.91108944</td></tr><tr bgcolor='#E3E3F3'><th>Z_AVE</th><td>43.05</td></tr><tr bgcolor=''><th>ZMIN</th><td>43</td></tr><tr bgcolor='#E3E3F3'><th>BULDNG_HGT</th><td>2.5</td></tr><tr bgcolor=''><th>ZMAX</th><td>43.1</td></tr><tr bgcolor='#E3E3F3'><th>BASE_AVE</th><td>40.63367674</td></tr><tr bgcolor=''><th>CAPT_DATE</th><td>22/11/2001</td></tr><tr bgcolor='#E3E3F3'><th>geodb_oid</th><td>3</td></tr><tr bgcolor=''><th>OBJECTID</th><td>3</td></tr><tr bgcolor='#E3E3F3'><th>QUALITY</th><td>1</td></tr><tr bgcolor=''><th>PIN</th><td>190757</td></tr><tr bgcolor='#E3E3F3'><th>POLY_TYPE</th><td>footprint</td></tr><tr bgcolor=''><th>BASE_MIN</th><td>40.35626404</td></tr><tr bgcolor='#E3E3F3'><th>Shape_Area</th><td>146.866223839644</td></tr></table></center>]]></description><Snippet></Snippet> <styleUrl>#KMLSTYLER</styleUrl><Polygon>
<outerBoundaryIs><LinearRing><coordinates>116.039081808282,-31.8768122594757,2.5 116.039077549067,-31.8768210391491,2.5 116.039077203028,-31.8768217548923,2.5 116.039076853181,-31.8768224769921,2.5 116.039076476582,-31.8768232531657,2.5 116.039075862922,-31.876824519224,2.5 116.039071448839,-31.8768336201899,2.5 116.039071104737,-31.8768343295623,2.5 116.039065853341,-31.8768451562417,2.5 116.039065432756,-31.8768460246713,2.5 116.039063316507,-31.876850389067,2.5 116.03905558754,-31.8768663261,2.5 116.039032111994,-31.876914728857,2.5 116.038948100684,-31.876884863001,2.5 116.038933362874,-31.8768796241074,2.5 116.038897285366,-31.8768667976587,2.5 116.038904178744,-31.8768531434884,2.5 116.038919793499,-31.8768222060889,2.5 116.038923309905,-31.8768152406474,2.5 116.038928587384,-31.8768047861213,2.5 116.038972829325,-31.87682045672,2.5 116.038980036202,-31.8768057960203,2.5 116.038982094513,-31.8768016067867,2.5 116.038985238305,-31.8767952132137,2.5 116.03898688189,-31.8767918685083,2.5 116.038992269352,-31.8767809103634,2.5 116.039013867468,-31.876788472716,2.5 116.039028278027,-31.8767935175644,2.5 116.039038798415,-31.8767972016488,2.5 116.039081808282,-31.8768122594757,2.5</coordinates></LinearRing></outerBoundaryIs></Polygon> </Placemark>
<Placemark>
<description><!CDATA[<center><table><tr><th colspan='2' align='center'><em>Attributes</em></th></tr><tr bgcolor='#E3E3F3'><th>Shape_Length</th><td>55.7337538154969</td></tr><tr bgcolor=''><th>BASE_MAX</th><td>65.18875625</td></tr><tr bgcolor='#E3E3F3'><th>Z_AVE</th><td>66.75</td></tr><tr bgcolor=''><th>ZMIN</th><td>66.6</td></tr><tr bgcolor='#E3E3F3'><th>BULDNG_HGT</th><td>2.5</td></tr><tr bgcolor=''><th>ZMAX</th><td>66.9</td></tr><tr bgcolor='#E3E3F3'><th>BASE_AVE</th><td>64.77995018</td></tr><tr bgcolor=''><th>CAPT_DATE</th><td>22/11/2001</td></tr><tr bgcolor='#E3E3F3'><th>geodb_oid</th><td>4</td></tr><tr bgcolor=''><th>OBJECTID</th><td>4</td></tr><tr bgcolor='#E3E3F3'><th>QUALITY</th><td>1</td></tr><tr bgcolor=''><th>PIN</th><td>190434</td></tr><tr bgcolor='#E3E3F3'><th>POLY_TYPE</th><td>footprint</td></tr><tr bgcolor=''><th>BASE_MIN</th><td>64.37114411</td></tr><tr bgcolor='#E3E3F3'><th>Shape_Area</th><td>146.615229861613</td></tr></table></center>]]></description><Snippet></Snippet> <styleUrl>#KMLSTYLER</styleUrl><Polygon>
<outerBoundaryIs><LinearRing><coordinates>116.051436774146,-31.8803999458241,2.5 116.051438162782,-31.8804004478626,2.5 116.051444731291,-31.8804028243582,2.5 116.051467324042,-31.880411000245,2.5 116.051471635046,-31.8804029117568,2.5 116.051483001295,-31.8804070273577,2.5 116.051485830734,-31.8804080525756,2.5 116.051487869891,-31.8804087893422,2.5 116.051505251034,-31.8804150841447,2.5 116.0515063694,-31.8804154883847,2.5 116.051507292045,-31.8804158225212,2.5 116.051522155029,-31.8804212045751,2.5 116.05152236565,-31.8804212811751,2.5 116.051525953719,-31.8804225802396,2.5 116.051543239821,-31.8804288392082,2.5 116.051550881953,-31.880431605237,2.5 116.05155600776,-31.8804334617264,2.5 116.051556846518,-31.8804337665023,2.5 116.051576393579,-31.8804408437043,2.5 116.051578604204,-31.8804416440065,2.5 116.051598785001,-31.8804489510191,2.5 116.051600919206,-31.8804497236128,2.5 116.051603426194,-31.8804506314849,2.5 116.051605905219,-31.8804515295703,2.5 116.051606464403,-31.8804517316899,2.5 116.0516046844,-31.8804552814733,2.5 116.051602027752,-31.8804605807063,2.5 116.051601563684,-31.8804615031297,2.5 116.051588156374,-31.8804882394177,2.5 116.051585778572,-31.8804929820067,2.5 116.051585503564,-31.8804935291008,2.5 116.05158503372,-31.8804944674446,2.5 116.051584548584,-31.8804954376014,2.5 116.051565449855,-31.8805335214136,2.5 116.051548547249,-31.8805274456971,2.5 116.051544770807,-31.8805260893554,2.5 116.051539406264,-31.8805241608448,2.5 116.051534953209,-31.8805225600016,2.5 116.051517942482,-31.8805164467583,2.5 116.05151589397,-31.8805157099223,2.5 116.051513867824,-31.880514981235,2.5 116.051509576932,-31.8805134390696,2.5 116.05150351712,-31.8805112611279,2.5 116.051488553055,-31.8805058831067,2.5 116.051488713875,-31.8805055251269,2.5 116.051493463319,-31.8804949990838,2.5 116.05149828934,-31.8804843028019,2.5 116.051477597223,-31.8804766870547,2.5 116.051474943154,-31.8804757094395,2.5 116.051471155883,-31.8804743147023,2.5 116.051460973843,-31.8804705671159,2.5 116.051458263849,-31.8804695699267,2.5 116.051453943598,-31.8804785602855,2.5 116.05144718174,-31.8804760642174,2.5 116.051442494289,-31.8804743339137,2.5 116.051436395932,-31.8804720838453,2.5 116.051428976153,-31.8804693450104,2.5 116.051418715939,-31.8804655585248,2.5 116.051407384046,-31.8804613761276,2.5 116.051406545337,-31.880461066562,2.5 116.05140884358,-31.8804564207604,2.5 116.051412836408,-31.8804483458637,2.5 116.051416615233,-31.8804407067711,2.5 116.05142030619,-31.8804332442181,2.5 116.051423420203,-31.8804269474875,2.5 116.051426730988,-31.8804202531366,2.5 116.051433396498,-31.8804067753665,2.5 116.051436271714,-31.8804009605492,2.5 116.051436774146,-31.8803999458241,2.5</coordinates></LinearRing></outerBoundaryIs></Polygon> </Placemark>
<Placemark>

[petetw9]

So.......there's a very small portion of the "refusing to attach" file!!!

[tekgergedan]

This portion works fine with four purple polygons.

[ManoM]

Hi petetw9,

This works for me as well. What I would do at this point is extract your files from the kmz file and create a new one. Here are some steps to do that, assuming you are using a Windows XP machine:

1) Change the extension of your file from .kmz to .zip. For instance, if you have a file foo.kmz, change it to foo.zip. You can do this by right clicking on the file and selecting rename. If you cannot see the .kmz extension, you need to change your options so that you can. Go to your Windows Control Panel and select Folder Options. Change to the View tab. Uncheck the box "Hide extensions for known file types".

2) Right click on the file and choose Extract All.

3) Create a new folder and name it what you want the new file to be called, but without an extension.

4) Copy all the contents of that file to the new folder.

5) Right click on the new folder and select Send To->Compressed (zipped) Folder

6) There should now be a new zip file in the same directory as your new folder, name FolderName.zip. Rename that file to FolderName.kmz.

I hope that helps.
ManoM

[Dallasnightz]

Help my KMZ is not working , everytime I try and open it it gives me an error and Google earth shuts down

Can anyone help

I can send you the DMP and KMZ file if you send me your email

Thanks ALL

[ManoM]

Hi Dallasnightz,

You can post your kmz file to this forum and we'll try to debug.

ManoM

[petetw9]

Yes. This is the problem. Any of these files work fine individually, (though the large one with about 150 000 of those purple polygons tends to just crash) it is just when another is added that the parse error shows up - even if the file worked fine individually. AND if the first file is removed the 'error' file no longer has the parse error.

[petetw9]

So, it would seem no one has an answer to the Parse error problem or the uploading attachments to this website!! Typical. More rubbish!

[simon_a]

Hello Pete,

The problem is that it would seem no-one is in a position to replicate the parse error problem you are having because of the problem with uploading files.

There's nothing obvious about the parse error issue so it is just speculation until someone can re-create it. The size of your files also creates problems in the attaching.

It's difficult to pin down the attachment problem - I'm able to attach up to 20MB successfully; I guess it could be a problem with your browser but that's almost impossible to say too. Is there any way you could post these files to another hosting provider or FTP site?

Regarding your parse error: this kind of thing is normally due to GE now understanding the structure of a badly formed KML file. However, this is clearly not the case in your example as files load individually with no problem. This leads me to two possible explainations: firstly, that two (or more) files are interfering with each other in some way (maybe trying to create a reference to something twice) or that you have uncovered some kind of limit in GE by the sheer size of the data import, for example a maximum number of polygons or points.

It may be possibe to narrow this down by trying different combinations of files. Clearly, there is one file at least that causes a problem with others. Have you tried loading combinations of this file with just one other file to see if you get the problem with only two files? I guess you would need to try this file out with every other file individually (only two at a time) to see if the problem turns up.

There are lots of helpful people here who will do their best to give you a hand if they can - the complexity of your issues may make this a slow process...



Simon.

[petetw9]

Thanks for your response and suggestions Simon. I guess I am frantically trying to get some results and am having so little success that the blood is boiling....sorry. The size factor seems to be an issue. I have three kml's that I have played with in detail. There is a large, medium and small. I have discovered that I can only add them in the order: medium, large, small. Any other combination results in the parse error. Because I had so many problems in working this out, I tried merging all three together. Trying to open the resultant merged file simply crashed the entire computer. These kml's have been created using FME's kml writer. I am currently experimenting with Arc2Earth which (in the Export department anyway) seems to work better HOWEVER, the trial version is limited to only 5000 features, so the files aren't big enough to give trouble.
I will try some more ideas.

[petetw9]

Hi All,

I have now uploaded these three files to our ftp site. The address is;
ftp://ftp.dli.wa.gov.au/gsb/GSM/kml/

In that folder is: SePth_3D_hgt.zip.
This is all three kml files I spoke of compressed together.
I hope this is helpful.

Thanks

[simon_a]

Hello Pete,

I also loaded these in this order: large, small medium; I got no error.

They take a while to load on my machine so I haven't got time to test all 6 combinations of loading order right now but maybe someone else will. Have you tried different machines?

You may have simply found a problem that is very unlikely to happen but still possible(?)

Good to see that you worked something out though - looks like an interesting project!

One more thing: these are very large files in themselves - you may find it better to split the data into smaller groups...



Cheers,

Simon.

[ManoM]

Hi petetw9,

I downloaded your files. I was able to load them in the order small, medium, large, and not have it crash. However, it was exceedingly slow. Like simon_a, I encourage you to cut your files up into many smaller pieces. You are putting a really large memory burden on GE and your computer. With the three files running, Google Earth was using over 500 megs of RAM on my Windows XP box. Over 200 megs of that is just holding those files in memory. Another option is to get much more memory and the best 3D card you can buy, which might solve some of your problems.

ManoM

[petetw9]

Thanks for your efforts. It seems weird that I constantly get the error and others don't seem to. I have 3Gb of RAM in my box to deal with this sort of data size but graphics cards have been somewhat troublesome. I had an NVIDIA quadro 256 which just didn't work so while I get approval for, and testing of, a more expensive and better card I am running an ATI 128, which quite surprisingly works (a bit).

[Rufftgeo]

Hi,

I am receiving the same problem. I have tried changing the file to a zip document but am unaware of the method to opening the file and fixing the coding. When I open it it is in Egyptian Cairo. The zip files were created after the KML files would not open in google earth. I created another attempt of the KMZ file. I really appreciate any guidance. 

I have attached the documents below.

[Rufftgeo]

If I place point features instead of polygons I am able to open the KML file in google earth. If anyone has any recommendations I would greatly appreciate it. I am trying to open a KML file created through arcmap 10 in google earth.

Thank you,

Kelsey

[Noisette]

Hi, extracting the doc.kml from your kmz file, this is where the error is:

<Document id="<70&#37; Woodland Parcels 2">

  <name><70&#37; Woodland Parcels 2</name>

  <Snippet></Snippet>

  <Folder id="FeatureLayer0">

    <name><70&#37; Woodland Parcels 2</name>

I'm not familiar with arcmap, but if you need the < symbol in the name, it needs to be &lt; in the kml file, as in the attached example.  

[Jason M]

FYI. This thread is duplicated in the 'Advanced Support for KML' discussion group with the same answer.

https://groups.google.com/d/msg/kml-support-advanced/tEwhhlmifHs/NmkiC70r_sYJ