Frequencies table "start_time" and "end_time" ignored

[Transit001]

Hello,

I am wondering why the columns "start_time" and "end_time" in the
Frequencies table are ignored by the Trip Planner? This has been the
case for a long time, goes against the GTFS specification, and has the
potential to cause misleading results to users. Can this issue be
corrected?

Thanks for any assistance.

(P.S. This is a more succinct restatement of my recent post of the
same question.)

[Joe Hughes]

Hi Transit001,

For in-depth debugging of the interactions of a particular feed with
the Google Maps trip planner, I recommend using the Google Transit
Partner Support Group:
http://groups.google.com/group/google-transit-partner-support

Cheers,
Joe Hughes
Google

[Transit001]

Joe,

I don't believe this is specific to any one feed, it is rather a
fundamental issue with the trip planner. It is difficult to make a
good feed when I don't know what features of the specification will
work and what features won't. For example, I am trying to make what
would have gone in the Frequencies table instead be iteratively
generated into an exhaustive list of stop_times. Do I really need a /
complete/ feed in order to be eligible to start testing the feed
live? The Demo Transit Agency and feeds that are currently live are
all that I've had to work with.

Thanks

[Joe Hughes]

Hi "Transit001",

The partner support group is definitely the right place to discuss the
interactions of a feed that you'd be publishing with Google Maps trip
planner.

Cheers,
Joe Hughes
Google