Update for GTFS-ServiceChanges v3.1 - NOT FOR PRODUCTION USE

[barbeau]

Do not merge - work in progress

Based on the .proto from MobilityData/transit#47, which is subject to change.

NOT FOR PRODUCTION USE - FOR PROTOYPING ONLY

If you start using these bindings, please comment below!

Java

If you're using Maven to manage your dependencies in your project:

1. Clone this project and check out this branch (service-changes)
2. cd java - change to the Java subdirectory
3. mvn install - build the Java bindings and install them to your local Maven repo
4. Change your pom.xml to point to the following:

    <groupId>io.mobilitydata.transit</groupId>
    <artifactId>gtfs-realtime-bindings</artifactId>
    <version>0.0.6-SNAPSHOT</version>

If you're not using Maven to build your own project:

1. mvn package
2. Look in target directory - you should see a gtfs-realtime-bindings-0.0.6-SNAPSHOT.jar file there you can use as a library for your project

[barbeau]

I've added a field for StopTime to FeedEntity so stop times can be added to the feed. This was an oversight in the original draft .proto.

[barbeau]

I've moved StopTime to be a repeated entity within Trip - otherwise there was no way to tie StopTimes to a Trip. See MobilityData/transit#47 (comment).

[barbeau]

I just added the two new route_types from google/transit#174 to the bindings for service changes.

[barbeau]

I removed stop_id from stop_time_properties - NewStops should only be used in new Trips, not TripUpdates

[barbeau]

I've added Trip.start_date to specify the date when a new trip starts.

[barbeau]

I just pushed a fix for a field name: biked_allowed -> bikes_allowed

[barbeau]

I just pushed two change to the bindings - see:

• Allow repeated start_date for new Trips - MobilityData/transit@e30983f
• Trip.replaces_trip_id -> TripUpdate.replaced_by_trip_id - MobilityData/transit@9c5af29

[mpaine-act]

• Allow repeated start_date for new Trips - MobilityData/transit@e30983f

I have question about support for start_date. When the trip starts a few minutes before midnight but is still considered part of the current day in which it runs 99% of the trip. Should the start_date be null, the previous date or the current date? Also, should start_time be listed in either case?