HomeMicrosoft


Schedule Stops - Shouldn't be this hard in Streets & Trips!
NightHawkFan
I'm going to be going on a few trips coming up soon. I plan to make a couple stops along the way and I'm having issue on how the Schedule Stop "function" [doesn't] work for me.

The setup:
Microsoft Streets and Trips 2010
Windows 7 Ultimate 64 bit
Acer laptop
I can plan out the route, add in the destination points as I go along. Here's where it gets annoying. I have the options set to depart 9am, and the end of day roughly 5pm. Seems to be about the limit for the family. All speeds are avg. If I simply add one of my stopping points as a waypoint, it has me leaving my house at 9am (ontime), spending the night along the way, and arriving at my point at about 3pm. But, I plan to stop for the night at this location, and depart the next morning 9am.

How do I tell it to leave home at the appointed time, I get to my destination when I get there, but then spend the night, and leave the next morning? Right now, what it seems to want to do is mark my stop at 5pm, then work the route backwards, all the way to the beginning, having me leave home at 10:30 am. It's not what I want.

I found this post: http://www.laptopgpsworld.com/1939-drive-time-start-stop
It seemed to be the answer, but when I set the option to "Depart at: 9am" ... it still had my arrival at 5pm, leaving home later than I'd plan.

I don't care what time I arrive at my point, I'll get there when I get there. But it would be nice for planning purposes to know what time I'm going to arrive, and in addition, how this affects the remainder of the trip.

Help? Hints? Tips? Anything? Did this even make sense? (I'll admit I'm a little frustrated as I write this.)
NightHawkFan
Oh, one more thing... this just about nearly sent me to the floor crying... I thought I'd be smart about it, let it calculate the route as a pass through, like it wants to do initially. Saw that it had me arrive at 3:30pm. So I set the Schedule Stop to "Arrive: 3:30; Depart: 9:00" ... when it recalculated my route, it had me leave my house, travel for 6 minutes to the end of the sub-division, and then scheduled a "End of Day" ...
Ken in Regina
FOUND IT!!!!!

- Right-click on your starting point and select "Schedule Stop".

- Click "Depart at:". It will default to whatever your default start time is in the "More Options..." window. You can set it to anything you want, of course.

This forces the route to start at the Depart time.

SpadesFlush
But, Ken, I think NightHawkFan has a point here.

Streets & Trips seems to give the "Arrive At" option priority over "Depart At" if both are used when scheduling a day's trip and will perform as he/she describes. I have had similar experience. I work around it. For long, multi-day trips, I usually set the route option profile start/end times quite wide so they do not get in the way, like 8 am to 10 pm. Then for over-night stops, I use the "Schedule Stop" feature but I set "Stop for:" as 1 (or how many other) night(s). The route planning will default to the Route Option Depart At time (8 am in this example) and will arrive whenever. If I am happy to arrive later than this projected Arrive At time, I may mess with the Depart At time, say by entering 9:30 rather than the default. Or adding Stop for times along the way.

In other words, I usually avoid using both manually-entered Depart At and Arrive At options for the same day. If one is important, I use only that one and let the other get calculated. I can live with this.
NightHawkFan
Spades -what you said makes sense... still didn't work for me. It still wants to set my arrival time to my stop, and rework the route backwards to my origination point. Even after I expanded my travel times. On the other hand, I could just as easily skip this stop, at which point, I've done the route enough times, I know where & when to stop and how long things will take.

Thanks for the hints... I'm going to keep playing with it...
SpadesFlush
Quote:
Originally Posted by NightHawkFan
... It still wants to set my arrival time to my stop, and rework the route backwards to my origination point....
Yes, I don't know if you can get around that. I think as long as you put in a 'hard' Arrive-at time, it will always force to that.
NightHawkFan
Tried that too... that's when it told me to leave my house, drive for 6 minutes to the end of my subdivision, and stop for the night. I may have to pull some strings and use some of my MS connections to see who to get a hold of.
SpadesFlush
MS Product people follow this Forum, so to some extent your concerns will already have been registered.
Ken in Regina
SpadesFlush, I agree that Streets&Trips' default method is annoying in the extreme. Especially the fact that if you use the route planner you cannot disable the "Start driving" and "End driving" times. All you can do is change them. And then you are forced to use other, unintuitive methods, to work around them.

NightHawkFan, did you do as I described? I tried it a number of different ways without forcing the Depart time on the departure point and it always defaults to forcing the departure time by calculating backwards from the arrival time at the first stop, just as you described. But it's really simple to work around it.

Here's exactly what I did and it works perfectly.

- Put your departure point (in this case, I used my home address) as the first entry in the route planner.

- Set this departure point as a scheduled stop.

- Set the Depart time on that stop as your planned start time.

This will force the route calculation to work from your Depart time instead of backwards.

Or am I overlooking some other subtlety to what you are attempting to do?

...ken...
NightHawkFan
Ken - Maybe if I'm a little more explicit in what I'm seeing and what I did.

And I'll give actual points so that the entire class can follow along.
Departure Point: Bellevue, Nebraska
Add Destination: Cloudcroft, New Mexico
Add Destination: Alta Loma, California

Options: Starting time 9am, Ending time 5pm, with say 2 hour fudge time.
You'll see that it Departs Bellevue at 9am, puts me somewhere in Oklahoma for the night, then departing the next morning at 9am ... so far so good. I then arrive in Cloudcroft, NM, roughly 3:30pm that second day. Great. Again, so far so good. Now, I'd like to spend the night in Cloudcroft. So I click on Cloudcroft and then click the clock button to say Schedule Stop. Now, I don't care how long I'm there, I just know I want to depart the next morning at 9am. I unselect the first option and select the "Depart At" and set for "9:00am" ...

When the directions change... I'm now departing Bellevue, NE at 10:30am... 90 minutes later than previous. In addition, I'm now arriving in Cloudcroft at 5pm. Same thing happens if I use the "Stop for 1 Night(s)" option.


What I would prefer it do is not care what time I arrive... If I get there at 2pm, I get there at 2pm... if it's 8pm, then it's 8pm, but I'm spending the night... It doesn't seem to care that I might want to spend time in town in addition to spending the night.

AHHHH! I think I have it... If I set Cloudcroft as a scheduled stop... then mark my departure point with a specific departing time... then I get the desired result... I arrive in cloudcroft at 3:30pm... and spending the night.

I think I mis-interpreted your instructions the first time Ken... I was tinkering with the Cloudcroft waypoint, when I should have been tinkering with the Departure time of the starting point.

Still think it should have been a little easier to accomplish. Or at least maybe as a setting somewhere.

Thanks for your help!
SpadesFlush
I for one am glad you got there in the end.
Quote:
Originally Posted by NightHawkFan
...
Still think it should have been a little easier to accomplish. Or at least maybe as a setting somewhere.
...
I have to agree with that. More user control over these parameters would be nice.
Ken in Regina
Yes, for my example to relate to yours, I was setting Bellevue, NE as a scheduled stop with a Depart time of 9am. Then it worked.

Yes, it should be a bunch easier. The trouble is that when you ask software developers to make it easier they tend to dumb it down instead. So if they "fix" this situation you can bet that we would lose a bunch of the flexibility that it currently provides.

...ken...
Marvin Hlavac
Quote:
Originally Posted by NightHawkFan

When the directions change... I'm now departing Bellevue, NE at 10:30am... 90 minutes later than previous.

Simply schedule the departure time of your Start location (Bellevue, Nebraska) to 9:00 am, and all should be fine.
laptopgpsworld.com About