Streets and Trips, Time Estimates

[eejohnson]

Hey Folks…
I am planning my first cross country trip (Virginia to Oregon and back, close to a month on the road) and I have been using Streets and Trips to lay it out. However, when I was checking the time the software was allowing for parts of the trip, I realized that for the day I was going through Yellowstone had been dramatically under-estimated. The software had worked out a time that would require an average of 68 mph! To compound this, the actual speed limit in the park is 45 mph; a speed you are NOT going to average during tourist season. In the past I have used S&T to plan out shorter trips and the timing seemed good with the speed setting on average. This error has me worried about the timing on the rest of the trip.

So… on with the questions:

Can anyone with some S&T experience let me know how well it does with the time estimations?

Are there any suggestions on how to set up the software to give the best time estimates?

My Garmin seems spot on for timing, so I tried Garmin’s Base Camp. The timing did seem better but the software interface is awful and I don’t think I could plan out the days as easily with it.

So…is there a better software choice for this kind of planning?

Thanks,
Eric

 

[AA1PR]

mine seems to be close enough for what I do

go to route> goto more options and set up your driving speeds from there

once there driving speeds tabs is the one that I tweak most often along with flexibility

never truly played or altered segments though

 

[SilverBullet]

Yup, driving speeds is key. Also, remember that these programs always account for "no traffic" times. So in NP traffic is a given, so just adjust your speed down.