Failed to Add New Component - Import KMZ

Issue present in both Firefox and Chrome

New Project, New Component, Import, selected kmz fails to load Import as Destination, Path, or Map.
Tried using both terrain and elevated kmz files produced from Global Mapper Pro v23.1 (b030822), with the last iteration having the following settings at the time of export from Global Mapper:

Not sure what I should try next.
Also, there wasn't any clear means of attaching the sample .kmz files - is this forum interface the only means of providing bug report feedback?
Comments
12 comments
FWIW, these kmz files load in Google Earth Pro without issue.
Still not seeing the .kmz file showing on the web browser interface; however, note that the user entered description suggests otherwise.
Interestingly, I was able to load kmz files (both area and line features) into the browser's workspace without issue using the ADD LAYER, however, they're impotent in terms of being recognized as a NEW COMPONENT.
Can you provide a link to the KMZ file on Dropbox or similar?
Thank you for your quick reply Jim.
There are (3) separate kmz files with polygon and line features in the folder here:
https://drive.google.com/drive/folders/1PXH6UfbnpmD0KHB-P4TQ_Fj3p0w3yPhR?usp=sharing
Let me know if there's any issue with their formatting.
FWIW - I'm totally new to Dronelink & its web interface and these files were my first attempted Component uploads. While I expect I screwed up somehow on my end, I thought it still worth the time and bother to pass along this feedback.
The features in the KMZ need to be one of these:
Point features weren't included in any of the (3) shared kmz files; however, polygon and line features were included. If you open the (3) files in any GIS applications or Google Earth, you'll see that.
The issue is you have it inside of a MultiGeometry node, which the code does not handle:
This version works:
Thank you for looking into this Jim.
I'm no coder, but shouldn't the <MultiGeometetry> object (as defined in KML Version 2.2) be allowed by Dronelink?
In the mean time, should Dronelink users only use kml files that are produced by Google Earth?
Maybe, I am just pointing out that the code isn't written to handle it right now, so moving this to feature requests.
That was our primary test case, but as long as you produce KML files that our code handles, it doesn't matter where they come from.
I'm just glad you figured out what the issue was. Thank you!!
The work around that I proposed works, BTW:
Please sign in to leave a comment.