Fwd: feed_info.txt date format specification

[Brian Ferris]

Someone just pointed out what looks like a bug in the GTFS spec.  For feed_info.txt feed_start_date and feed_end_date, the spec states:

"Both days are given as dates in YYYYDDMM format as for calendar.txt"

Notice the day-before-month format.  But in fact, the date format used in calendar.txt and elsewhere is YYYYMMDD.  I think this is just a typo, as I've always parsed these dates in feed_info.txt as YYYYMMDD.  If no one objects, I'm going to update the spec to reflect this.

Brian

---------- Forwarded message ----------
From: <pelletie...@gmail.com>
Date: Wed, Apr 17, 2013 at 9:03 PM
Subject: feed_info.txt date format specification
To: googletran...@googlegroups.com


I noticed something stranfe in the GTF Specs page. Under feed_info.txt the date format for fields "feed_start_date" and "feed_end_date" is:

Both days are given as dates in YYYYDDMM format as for calendar.txt

The wording (perhaps not 100% English) seems to indicate that dates are to be in the same format as calendar.txt. However, the description in calendar.txt is:

The start_date field's value should be in YYYYMMDD format.

The end_date field's value should be in YYYYMMDD format.

So, which is it? YYYYMMDD or YYYYDDMM?

Thanks. 

--
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.
 
 

[Brian Ferris]

Ok, hearing no objections, I've fixed the typo in the spec documentation:

https://developers.google.com/transit/gtfs/reference#feed_info_fields