Mr. Coffee
Well-Known Member
- Region
- USA
- City
- A Demented Corner of the North Cascades
"Plan your trip, but plan to ditch your plan."
Based on some discussion in other threads, I thought I'd open up the floor and put out some thoughts about planning bike trips and some of the things that might go into it. There is kind of a sliding scale of necessity here: if you are making a short ride in an area you are very familiar with you probably don't need much of a plan at all, but if you are making a longer and more complicated trip or are riding with a larger group you'll need more of a plan, and possibly a pretty elaborate one.
"Plans are useless but planning is essential."
In general, one of the more entertaining parts of trip planning is playing around with maps and figuring out where to go. The introduction of various GPS-based cycling apps has made this process pretty fun and almost like playing an interesting video game. These can be a good starting point. Also very helpful is Google Maps and Google Street View.
You might also want/need to scout out parts of your trip. You might do that on a bike or you might use an actual motorcar to do the work. I'll scout to get a feel for what the road surface is like, what complex intersections look like from the ground, what is in stock at various markets on the route, and maybe also getting beta on places to stay along the way. It is also a good idea to make liberal use of your phone and email to ask questions and get more and better information.
It is also a good idea to designate some control points (or decision points). In my terminology those are convenient locations (usually chosen as places you'd like to stop anyway) where it is a good idea to take stock of how the trip is going so far and deciding if you want to change your plan. Some of the questions I'd ask myself at such a point are: "are we on schedule?", "is the weather especially bad or good?", "am I okay?", "is the bike okay?" If you are in a group having such agreed on locations where everyone can gather and take stock of the trip so far is a Really Good Idea.
Also when going on a nontrivial expedition, it is very wise to let some responsible person know what your plan is. When you give them your plan, also attach photos of your bike and you in what you wear on your bike. If you are camping include photos of your tent or shelter. On a multi-day trip have prearranged check in times and dates -- this is kind of on a sliding scale and I generally don't check in more than every other day, although on a complicated and difficult trip this may be twice a day.
If the group is beyond a certain size you probably need to write all this stuff down. If riding in a small group you can huddle over coffee and figure out the Plan for the day -- it helps if someone is carrying a tablet because it is easier for people to see everything.
Based on some discussion in other threads, I thought I'd open up the floor and put out some thoughts about planning bike trips and some of the things that might go into it. There is kind of a sliding scale of necessity here: if you are making a short ride in an area you are very familiar with you probably don't need much of a plan at all, but if you are making a longer and more complicated trip or are riding with a larger group you'll need more of a plan, and possibly a pretty elaborate one.
"Plans are useless but planning is essential."
In general, one of the more entertaining parts of trip planning is playing around with maps and figuring out where to go. The introduction of various GPS-based cycling apps has made this process pretty fun and almost like playing an interesting video game. These can be a good starting point. Also very helpful is Google Maps and Google Street View.
You might also want/need to scout out parts of your trip. You might do that on a bike or you might use an actual motorcar to do the work. I'll scout to get a feel for what the road surface is like, what complex intersections look like from the ground, what is in stock at various markets on the route, and maybe also getting beta on places to stay along the way. It is also a good idea to make liberal use of your phone and email to ask questions and get more and better information.
It is also a good idea to designate some control points (or decision points). In my terminology those are convenient locations (usually chosen as places you'd like to stop anyway) where it is a good idea to take stock of how the trip is going so far and deciding if you want to change your plan. Some of the questions I'd ask myself at such a point are: "are we on schedule?", "is the weather especially bad or good?", "am I okay?", "is the bike okay?" If you are in a group having such agreed on locations where everyone can gather and take stock of the trip so far is a Really Good Idea.
Also when going on a nontrivial expedition, it is very wise to let some responsible person know what your plan is. When you give them your plan, also attach photos of your bike and you in what you wear on your bike. If you are camping include photos of your tent or shelter. On a multi-day trip have prearranged check in times and dates -- this is kind of on a sliding scale and I generally don't check in more than every other day, although on a complicated and difficult trip this may be twice a day.
If the group is beyond a certain size you probably need to write all this stuff down. If riding in a small group you can huddle over coffee and figure out the Plan for the day -- it helps if someone is carrying a tablet because it is easier for people to see everything.