Duplicate times shown in schedule viewer for loop routes that share same start point and destination

[GoogleCodeExporter]

When displaying a route in schedule viewer, the following format yields
duplicate times for the stop that shares the end point of one trip and
start point of the next trip:

01ANYDAYBUS,10:00:00,10:05:00,HOME_BUS_STOP,1,,,
01ANYDAYBUS,10:10:00,10:10:00,BUS_STOP_A,2,,,
...
01ANYDAYBUS,10:25:00,10:25:00,BUS_STOP_D,5,,,
01ANYDAYBUS,10:30:00,10:35:00,HOME_BUS_STOP,6,,,
02ANYDAYBUS,10:30:00,10:35:00,HOME_BUS_STOP,1,,,
02ANYDAYBUS,10:40:00,10:40:00,BUS_STOP_A,2,,,
...
02ANYDAYBUS,10:55:00,10:55:00,BUS_STOP_D,5,,,
02ANYDAYBUS,11:00:00,11:05:00,HOME_BUS_STOP,6,,,
03ANYDAYBUS,11:00:00,11:05:00,HOME_BUS_STOP,1,,,

The schedule viewer output (in the pop-up balloon) shows:

10:00   The Google Transit
10:30   The Google Transit
10:30   The Google Transit
11:00   The Google Transit
11:00   The Google Transit

Is there a workaround for this, or should stop_times.txt be formatted in a
different way? Maybe I am overlooking something here. All other stops are
fine. This is only the case for the stop with shared times.

Thanks.

Original issue reported on code.google.com by shawn.bo...@gmail.com on 18 Jul 2008 at 2:59

[GoogleCodeExporter]

Note the schedule viewer doesn't know anything about block transfers and 
calendars.
Are 01ANYDAYBUS and 02ANYDAYBUS in a block so you expect only one stop in the 
bubble?
Maybe the bubble should include the trip id to help people work out what it is
displaying.

Original comment by tom.brow...@gmail.com on 19 Jul 2008 at 12:13

• Added labels: App-ScheduleViewer, Language-Python

[GoogleCodeExporter]

I have this same problem with schedule viewer.  I have an hour-long loop that 
spends
the first half-hour going from point A to B, and the 2nd half going from B to 
A.  If
you click on point B, it gives a time of xx:30 with a destination of point B, 
and a
time of xx:30 with a destination of point A.  If i change my arrival time of the
first half to xx:25, schedule viewer will post xx:25, regardless of the 
departure
time.  I could easily change the 2 half-hour trips to 1 hour-long trip, but i 
had
used the 2 half-hour trips to take advantage of the trip_headsign, instead of
overwriting the trip_headsign with stop_headsign for half of the loop.  
Instead, is
there a way to not show that arrival time from the first half of the loop when i
click on the stop?  The overall window can still show the arrival time.  Or 
don't
post the direction of the last stop in a trip when you click on a bus stop?

Original comment by greatest...@gmail.com on 22 Jul 2008 at 7:02

[GoogleCodeExporter]

The current goal of the schedule viewer is to make it easy to explore a GTFS. 
Showing
block transfers would be nice. Collapsing multiple trips in the stop info window
doesn't seem so useful.

If you'd like the stop info window to list both arrival and departure times 
please
make a new issue or a patch, it should be a trivial change.

RE: 2 trips with a block transfer vs 1 trip with changing stop_headsign
I'd use 2 trips if they are considered different routes, 1 trip and changing
stop_headsign if passengers think of both directions as the same route.

Original comment by tom.brow...@gmail.com on 22 Jul 2008 at 8:53

[GoogleCodeExporter]

I noticed that duplicate time displays in the stop balloons are due to the same 
route
being used on different services. That is the same text appears for a mtwtf
servicesand for ss schedule. 

If you click on the route details you can see the different service_ids - it 
would be
nice if the stop balloons and the route details displayed the service_id.

Original comment by rheitz...@gmail.com on 30 Jul 2008 at 4:39

[GoogleCodeExporter]

the stop windows in schedule view now show the service_id. after clicking on a 
trip 
the full contents of the routes.txt and trips.txt rows are shown below the map. 
The 
only thing maybe missing to help here is trip_id, but for normal feeds the 
tuple 
(service_id,stop,route name,trip headsign) should be unique.

Original comment by tom.brow...@gmail.com on 21 Sep 2009 at 7:00

• Changed state: WontFix