I know my KML has no icon, I don't need one.
Printable View
I know my KML has no icon, I don't need one.
**LOL**
even if no own icon (bmp) is used, one is assigned automatically. But the KML should be at least iGO compliant and not a google KML that can only read from /earth/ or /maps/
Quite overloaded for an iGO kml, but never mind.
Was the kml file imported correctly into iGO?
So now you have two more files besides the kml file under content/userdata/poi. (with icon there would be three additional files).
The POIs from iGO are already displayed. But of course you have to search near the POIs.
No standard icon is displayed under WinCE, only under Android.
This particular KML has worked in iGO 2.0, 2.4, android versions and nextgen. It does not work in THIS version of iGo.
I have copied the KML, kns and kix from a different version into the userdata/poi folder and it still does not work in this version.
!* insert only KML in Data-Folder iGO_xxx\Content\Userdata\poi, not index file kns und kix !
Yes, I know, but I copied those files from a different version to see if it would recognize anything.
the problem will probably not be the KML itself, but the installation of a version with data/files from another device (e.g. save folder)
Since iGO 8.3 there hasn't actually been a version that I haven't tested on various devices - and under which no KML was recognized. There were often problems because of unadapted data.zip or voice files.
So IMO first look for the error in the system structure?
I think the problem is the .kml file.
The "original" works for me with no IGO version.
But after I changed the header of the .kml, it works with all my IGO versions.
Spoiler: Screen
[Only registered and activated users can see links. Click Here To Register...]
👍 Post #32 😉
As I said, the KML file runs without problems for me.
Both under WinCE (Becker) and Android (Primo and Nextgen).
Does iGO now create the kns and kix files itself? If not, iGO has no write access to the folder.
In "normal" installations, the userdata folder must therefore always be on the internal memory.