Add continuous/request stops

gtfs/spec/en/reference.md

@@ -211,6 +211,16 @@ File: **Required**
 |   |  | * **2** - Must phone agency to arrange drop off |  |
 |   |  | * **3** - Must coordinate with driver to arrange drop off |  |
 |   |  | The default value for this field is **0**. |  |
+| continuous\_pickup | Optional | The **continuous\_pickup** field can be used to indicate a section of a trip where it is possible to board the transit vehicle at any point along the vehicle’s path of travel. Some terms used to describe this service feature include "hail-and-ride" (UK), "request stops" (UK) or "flag stops" (USA). In order to describe this type of service, the trip must reference a route alignment (**shape_id**) in shapes.txt. After a **continuous\_pickup** type is specified that type applies for the length of the vehicle path through stop points until a different, non-empty **continuous\_pickup** value is specified in a subsequent stop\_times.txt record for the trip. **continuous\_pickup** applies only to pickup on an alignment, and does not override any pickup\_type values that are set for discrete stops. Valid values for the **continuous\_pickup** field are: |  |
+|   |  | * **Empty** - No change in continuous pickup type. If no continuous pickup type is set with the first stop\_times.txt record of a trip, then a type of **0** is assumed (see below). |  |
+|   |  | * **0** - No continuous pickup available.  |  |
+|   |  | * **2** - Must phone agency to arrange a request stop pickup along the alignment |  |
+|   |  | * **3** - The rider may indicate they wish to board by "flagging" the vehicle on the street, without prior notice |  |
+| continuous\_drop_off | Optional | The **continuous\_drop_off** field can be used to indicate a section of a trip where it is possible to alight from the transit vehicle at any point along the vehicle’s path of travel. Some terms used to describe this service feature include "hail-and-ride" (UK), "request stops" (UK) or "flag stops" (USA). In order to specify continuous drop-off, the trip must reference a route alignment (**shape_id**) in shapes.txt. After a **continuous\_drop_off** type is specified in a trip that type applies for the length of the vehicle path through subsequent stop\_times.txt records until a different, non-empty **continuous\_drop_off** value is specified in a subsequent stop\_times.txt record for the trip. **continuous\_drop\_off** applies only to drop-off on an alignment, and does not override any drop\_off\_type values that are set for discrete stops. Valid values for the **continuous\_drop_off** field are: |  |
+|   |  | * **Empty** - No change in continuous drop-off type. If no continuous drop-off type is set with the first stop\_times.txt record of a trip, then a type of **0** is assumed (see below). |  |
+|   |  | * **0** - No continuous drop-off available |  |
+|   |  | * **2** - Must phone agency to arrange a request-stop drop-off along the alignment |  |
+|   |  | * **3** - The rider may indicate they wish to alight by coordinating with the driver |  |
 |  shape_dist_traveled | Optional | When used in the [stop_times.txt](#stop_timestxt) file, the **shape_dist_traveled** field positions a stop as a distance from the first shape point. The **shape_dist_traveled** field represents a real distance traveled along the route in units such as feet or kilometers. For example, if a bus travels a distance of 5.25 kilometers from the start of the shape to the stop, the **shape_dist_traveled** for the stop ID would be entered as "5.25". This information allows the trip planner to determine how much of the shape to draw when showing part of a trip on the map. The values used for **shape_dist_traveled** must increase along with **stop_sequence**: they cannot be used to show reverse travel along a route.  The units used for **shape_dist_traveled** in the [stop_times.txt](#stop_timestxt) file must match the units that are used for this field in the shapes.txt file. |  |
 |  timepoint | Optional | The timepoint field can be used to indicate if the specified arrival and departure times for a stop are strictly adhered to by the transit vehicle or if they are instead approximate and/or interpolated times. The field allows a GTFS producer to provide interpolated stop times that potentially incorporate local knowledge, but still indicate if the times are approximate. For stop-time entries with specified arrival and departure times, valid values for this field are: |  |
 |   |  | * **empty** - Times are considered exact. |  |