Transferring Trip Planner data to a BMW Navigator V...

Former Member
Former Member
I have created a number of Trips and when I transfer them to the internal storage on my NAV5, I get random results relative to Scheduled/Unscheduled. When I look at the temp.gpx on the NAV5 before unplugging it form my Mac, most of the Routes do not have <tmd:TripMetaData> data.

When the Trips are Exported from BaseCamp as GPX files to my Mac, all Routes do have <tmd:TripMetaData> data.

Is anyone else seeing this?
  • Former Member
    0 Former Member over 10 years ago
    The issue just got more interesting. On the NAV5 if I import the GPX file, which has all of the appropriate Meta Data for Trip Date, the results in the NAV5 Trip Planner are again random as to whether I get Upcoming Trips or Unscheduled Trips.

    So, I looks to me like BOTH BaseCamp and the NAV5 are not working as intended.
  • It seems to be working as I would expect on my 590. Using both drag and drop of a complete folder containing routes, tracks and waypoints to the card, and then importing routes to Trip Planner, as well as using the menu transfer to just send the route list to the internal memory of the Zumo 590 and importing from there, results in scheduled routes, sorted as per the first point departure time.
  • Former Member
    0 Former Member over 10 years ago
    Thanks, and I understand your lack of exuberance for the Trip Planner. I keep trying as I think it could be of value when/if things work as expected -- including the high-end GPS devices that come out of Garmin Development. I think this is an XML issue on the NAV5 side and that BaseCamp is just creating the temp.gpx file that the NAV5 "is asking for".

    Maybe the BaseCamp team can enlighten me/us as to how sending data to a device like the NAV5 or zumo590LM works.
  • Unfortunately, as far as I know, no PND has support for the Trip Planner's meta data that would make the experience better. It is still on their To Do list. The routes that are sent should all be treated as regular routes. I don't know why they would be treated differently by the NAV5.
  • Former Member
    0 Former Member over 10 years ago
    Hmmmm,

    I guess the zumo team is ahead of the game. I requested that some folks with zumo590LM's try this and they all found that the Trip Meta Data was used by the zumo590LM upon Import. I then sent my GPX file to my brother who imported it into his zumo590LM and all of the routes meta data was read as I planned it in BaseCamp.

    The reason I would expect it is because PND's have been using a "Trip Planner" app for some time now and BaseCamp chose to used the same naming [Trip Planner] in BaseCamp. As a customer that tells me that I should expect compatible behavior between these new devices that use a Trip Planner and BaseCamp. That expectation does not seem unreasonable to me.