Further clarify SKIPPED behavior in Trip Updates docs

google · Feb 20, 2019 · 34b21b9 · 34b21b9
1 parent 9efe24e
commit 34b21b9
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/gtfs-realtime/spec/en/trip-updates.md b/gtfs-realtime/spec/en/trip-updates.md
@@ -23,7 +23,7 @@ For each [StopTimeUpdate](reference.md#StopTimeUpdate), the default schedule rel
 
 **Updates should be sorted by stop_sequence** (or stop_ids in the order they occur in the trip).
 
-If one or more stops are missing along the trip the update is propagated to all subsequent stops. This means that updating a stop time for a certain stop will change all subsequent stops in the absence of any other information.
+If one or more stops are missing along the trip the delay from the update is propagated to all subsequent stops. This means that updating a stop time for a certain stop will change all subsequent stops in the absence of any other information. Note that updates with a schedule relationship of `SKIPPED` will not stop delay propagation, but updates with schedule relationships of `SCHEDULED` (also the default value if schedule relationship is not provided) or `NO_DATA` will.
 
 **Example 1**