Proposal: Support multi-car crowding in GTFS-RT

82 views
Skip to first unread message

Loic Fontolliet

unread,
Jul 27, 2020, 6:33:07 PM7/27/20
to GTFS-realtime
Hello,

I just opened a new proposal to support multi-car crowding in GTFS-RT.
Feel free to review and comment!

Thanks,
Loïc

Loic Fontolliet

unread,
Aug 31, 2020, 11:46:42 AM8/31/20
to GTFS-realtime
Hello,

This pull request has been open for several weeks, so per the Official Process I'm calling for a vote.
Vote will be closed on Monday the 7th of September at 23:59:59 UTC.

You can vote via +1 or -1 comment on the GitHub pull request.

Thanks,
Loïc

Loic Fontolliet

unread,
Sep 7, 2020, 9:05:55 PM9/7/20
to GTFS-realtime
Hello everyone,

The vote is now closed. Here is the tally.

Yes (+1)

No (-1)

Result: 83.3% Yes

We need at least 80% yes for experimental GTFS-RT features per the official processso this proposal passes.

Note: I will modify the comment describing the `carriage_sequence` field as suggested by @juanborre and @barbeau in this GitHub comment, unless someone wants to change their vote if this change in the comment is made.

Thanks to everyone who contributed to this proposal.

Loïc


Harsh Verma

unread,
Sep 28, 2020, 6:23:59 PM9/28/20
to gtfs-r...@googlegroups.com

We need to consider and handle the case -

For car ordering or car position, it will be done regardless of the direction of travel -

For many trains and train operators, generally, the train Consists always remains the same, and stay in the same order, with the car adjacent to the locomotive always being termed as Car # 1 and the next car as # 2, then Car # 3 and so on.

So, the reporting of Car # 1 may need to remain the same, particularly with the AMTRAK Capitol Corridor CCJPA. In some other transit systems, it may not be the same.

Even though the train may be going in either direction, the locomotive is many times always on one side and would be either pulling or pushing (behind the cars) the train coaches.

Car 1 is always adjacent to the locomotive, regardless of the direction of travel.


Thanks,

Harsh Verma



--
You received this message because you are subscribed to the Google Groups "GTFS-realtime" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gtfs-realtim...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gtfs-realtime/fcf705d8-1403-47db-8ba1-dc5c3bf69cfbn%40googlegroups.com.

Harsh Verma

unread,
Sep 29, 2020, 1:20:42 AM9/29/20
to gtfs-r...@googlegroups.com, harshve...@gmail.com
Hope to see some comments and develop an approach for this...


For multi-car occupancy, “order of Car numbering may not be flipped every time the train direction of travel is changed”.

Carriage Sequence is always going to be 1, 2, 3, 4, 5

The first occurrence of the repeated field will represent the first car or vehicle, given the direction of travel is not always true generally with rail operations and passenger rail industry, specially in the case of AMTRAK Capitol Corridor and this needs to be accounted for, to have an operator view of the same.

There needs to be a special case for this consideration.

 Thanks,

Harsh Verma


Reply all
Reply to author
Forward
0 new messages