Transitfeed

Original release on 2011-10-27:
- Issue 305: Change "Too Many Consecutive !StopTimes with same departure/arrival time" from ERROR to WARNING

Original release on 2011-10-21:
- Issue 296: Feed Validator should send a warning when there are multiple consecutive 0:00:00 stop_times
- Issue 300: frequencies.txt - exact_times is now an officially adopted proposal
- Issue 301: agency.txt - agency_fare_url is now officially part of the GTFS spec
- Issue 302: Add Eclipse project files to svn:ignore
- Issue 303: The feed_info.txt proposal has been officially adopted

Original release on 011-05-06:
- New features
- Adding possibility to warn about "deprecated column names" (r1423, other related commits: r1463, r1521)
- Adding the first FeedValidator extension: this “googletransit” extension adds and alters validations of feeds to be used by Google Transit (r1452, see also FeedValidatorExtensions)
- extension of transitfeed.FareAttribute
- validation of new file feedinfo.txt
- extension of transitfeed.Schedule
- extension of transitfeed.Frequency (r1455)
- extension of transitfeed.Route and transitfeed.Stop (r1509)
- extension of transitfeed.Agency (includes the BCP-47 language code validation) (r1521, other related commits: r1524)
- adding feedvalidator_googletransit.py for using the googletransit extension without having to add the -extension flag (r1498)
- General validation changes
- Removed date dependency from two tests (r1393)
- Allowing trip_id to contain a hash '' (r1399)
- Avoiding duplicate errors from schedule.Validate due to validate_children=true (r1408)
- Fix handling of empty string stop_lat and stop_lon values in stops.txt ( issue 258 , r1419)
- Harmonizing and extending date validation in ServicePeriod. Dates must be between 1900 and 2100 (r1424)
- transitfeed API changes
- Changes to the extensibility mechanism to make creating and testing of extensions easier (r1409 and r1438)
- Code formatting changes: cleaned code and removed trailing whitespaces (r1420)
- Code refactoring: harmonized the Expect... and Expect...InClosure functions in the ValidationTestCase (r1421)
- Making the error level configurable on all problem types (r1439)
- Making feedvalidator.py extensible (r1498)
- Other changes
- Making transitfeed nosetests run on Windows 7 (r1458)
- Adding a line to the output (both Console and HTML) saying which extension, if any, was used to validate the feed (r1497)

Original release on 2010-08-05:
- New features
- Introduction of an extensibility mechanism so validation can be altered without directly changing the base transitfeed code (r1296. Other related commits: r1319)
- Validation changes
- Transfers are now ID'd by the pair (from_stop_id, to_stop_id). While not prohibited by GTFS duplicate IDs are still allowed, but a warning is issued (r1268)
- Warning when two trips in the same block have overlapping stop time intervals, and when both trips run on the same date. (Change by Brian Ferris - issue 230, r1297)
- Removed error when transfers = 0 and transfer_duration > 0, as it is allowed by GTFS (issue 232, r1298)
- Added a warning when there are no exceptions defined in calendar_dates.txt (r1306)
- Added detection of large transfers. Issues a warning if the stops are >2km appart, and an error if they are >10km appart. Also issues a warning if min_transfer_time + 120s is not enough to cover the distance when walking at 2m/s (very fast walking). (issue 234, r1307)
- util.FloatStringToFloat and util.NonNegIntStringToInt are now more flexible, issuing a warning when the number formats are not recognized but can be parsed by Python. As this is implementation dependent, it should be moved to an error as soon as possible. (r1350)
- transitfeed API changes
- Introduction of an object factory (r1281)
- Introduction of the HeadwayPeriod (later renamed to Frequency) and GtfsFactory classes (r1281)
- Trip._FIELD_NAMES_HEADWAY was removed. Frequency._FIELD_NAMES should be used instead. (r1296)
- Invalid values in routes.txt's route_color and route_text_color are now replaced by the respective default values (r1281)
- Schedule.AddAgencyObject() no longer calls Validate() by default on the Agency object being added (r1281)
- Schedule.AddTripObject() no longer calls Validate() by default on the Trip object being added (r1281)
- Schedule.AddRouteObject() no longer calls Validate() on the Route object being added (r1281)
- Instanciation of GTFS classes should not be done directly, but through GtfsFactory instead (r1281)
- Introduction of a ShapePoint class (r1289)
- Separation between problem reporting (what warnings and errors exist) and accumulation (how to handle them). (r1319)
- Renamed a couple of classes to more closely mirror their respective GTFS names. Fare was renamed FareAttribute and HeadwayPeriod was renamed Frequency. GenericGTFSObject was also renamed to GtfsObjectBase. (r1324)
- Other changes
- FeedValidator on Windows now deletes database file successfully (issue 206, r1257)
- Introduction of a GenericGTFSObject (later renamed GtfsObjectBase) from which all GTFS classes should inherit (r1258)
- Moved each GTFS class to its own file and removed the big transitfeed/_transitfeed.py. The API was not changed. (issue 196, r1275)
- Fixed google_random_queries.py usage info, added URL to usage of several tools (r1280)
- Added single date selection to Schedule Viewer (issue 17, r1300)
- Unit tests now pass in Python 2.6 (issue 237, r1323)
- All classes, except StopTime for performance reasons, go through the GtfsFactory instead of directly instantiating classes. (r1321)

Original release on 2009-12-15:
- Fixing the Windows binary distribution, which by mistake did not include the pytz package for timezone validation.

Original release on 2009-12-11:
- Moved transitfeed.py to transitfeed/_transitfeed.py to package it properly with transitfeed/util.py and transitfeed/shapelib.py; provided transitfeed/__init__.py to make the contents of transitfeed available under the same names as before.
- Validation changes
- Warn when there are several consecutive days without service in the feed validation (issue 188)
- Warn when the successive stop-times have the same value of shape_dist_traveled and Error when they are decreasing (issue 125, issue 203)
- The W3C formula for luminance comparison of line colors is used (partial fix for issue 108)
- Warn when an input file has more than one column with the same name (issue 87)
- Warn when start date or end date are set, but are not valid dates (issue 41)
- For problem types that can be sorted by severity keep the N most severe instead of the first N found. These include !StopTooFarFromParentStation, !StopsTooClose, !StationsTooClose, !DifferentStationTooClose, !StopTooFarFromShapeWithDistTraveled, and !TooFastTravel. (issue 184)
- transitfeed API changes
- Schedule.Validate() is now not run by Loader.Load() by default. To call it implicitly set extra_validation to True, or call it explicitly indicating the service_gap_interval.
- For performance reasons !ServicePeriod.!IsActiveOn now takes both a date string and, optionally, a date object representing the same date as the string.
- Other changes
- All tools now have a crash handler. The crash dump file is now called transitfeedcrash.txt
- --help available in all tools
- Make bottom panel in schedule viewer fixed height to partially address issue 45
- Changes to make all tests pass in python 2.4