Hi,

Since a few days ago KMZ files recently exported from Google My Maps are producing a parsing error message when you try to add them to Little Navmap. This happens also with the latest tool version just released. However any KMZ file that was exported in the past works well, because one file I exported last week can be added to Little Navmap without issues. It seems Google has recently changed the export format because I just created a brand new map today and added one marker and when exporting it the error also appears. With KML file the exportation works well and they can be loaded without problems, but you lose all the icons, which is the added value of using KMZ.

Could you please take a look to it? I use some KMZ files with relevant POIs and airports to help me creating the flightplans so I would really appreciate to continue using them.

Cheers

Edited June 15, 20223 yr by geloxo

KML code is a part of the Mable widget used by LNM and this was not modified for ages. Did something in your KML/KMZ files change?

I'd rather use the LNM userpoints / CSV to show POIs, BTW.

Alex

The problem is that Google My Maps only allows to export as KMZ or KML, not as CSV. I didn´t change anything, except adding a few extra POIs to my map. But indeed if I export now again the map that I modified last week (which original KMZ works well with your tool) the exported KMZ today drops the error. Also, as I explained, if I create a new map and add just one POI the error appears again, so my original map is not corrupted as new ones also have this issue. I´m using Chorme as explorer but I was using it last week as well. This is really bizarre. I never had problems with that using your tool in the past.

Cheers

Edited June 15, 20223 yr by geloxo

I'd not use KML/KMZ if the files contain only point objects.

There are online KML to CSV converters like this one: https://www.convertcsv.com/kml-to-csv.htm

You have to adjust the CSV to fit LNM. You can do this using LibreOffice Calc or MS Excel. The LNM CSV is described here and has only a few required fields (only coordinates): https://www.littlenavmap.org/manuals/littlenavmap/release/2.6/en/USERPOINT.html#csv-data-format

The Marble KML support is buggy. Not my code and KML is quite variable which does not make it easier.

Alex

 

Thanks for reply. I have tried to re-export the KMZ today again and now it works well. I tested it with your latest release and with the previous. So clearly there was something buggy on Goggle My Maps side during last days that appears to be fixed now. Thanks for the hints about CSV too.

Cheers