Je pense qu'il s'agit d'un bug de la moulinette de parawing et/ou d'un bug de googlemaps et/ou une limitation de google maps
En fait, dans les kmz qui ne marchent pas (en fait, j'ai juste essayé avec celui que tu donnes), l'arborescence est:
Archive: get_kml.php?trace=6627-26-06.kmz
Zip file size: 464665 bytes, number of entries: 16
-rw-a-- 0.0 fat 1235 b- defN 13-May-26 23:26 images/Vario.png
-rw-a-- 0.0 fat 1314 b- defN 13-May-26 23:26 images/Altitude.png
-rw-a-- 0.0 fat 1289 b- defN 13-May-26 23:26 images/Speed.png
-rw-a-- 0.0 fat 1540 b- defN 13-May-26 23:26 images/Time.png
-rw-a-- 0.0 fat 1400 b- defN 13-May-26 23:26 images/Distance.png
-rw-a-- 0.0 fat 1093 b- defN 13-May-26 23:26 images/Glide Ratio.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/VarioTime.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/VarioDistance.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/AltitudeTime.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/AltitudeDistance.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/SpeedTime.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/SpeedDistance.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/DistanceTime.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/Glide RatioTime.png
-rw-a-- 0.0 fat 0 b- defN 13-May-26 23:26 images/cfdDistanceTime.png
-rw-a-- 0.0 fat 6859087 b- defN 13-May-26 23:26 /tmp/doc.kml
et dans un kmz qui marche:
Archive: toto.kmz
Zip file size: 465379 bytes, number of entries: 16
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/AltitudeDistance.png
-rw-r--r-- 3.0 unx 1314 bx defN 13-May-26 23:26 images/Altitude.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/AltitudeTime.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/cfdDistanceTime.png
-rw-r--r-- 3.0 unx 1400 bx defN 13-May-26 23:26 images/Distance.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/DistanceTime.png
-rw-r--r-- 3.0 unx 1093 bx defN 13-May-26 23:26 images/Glide Ratio.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/Glide RatioTime.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/SpeedDistance.png
-rw-r--r-- 3.0 unx 1289 bx defN 13-May-26 23:26 images/Speed.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/SpeedTime.png
-rw-r--r-- 3.0 unx 1540 bx defN 13-May-26 23:26 images/Time.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/VarioDistance.png
-rw-r--r-- 3.0 unx 1235 bx defN 13-May-26 23:26 images/Vario.png
-rw-r--r-- 3.0 unx 0 bx stor 13-May-26 23:26 images/VarioTime.png
-rw-r--r-- 3.0 unx 6859087 tx defN 13-May-26 23:26 doc.kml
16 files, 6866958 bytes uncompressed, 462655 bytes compressed: 93.3%
Y'a juste le doc.kml qui n'est pas mis au même endroit (d'ailleurs, parawing semble utiliser en plus un chemin absolu, et ça, c'est mal dans un zip)
Et quand on lit la doc de google sur le format KMZ:
Put the default KML file (doc.kml, or whatever name you want to give it) at the top level within this folder. Include only one .kml file. (When Google Earth opens a KMZ file, it scans the file, looking for the first .kml file in this list. It ignores all subsequent .kml files, if any, in the archive. If the archive contains multiple .kml files, you cannot be sure which one will be found first, so you need to include only one.)
Donc c'est bien expliqué que google earth il cherche et prend le premier, mais que la spec du KMZ, c'est : "tu mets un fichier kml à la racine".
Man's, un fix pour parawing ?