private data layers not handling images included with kmz

[GoogleCodeExporter]

When a kmz includes image files as well as the doc.kml file, the images are not 
found when the kmz is loaded as a private data layer.

As an example, a layer that works fine when accessed by the public data layer 
kml through cloudfront (such as SeabirdColonyNew.kmz - see attached) can be 
downloaded and then viewed through Google Earth client just fine.
But when this same kmz is loaded as a private data layer the images are not 
found by the kml (red x's are the result).

My temporary solution has been to load the kmz onto cloudfront, create a simple 
kml that refers to that cloudfront url, and upload that simple kml as the 
private layer.  
This solution works well enough until we want to ensure that the data is truly 
private (rather than publicly available (albeit somewhat anonymous) through 
cloudfront).  

Original issue reported on code.google.com by sfletche@gmail.com on 13 Apr 2011 at 10:57

Attachments:

• SeabirdColonyNew.kmz

[GoogleCodeExporter]

Original comment by sfletche@gmail.com on 14 Apr 2011 at 5:12

[GoogleCodeExporter]

This is likely not a marinemap issue. Might be worth posting the file to the 
earth api bug tracker.

Original comment by underbluewaters on 14 Apr 2011 at 5:48

[GoogleCodeExporter]

I think it's possible my original report was misconstrued. 
I'm restating the problem here in what I hope will be clearer language...

When I upload the attached file, SeabirdColonyNew.kmz, to Oregon Marinemap (as 
a kmz upload), red x's (trade-mark ge red x in a box) appear in place of the 
image icons.  

The correct icon images do not appear until the kml folder is opened/expanded 
to show its contents, after which the folder can be opened/closed, turned 
on/off, and the icons images remain.  

When the application is refreshed with the seabird colony folder closed, the 
refreshed application returns to the red x display until the folder is opened 
again.  

Original comment by sfletche@gmail.com on 21 Sep 2011 at 6:10

[GoogleCodeExporter]

I'm certainly not volunteering to work on this as I'm pretty busy with 
OceanPlanner, but let me know if you need commit permissions on the kmltree 
project. I believe kmltree will resolve relative links to assets like images 
(at least it will for networklinks), so checking out where that url resolution 
process is happening could be a good starting point.

Original comment by underbluewaters on 21 Sep 2011 at 7:45