Fix broken ScheduleRelationship links on Reference.md (#161)

* Update reference.md Fix broken links to ScheduleRelationship (under TripDescriptor) in Index. * Update reference.md Fixed additional link in TripDescriptor section
MobilityData · Jul 17, 2023 · 8a23981 · 8a23981
1 parent 2c866a3
commit 8a23981
Showing 1 changed file with 6 additions and 6 deletions.
diff --git a/docs/realtime/reference.md b/docs/realtime/reference.md
@@ -50,7 +50,7 @@ Fields labeled as **experimental** are subject to change and not yet formally ad
     *   [FeedEntity](#message-feedentity)
         *   [TripUpdate](#message-tripupdate)
             *   [TripDescriptor](#message-tripdescriptor)
-                *   [ScheduleRelationship](#enum-schedulerelationship-1)
+                *   [ScheduleRelationship](#enum-schedulerelationship_1)
             *   [VehicleDescriptor](#message-vehicledescriptor)
                 *   [WheelchairAccessible](#enum-wheelchairaccessible)
             *   [StopTimeUpdate](#message-stoptimeupdate)
@@ -60,7 +60,7 @@ Fields labeled as **experimental** are subject to change and not yet formally ad
             *   [TripProperties](#message-tripproperties)
         *   [VehiclePosition](#message-vehicleposition)
             *   [TripDescriptor](#message-tripdescriptor)
-                *   [ScheduleRelationship](#enum-schedulerelationship-1)
+                *   [ScheduleRelationship](#enum-schedulerelationship_1)
             *   [VehicleDescriptor](#message-vehicledescriptor)
                 *   [WheelchairAccessible](#enum-wheelchairaccessible)
             *   [Position](#message-position)
@@ -72,7 +72,7 @@ Fields labeled as **experimental** are subject to change and not yet formally ad
             *   [TimeRange](#message-timerange)
             *   [EntitySelector](#message-entityselector)
                 *   [TripDescriptor](#message-tripdescriptor)
-                    *   [ScheduleRelationship](#enum-schedulerelationship-1)
+                    *   [ScheduleRelationship](#enum-schedulerelationship_1)
             *   [Cause](#enum-cause)
             *   [Effect](#enum-effect)
             *   [TranslatedString](#message-translatedstring)
@@ -450,14 +450,14 @@ TripDescriptor.route_id cannot be used within an Alert EntitySelector to specify
 
 **Fields**
 
-| _**Field Name**_ | _**Type**_ | _**Required**_ | _**Cardinality**_ | _**Description**_ |
-|------------------|------------|----------------|-------------------|-------------------|
+| _**Field Name**_ | _**Type**_                                                                 | _**Required**_ | _**Cardinality**_ | _**Description**_ |
+|------------------|----------------------------------------------------------------------------|----------------|-------------------|-------------------|
 | **trip_id** | [string](https://developers.google.com/protocol-buffers/docs/proto#scalar) | Conditionally required | One | The trip_id from the GTFS feed that this selector refers to. For non frequency-based trips (trips not defined in GTFS frequencies.txt), this field is enough to uniquely identify the trip. For frequency-based trips defined in GTFS frequencies.txt, trip_id, start_time, and start_date are all required. For scheduled-based trips (trips not defined in GTFS frequencies.txt), trip_id can only be omitted if the trip can be uniquely identified by a combination of route_id, direction_id, start_time, and start_date, and all those fields are provided. When schedule_relationship is DUPLICATED within a TripUpdate, the trip_id identifies the trip from static GTFS to be duplicated. When schedule_relationship is DUPLICATED within a VehiclePosition, the trip_id identifies the new duplicate trip and must contain the value for the corresponding TripUpdate.TripProperties.trip_id. |
 | **route_id** | [string](https://developers.google.com/protocol-buffers/docs/proto#scalar) | Conditionally required | One | The route_id from the GTFS that this selector refers to. If trip_id is omitted, route_id, direction_id, start_time, and schedule_relationship=SCHEDULED must all be set to identify a trip instance. TripDescriptor.route_id should not be used within an Alert EntitySelector to specify a route-wide alert that affects all trips for a route - use EntitySelector.route_id instead. |
 | **direction_id** | [uint32](https://developers.google.com/protocol-buffers/docs/proto#scalar) | Conditionally required | One | The direction_id from the GTFS feed trips.txt file, indicating the direction of travel for trips this selector refers to. If trip_id is omitted, direction_id must be provided. <br><br>**Caution:** this field is still **experimental**, and subject to change. It may be formally adopted in the future.<br>|
 | **start_time** | [string](https://developers.google.com/protocol-buffers/docs/proto#scalar) | Conditionally required | One | The initially scheduled start time of this trip instance. When the trip_id corresponds to a non-frequency-based trip, this field should either be omitted or be equal to the value in the GTFS feed. When the trip_id correponds to a frequency-based trip defined in GTFS frequencies.txt, start_time is required and must be specified for trip updates and vehicle positions. If the trip corresponds to exact_times=1 GTFS record, then start_time must be some multiple (including zero) of headway_secs later than frequencies.txt start_time for the corresponding time period. If the trip corresponds to exact_times=0, then its start_time may be arbitrary, and is initially expected to be the first departure of the trip. Once established, the start_time of this frequency-based exact_times=0 trip should be considered immutable, even if the first departure time changes -- that time change may instead be reflected in a StopTimeUpdate. If trip_id is omitted, start_time must be provided. Format and semantics of the field is same as that of GTFS/frequencies.txt/start_time, e.g., 11:15:35 or 25:15:35. |
 | **start_date** | [string](https://developers.google.com/protocol-buffers/docs/proto#scalar) | Conditionally required | One | The start date of this trip instance in YYYYMMDD format. For scheduled trips (trips not defined in GTFS frequencies.txt), this field must be provided to disambiguate trips that are so late as to collide with a scheduled trip on a next day. For example, for a train that departs 8:00 and 20:00 every day, and is 12 hours late, there would be two distinct trips on the same time. This field can be provided but is not mandatory for schedules in which such collisions are impossible - for example, a service running on hourly schedule where a vehicle that is one hour late is not considered to be related to schedule anymore. This field is required for frequency-based trips defined in GTFS frequencies.txt. If trip_id is omitted, start_date must be provided. |
-| **schedule_relationship** | [ScheduleRelationship](#enum-schedulerelationship-1) | Optional | One | The relation between this trip and the static schedule. If TripDescriptor is provided in an Alert `EntitySelector`, the `schedule_relationship` field is ignored by consumers when identifying the matching trip instance.
+| **schedule_relationship** | [ScheduleRelationship](#enum-schedulerelationship_1)                       | Optional | One | The relation between this trip and the static schedule. If TripDescriptor is provided in an Alert `EntitySelector`, the `schedule_relationship` field is ignored by consumers when identifying the matching trip instance.
 
 ## _enum_ ScheduleRelationship