Skip to content

Commit

Permalink
Merge pull request #359 from HSLdevcom/feat/assigned-stop-id
Browse files Browse the repository at this point in the history
Add assigned-stop-id
  • Loading branch information
thjarvin authored Mar 8, 2024
2 parents a054858 + 279055c commit 03b5efc
Show file tree
Hide file tree
Showing 3 changed files with 1,180 additions and 86 deletions.
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
<modelVersion>4.0.0</modelVersion>
<groupId>fi.hsl</groupId>
<artifactId>transitdata-common</artifactId>
<version>1.5.6-RC</version>
<version>1.6.0-RC</version>
<packaging>jar</packaging>
<name>Common utilities for Transitdata projects</name>
<properties>
Expand Down
31 changes: 31 additions & 0 deletions protos/gtfs-realtime.proto
Original file line number Diff line number Diff line change
Expand Up @@ -182,6 +182,35 @@ message TripUpdate {
extensions 1000 to 1999;
}

// Realtime update for certain properties defined within GTFS stop_times.txt.
// Caution: this message is still experimental, and subject to change. It
// may be formally adopted in the future.
message StopTimeProperties {
// Supports real-time stop assignments. Refers to a stop_id defined in the
// GTFS stops.txt.
//
// The new assigned_stop_id should not result in a significantly different
// trip experience for the end user than the stop_id defined in GTFS
// stop_times.txt. In other words, the end user should not view this new
// stop_id as an "unusual change" if the new stop was presented within an
// app without any additional context. For example, this field is intended
// to be used for platform assignments by using a stop_id that belongs to
// the same station as the stop originally defined in GTFS stop_times.txt.
//
// To assign a stop without providing any real-time arrival or departure
// predictions, populate this field and set
// StopTimeUpdate.schedule_relationship = NO_DATA.
//
// If this field is populated, StopTimeUpdate.stop_sequence must be
// populated and StopTimeUpdate.stop_id should not be populated. Stop
// assignments should be reflected in other GTFS-realtime fields as well
// (e.g., VehiclePosition.stop_id).
//
// Caution: this field is still experimental, and subject to change. It
// may be formally adopted in the future.
optional string assigned_stop_id = 1;
}

// Realtime update for arrival and/or departure events for a given stop on a
// trip. Updates can be supplied for both past and future events.
// The producer is allowed, although not required, to drop past events.
Expand Down Expand Up @@ -221,6 +250,8 @@ message TripUpdate {
optional ScheduleRelationship schedule_relationship = 5
[default = SCHEDULED];

optional StopTimeProperties stop_time_properties = 6;

// The extensions namespace allows 3rd-party developers to extend the
// GTFS Realtime Specification in order to add and evaluate new features
// and modifications to the spec.
Expand Down
Loading

0 comments on commit 03b5efc

Please sign in to comment.