The routes were transferred from Basecamp to my Garmin 660 with no issues at all. Last years tour of Europe went without a hitch. (Not much use if you want to travel via numerous towns, attractions, and use your own routes between them). Gooogle has it’s limitations such as if your planning a multi stop trip, Google limits you to only 10 destinations per trip. Great for making sure you’ve chosen some nice biking roads. You can even send the whole route to Google Earth from Basecamp and watch a simulated tour flying about 60 feet above the roads you will be driving on. While planing the route I could simply click a button and it would take me to Google Earth and superimpose any waypoints onto the Google Earth image. Basecamp allowed me to imput what time to leave, and worked out what time I would arrive at my stops, I even input layover times for lunch, refules etc. Included were fuel stops, lunch stops and coffee stops. The route was split into different days, starting at the Hotel, traveling some routes I planned myself, some imported motorcycle routes from the internet in GPX format and some combined of my own plans and imported routes. Last year I planed all the routes for a two week tour from my home in England, taking in France, Belgium, Germany, Austria, Switzerland and Luxembourg. I persevered, watched some tutorials on the internet and now like it better than Google Maps for planing long journeys. It was not very intuitive and I was about to give up on it until my friend told me some of it’s benefits. The actual road for the ride was great though. Base Crap did give me the exact route on the GPS, but it sure was a long and painful "road" to get it there. Microsoft Streets export also gave me a flight plan. Nothing but straight lines and turns that a plane would need to do to avoid mountains and airport approach/departure lanes. Google is generally very easy to plan a route, but trying to export to a GPS tends to give you a flight plan. I would have spent much less time putting the route directly into the GPS using Google maps to get map coordinates to set the way points. I had to put in at least 15 way points, and each new way point took exponentially more time to remove tons of loops and backtracking. At least two hours later, I finally had a match. So, I used Base Crap to duplicate the route I spent less than ten minutes on Google with. But recently, I wanted to get a more detailed route directly on my GPS for a 100 mile very limited major highway route. My zumo gets a few points set later in stages when I am heading out.
I call it "Garmin Base Crap!" My usual for a trip is spending a few minutes with either Microsoft Streets (version is a bit old now) or Google Maps. Yes, no argument from me, a single route with 300 way points would be far beyond Google Maps and a phone to solve unless one had months in advance (maybe years?. Do they give you minutes, hours, days, or weeks to solve that? I'm not being a wise guy, I really don't know.ĭo you use a laptop or desktop to solve that or can you solve it on the Garmin itself (that is, is the Garmin just a display device for a problem that is solved on another platform?). In that sense, the difference between the typical idea of "many stops" and "300" stops is HUGE. usually constrained by how much time they ride in a day or two, no problem with a phone imo. how much time do they give you in advance to solve a routing problem like that?įor most riders, "many stops" for a given route might be a dozen or less. yes, I agree, that would be a very complex problem. Click to expand.I'm always interested in learning new stuff.Ĭan you provide more detail and perhaps the method used to identify and input "300 bonus locations".
0 kommentar(er)
