diff --git a/add-one-pager-info/404.html b/add-one-pager-info/404.html new file mode 100644 index 00000000..2f401876 --- /dev/null +++ b/add-one-pager-info/404.html @@ -0,0 +1,849 @@ + + + +
+ + + + + + + + + + + + + + +Schemas for TIDES suite.
+TIDES consists of a package of files as defined in the following table.
+The following table is automatically generated from [tides.spec.json
]
name | +title | +description | +required | +
---|---|---|---|
vehicle-locations |
+Vehicle Locations | +Timestamped vehicle locations and speeds. | +False | +
passenger-events |
+Passenger Events | +Timestamped passenger-related events, including boardings and alightings. | +False | +
fare-transactions |
+Fare Transactions | +Timestamped fare transaction, associated with devices. | +False | +
stop-visits |
+Stop Visits | +Summarized boarding, alighting, arrival, departure, and other events (kneel engaged, ramp deployed, etc.) by trip and stop for each service date. | +False | +
trips-performed |
+Trips Performed | +Trips performed for each service date. | +False | +
station-activities |
+Station Activities | +Summarized transactions, entries, and exits by stop or station and time period for each service date (for events not associated with a trip). | +False | +
devices |
+Devices | +Measurement devices, such as AVL, APC, and AFC devices, associated with vehicles or stops or stations. | +False | +
train-cars |
+Train Cars | +Assets that comprise vehicles, such as train cars, with descriptive information. | +False | +
vehicle-train-cars |
+Vehicle Train Cars | +Relationships between assets and vehicles. | +False | +
vehicles |
+Vehicles | +Vehicles, including buses and train consists, with descriptive information. | +False | +
operators |
+Operators | +Personnel who operate vehicles. | +False | +
File components for TIDES are specified in [tides.spec.json
] in a format compatible with the
+frictionless data data package standard.
Files in the TIDES suite are related to each other and other open standards as follows:
+Relationship of trip_id_scheduled
to GTFS Schedule trip_id
trip_id_scheduled
in TIDES and trip_id
in GTFS Schedule should be consistent when a performed trip exists in the published GTFS Schedule.
If a trip does not exist in the published GTFS Schedule, trip_id_scheduled
values in TIDES do not have any assumed relationship with GTFS.
{"use strict";/*!
+ * escape-html
+ * Copyright(c) 2012-2013 TJ Holowaychuk
+ * Copyright(c) 2015 Andreas Lubbe
+ * Copyright(c) 2015 Tiancheng "Timothy" Gu
+ * MIT Licensed
+ */var Wa=/["'&<>]/;Vn.exports=Ua;function Ua(e){var t=""+e,r=Wa.exec(t);if(!r)return t;var o,n="",i=0,s=0;for(i=r.index;i