Cannot Import KML data from Google's My Maps (mapsengine)

Peter Barkley shared this problem 4 years ago
Solved

I have the lastest version of Locus Pro running on a Nexus 5.


I have made a bunch of points of interest using Google's Maps Engine (or My Maps as its called now).


Within Maps Engine I click Export as KML and export the entire map.


I then place this KML file on my phone in the /sdcard/Locus/MapItems/ directory, and can view it within the "Items" tab in Locus.


When I click on the file to import the waypoints it states "Problem with file 'myfile.kml'!".


Are there logs I can see somewhere to see what the problem is? How can I trouble shoot this?

Comments (9)

photo
1

would you like to share one of your kml please?

photo
1

edit

...because it works for me as expected.


my test:

https://mapsengine.google.com/map/

create two points

export as kml


---

(i you use pc and dropbox:)

copy kml to dropbox

open dropbox on my device

---


tap my kml

open/import with locus pro

done

photo
1

Attached is the KML I am attempting to do this with.


Thanks for the help!

photo
2

thx

ok there was an error now.

brb...

nice trip btw... :)

photo
2

edit


temporary workaround:

import to google earh

export as kmz

import in locus - see clip

photo
2

Thanks that worked!

photo
2

Hi guys,


issue found on like 1873, where is color defined as "<color> 0AD98D6</color>". But color created from 7 characters do not make a lot of sense (should be 6 or 8).


I'll fix this to next Locus version 3.4.0, thanks for a report.

photo
2

nice! good point :)

line 1873:

  1. <color> 0AD98D6</color>
  2. sould be
  3. <color>ffAD98D6</color>

---


and what about the other message

"Defined area is not valid" ?


edit

oh, that's a new bug

offtopic here...

photo
1

hi,


as I wrote on different place, so once again for other users.


Notification about problem with defined area is just incorrect work of one function. it has absolutely no affect on work with Locus, it's just annoying. Will be also fixed in next version at start of next week (it will be 3.3.1, not 3.4.0 mentioned above).