Trip Planner Feature is here! (BETA)

Hi
i'm testing the Trip Planner for Hiking Activity with TrekMap Italia V3 Pro, and i have to say that it is not display realist duration time of the activity.
For example if i have to go from "Rifugio marinelli" to "Monte Coglians", I already know that it will take me 5 hours more or less for the roundtrip, but the trip planner shows me 1 hour and 2 minutes..maybe the TripPlanner is not for hiking activities yet?
But as far a si can see, all hiking activities are wrong in time trip calculation
btw could be a nice feature!

Let me ask what your profile looks like for hiking. What do you have set as the average speed for your hiking profile? This would have an effect on times. I am not familiar with that specific route, but remember that BaseCamp in general will calculate the shortest route by default, so in that profile you might want to see if there are any avoidences checked. You can make a custom profile if you wish not to edit the original one and base it on hiking to get a more accurate route. Does this help?

Hi, thanks for the replay
well i cannot find where to set the average speed in my hiking profile..i'm using Baecamp for Mac..
well the route is quite correct, but it seems that BaseCamp doesn't take care of elevation or difficulty of the route..that i think it should..

Trying to Make Sense out of Trip Planner

In the past I had used MapSource to save waypoints and routes and send them to my GPS unit. Now, my nuvi 3590LMT doesn't so much want to converse with MapSource, and MapSource was rather tedious to work with regarding searching for addresses, etc. BaseCamp is really much more powerful, but the definition of routes and trips is quite confusing. I seriously need a user guide that covers these subjects. The help screens don't even acknowledge the idea of a trip or a hub, whatever that is. I don't know what it is or how to use it. Defining routes in Base Camp is pretty straight forward, but when I upload them to my 3590, they show up as "trips".

I tried creating trips in Base Camp. When I try to type in a waypoint, it grabs the bit in its mouth and starts searching before I can enter enough text to narrow down what I'm trying to specify. I have dozens of Hampton Inns in my waypoints. I have to wait a long time while Base Camp is searching through everything that starts with Hamp... before I can type more in to narrow down the search. It would be SO MUCH easier if a selection of a waypoint just displayed my waypoint list and let me select from it. I'm not sure what the Trip Planner is trying to do. I guess it is searching for all sorts of points of interest that I might want to include in my trip.

If my trip goes from Scottsdale to Santa Fe, then to Dodge City, then to Des Moines, then to Elgin, etc, the Trip planner seems to want to call this trip Scottsdale to Santa Fe, and all subsequent waypoints seem to be at a different level. I just don't understand what is happening. I need a user guide!!!

There is a bit of naming convention confusion. Let me try to clarify.

A "Trip" in terms of BaseCamp is a set of routes strung together to create a full itinerary for travel you may do. For example, if you are taking a family vacation to California from Arizona, you might put in your home address. The first route will take you to say your hotel. Then from your hotel to Magic Mountain. Then from Magic Mountain to a place to eat. Then back to the hotel. Then the next day you may go from your hotel to Disneyland. Then from Disneyland to a Dodgers Game. Then from the Dodgers Game back to your hotel. So you get the idea. It is a way to string together a number of routes in such a way as to plan a number of days travelling for business or for personal vacation. "Trips" on a device may actually mean Routes to BaseCamp. It depends on the device and how they used the naming convention. We are working with other teams to make sure that we are all on the same page. The BaseCamp trip concept is very new at Garmin and there are still a few kinks to work out.

Now, regarding your searching, we have a planned bug-fix release which will be out soon that will address some of your searching concerns.

Trip naming is just the default. You were going from Scottsdale to Santa Fe. You can rename the trips. And you can rename the hubs. A hub in this context is a set of routes that belong to a specific city. The design idea was that you might spend 3 days in LA and stay at the same hotel. LA is your "hub," i.e. a base from which to plan the rest of your activities on your trip.

Does this help to answer some of your questions? Thank you for your feedback, and please feel free to contact this forum again for more information. We are happy to answer these questions.

Let me start by saying I've not been very happy with basecamp in general, and consider myself a mapsource user who persitently tries to convert, to no avail...

That being said, I'm trying to understand "Trips". I have created many routes in my time. Trying to create a trip using trips seems a little cumbersome. My first obstacle is trying to "rubber-band" the route to go around or to specific places.

So my question is, can I manipulate the route/trip without adding a formal waypoint using the drag method?

We are working with other teams to make sure that we are all on the same page.

How fabulous is it to see this statement from a Garmin insider!! Frankly, Garmin devices and software today seem not to be a cohesive system, but things designed by groups on opposite sides of the planet who don't know each other exists. I sincerely hope that Garmin management sees the huge opportunity they have to bring disparate pieces together into a more powerful whole if they fit together as a true family of products, each supporting the other. Whether it be route recalculating, routing algorithms, map updating, BC routes vs. BC trips vs. device routes vs. device trips, the list goes on and on.

How about for starters getting the device teams to open sections of this forum for the various device classes so users who frequent this forum (generally high level users IMO) can give them feedback for the devices? (I know how to submit suggestions today, I have done that, but that is a one-way street and is largely ignored from what I can tell.)

I fervently hope the "getting on the same page" effort is receiving the highest priority from upper management! I for one am cheering for you!

How fabulous is it to see this statement from a Garmin insider!!

I agree, and we have started to see some fruits of this, like Nuvi models that are not supposed to recalculate a route if it was created with the same map in Basecamp. OTOH, we still have a way to go. Trip Planner based Nuvi's have been on the market for over two years, but...

The BaseCamp trip concept is very new at Garmin

:)

The biggest problems with "routes" and "trips" in the Garmin world is that the various Garmin development teams don't seem to get the difference between routing points and "stops". They've decided that they're the same thing. At least the device developers have.

I really don't care whether you call them "routes" or "trips". I simply want to do multipoint routing that allows me to force a route/trip where I want/need it to go without treating the intermediate routing points as actual stops (eg. I may want to stop there for gas or lunch but I want the route/trip to continue to run as soon as I continue to drive, without significant intervention by me).

Why is it so difficult for the device developers to understand such a simple distinction and implement it properly? Eg. if I don't actually designate an intermediate point as a "stop" just let the route/trip keep running rather than breaking it into pieces and then forcing me to interact with the device to find and launch the next "leg".

It's not a question of whether we call them "routes" or "trips". The real issue for those of us complaining about it is that with devices that do "trips" we've lost the ability to do multipoint routing in a single route/trip.

Microsoft Streets & Trips has had the concept of "trips" for ages. It can do all of the things that the Basecamp developers are trying to reinvent with their "trips" functionality and much much more. It has had the ability to do multipoint optimized routing as part of a trip pretty much since the beginning.

If such a creaky old product as Streets & Trips got it right nearly a decade ago, why is it such a problem for Garmin's device developers and Basecamp developers? Just go buy a copy of Street & Trips to see how to do it right. Heck, just download the free 14-day trial version. It's unrestricted. Any developer that can't get the basic concept figured out in 14 days is getting paid way too much.

...ken...

If such a creaky old product as Streets & Trips got it right nearly a decade ago, why is it such a problem for Garmin's device developers and Basecamp developers? Just go buy a copy of Street & Trips to see how to do it right. Heck, just download the free 14-day trial version. It's unrestricted. Any developer that can't get the basic concept figured out in 14 days is getting paid way too much.

...ken...

They could also use Google Maps for some benchmark work for things such as route manipulation and the find feature...