Skip to content

Commit c45031f

Browse files
committed
remove answered questions about trip attributes
1 parent 17c3cb2 commit c45031f

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

data-types.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -106,10 +106,6 @@ Events represent changes in vehicle status.
106106
| `journey_id` | UUID | Optional | Journey UUID | TODO "see `journey_id`" or something |
107107
| `associated_ticket` | String | Optional | Identifier for an associated ticket inside an Agency-maintained 311 or CRM system |
108108

109-
(?) Does anyone use `associated_ticket`?
110-
111-
(?) Does anyone use `publication_time`?
112-
113109
### Event Times
114110

115111
Because of the unreliability of device clocks, the Provider is unlikely to know with total confidence what time an event occurred at. However, Providers are responsible for constructing as accurate a timeline as possible. Most importantly, the order of the timestamps for a particular device's events must reflect the Provider's best understanding of the order in which those events occurred.

0 commit comments

Comments
 (0)