KML file in IGO Primo GPS erraticFORUMS HOME SEARCH FORUMS

Total posts in this topic: 2
Showing newest posts first - Show oldest first
Sign in to post to this topicSIGN IN

    Page: 
    • 1
  • Photo
    plotaroute admin   Tuesday 03 Jan 2017 10:34:29

    Hi John,

    I'm not sure why the name of the route isn't being picked up, the KML file has the route name correctly recorded as per their instructions.  Maybe it is too long or contains characters that the app doesn't like?

    I think the other issue about the app getting confised with which part of the route it is on when sections overlap is a problem that also occurs with Garmin devices.  The only solution to this is to manually separate the overlapping sections of the route so that it can be sure whether you are going out or back.  This is really a bug with the navigation app as it should take into account your direction of travel but I suppose it is designed to get you to the finish as quickly as possible.  We do have a suggestion on our feature request list to provide a way of automatically separating overlapping out and back sections of a route, so you can vote for this if you like to help move it up the list (number 12).

    John

  • Photo
    Topic
    Creator
    Deleted User Tuesday 03 Jan 2017 05:33:56

    I exported my route to a KML file for installing on my IGO Primo GPS.  It loads fine, but I have two issues with it.

    First is minor, in that IGO does not read the name file and so assigns it some random street names as the title of the route.

    Second is a major, in that IGO  wants to send me back home all the time.   The chosen route has a loop that starts 40km from home, and therefore to and from that loop uses the same path.

    So the query is whether the Plotaroute version of the .KML file is compatible with either IGO8 or IGO Primo?    My gut feeling is that this is not a hardware issue, but rather one of IGO software attempting to interpret the KML file I am giving it.

    If for example I were to create a route entirely on the GPS, laboriously typing in all the waypoint co-ordinates, it will work fine.  This leads me to think there has to be an error in reading the externally created KML file.

    All suggestions gratefully received :)

    John

Page: 
  • 1