Service Timings , changes and other questions.

[webm...@horizons.govt.nz]

Hi All.

Apologies for the silly question but I am new at this...

I am setting up a new feed for our organisation and have come across a couple of scenarios I cannot work out, and would appreciate some guidance.

1) I have a route with up to , 10 stops but each stop is only active during certain times of the day

e.g. 

stop 1 - 7am, stop 2 - 8am, stop 3 - 9am, stop 4 - 10am, stop 5 - 11am, stop 6 - 12 midday, stop 7 - 1pm, stop 8 2pm

stop 1 - 8am, stop 2 - 9am, stop 3 - 10am, stop 4 - 11am

in this case stops 1-4 are all the same physical location.

Are all these supposed to be hooked off the same route with different trip specifications or should they have separate routes

2) I have a service where it is only active during school terms, does this get specified in the calendar file and calendar dates somehow or do I reproduce the file during these times.  This also goes for another service that has one extra stop during school times.

3) how do we handle bus stops where we have a physical stop but no timings to enter in the stop_times file, do we still include the stops in the file?

4) How do we handle a schedule that has a set time, but on a holiday it reverts to the timings from a weekend instead?  Is that set up as a second service and it is controlled through the calendar and calendar dates files? or is the existing service changed for this time?

Hopefully someone much smarter than me can offer some advice.

[Brian Ferris]

1) Generally, you would use one route, assuming that's how you advertise this service to riders normally.  See Route Organization in https://developers.google.com/transit/gtfs/style-guide for more details.  Then you would create different trips in trips.txt linked to that route, with each trip corresponding to an actual trip by a vehicle in your system.  Finally, in stop_times.txt, you would specify the series of scheduled stops for each trip.  At that point, you have complete control over which stops are used when.  For example, if stop #5 is only active from 5-7pm, you would only include that stop in trips operating between 5 and 7 pm.

2) You can create different trip entries for school vs no-school service, giving each trip different service_ids as appropriate (SCHOOL vs NOSCHOOL, for example).  Then in calendar.txt, you active the two service ids on different dates, depending on when school is in session.

3) You can include the stop in stop_times.txt but leave arrival and departure times blank.

4) Let's say you have two service_ids defined in calendar.txt: WEEKDAY and WEEKEND.  If there is a holiday on a Wednesday where you'll be running weekend service, you could have a calendar_dates.txt file like:

service_id,date,exception_type

WEEKDAY,some date,2

WEEKEND,some date,1

The first line cancels weekday service on the specified date, while the second line activates weekend service on the specified date, effectively swapping service on that date.

Brian

--
You received this message because you are subscribed to the Google Groups "GoogleTransitDataFeed" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googletransitdat...@googlegroups.com.
To post to this group, send email to googletran...@googlegroups.com.
Visit this group at http://groups.google.com/group/googletransitdatafeed?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[webm...@horizons.govt.nz]

That's fantastic thanks Brian...Now I have something more concrete to go on I think I am away...

Cheers

Chris

To unsubscribe from this group and stop receiving emails from it, send an email to googletransitdatafeed+unsub...@googlegroups.com.