Error: Checksites console Error: Error in the file content - Error in the KMZ file format - (Bad state: No element)

[dougienisbet]

Hi, I wonder if anyone could give me a hint where I may be going wrong. I've tried several attempts at creating a route using oom and Google Earth and every time it fails. I've tweaked a few things but I always get the error:

Error: Error in the file content - Error in the KMZ file format - (Bad state: No element)

The only thing I could think of that I've done differently from usual is that I used the 1:20000 scale in oom as it was for a personal running route I wanted to try where I visited a few rural mileposts.

The files are:
KMZ: https://www.dropbox.com/s/mfbo4a0oil9zzf6/stones2.kmz?dl=0
KML: https://www.dropbox.com/s/nwx6poi7ipi3was/stones2.kml?dl=0

Thanks,

Dougie

[MichaelRaz]

Only a guess based on the error "No Element" but your KMZ bounding box is missing a <rotation> element.

Your KMZ:
                <LatLonBox>
                        <north>54.8318991275</north>
                        <south>54.7941698848</south>
                        <east>-1.99251678827</east>
                        <west>-2.0851159494</west>
                </LatLonBox>

Example KMZ:
                <LatLonBox>
                        <north>45.357835654</north>
                        <south>45.344926580</south>
                        <east>-75.669659797</east>
                        <west>-75.694594849</west>
                        <rotation>12.625373184</rotation>
                </LatLonBox>

You can always try just adding the rotation element in (if no rotation use 0).

If you have not used this before, something like 7zip (free) can open up the KMZ directly and you can edit the document portion within 7Zip.  In fact you can replace the actual file, rename it etc as needed, all within 7zip - very handy.

[MichaelRaz]

Just tested and the lack of the <rotation> element causes the error you see. However, I think once you fix that you will get a different error as the file name in the KMZ file folder is tile_0_0_0.jpg (same as in the doc file url reference to it).  Both need to be tile_0_0.jpg.  The extra _0 will produce a new error once the parser gets past the first one.

[dougienisbet]

Thanks for digging into this. I'm still getting to grips with the file formats and thought that KMZ files were a lot more mysterious than they actually are.

Something has clearly changed in my workflow since the first couple of local routes I created and the ones above. The next time it happens I'll have a better idea how to start diagnosing the problem.