Parse/Convert Transit Data

We are looking for a short and simple program to convert bus schedules (in human readable text format) into a standardized CSV format. The input to the program will be three text files (1 describing bus schedules during weekdays, 1 describing schedules on saturdays, and 1 describing schedules on sunday). A set of example inputs ([login to view URL], etc) is attached. The program will output 4 files: (1) [login to view URL] - a file listing the stops served by the agency. (2) [login to view URL] - a file listing the routes run by the agency (3) [login to view URL] - a file listing each trip (e.g. run). (4) [login to view URL] - a file listing each individual stop-time (i.e. every time a bus stops at a particular stop). These four files should conform to the Google Transit Feed Specification (e.g. GTFS, see [login to view URL]), with the following caveats: (1) The program does not need to output [login to view URL], [login to view URL], or any of the other GTFS files. (2) The program should assume use 'WD', 'SAT', or 'SUN' for the service_id of trips starting on weekdays, Saturday, or Sunday, respectively. (3) The program should set stop_lat and stop_lon to 0 and 0, respectively, for each stop in stops.txt. (this information is not provided by the source input files). (4) When setting the direction_id field, use 0 for outbound/northbound/westbound, and 1 for inbound/southbound/eastbound. (5) When a stop shows up twice in a row in the input .txt file, you should assume that the first time is an 'arrival time' and the second time is a 'departure time'. I've also provided a set of output files corresponding to the desired output for the first two trips in HeadwaysOct2008Weekday.txt. You may choose to use any language in developing this program; however, we will give a slight preference to bidders who plan to use Java. Coders may feel free to use any open source (GPL, LGPL, GNU, Apache, etc.) software libraries in their implementation. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. ## Platform Linux