Nice start

Nice start! I've test driven the trip planner and have a few comments. Unfortunately, the comment system is broken for me (see below), so let me try this avenue.

When calling a schedule query in the morning(PT-zone), a schedule query only returns PM departures. Example, issued on Saturday June 20 2009 at 8:58AM PT-zone:

http://developer.metro.net/tm/schedule.php?apikey=MYKEY&route=1194&stop_on=15839&stop_off=16474

The resulting departures are way in the future:

<------------- snip -------------->

N-MEMORIAL PARK STATION-AT
01:09PM
01:21PM
01:33PM
01:45PM
01:57PM

−

E-LAKE STATION-AT
01:11PM
01:23PM
01:35PM
01:47PM
01:59PM

<------------- snip -------------->

Queries sent in the afternoon or shortly after midnight (I suspect to the end of the operational day) seem to be correct.

Generally, I would recommend the use of an abstract time format that does not include AM/PM or other formatting.

Other feeds that include time data use the following:

• TriMet web services: time in millis since midnight 1, January 1970 UTC (Basis in Java, used by TriMet's web service)
• weather.gov/xml: A 24h time format with UTC as reference, e.g.: 2004-04-27T25:00

(I am using 25h transit format as an example)

I'd prefer TriMet's format - it's easy to process in Java as Java time/date conversions take the timezone of the processor in consideration, including daylight savings time and the differences involving the handling of daylight savings time around the globe.

I've run into a strange problem on this web site: After deleting a post, it is no longer possible to post; error message:

"sorry, your note appears to have been empty! Please use your back button to return to the previous page and try again "

This regardless of web browser, i.e. it seems this is a back end, not a caching problem.