Changes for page SIRI StopMonitoring

Last modified by admin admin on 2024/07/23 05:00
From version 2.1
edited by admin admin
on 2024/07/23 04:58
Change comment: There is no comment for this version
To version 1.1
edited by admin admin
on 2024/07/23 04:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,7 +10,7 @@
10 10  
11 11  with the following GET parameters:
12 12  
13 -* **key** - your MTA Bus Time developer API key (required). Go {{html}}<a href="https://register.developer.obanyc.com">here</a>{{/html}} to get one.
13 +* **key** - your MTA Bus Time developer API key (required). Go {{html}}<a href="https://spreadsheets.google.com/viewform?hl=en&formkey=dG9kcGIxRFpSS0NhQWM4UjA0V0VkNGc6MQ#gid=0">here</a>{{/html}} to get one.
14 14  
15 15  * **version** - which version of the SIRI API to use (1 or 2). Defaults to 1, but 2 is preferrable.
16 16  
... ... @@ -48,8 +48,8 @@
48 48  
49 49  Other notes about the particularities of ##StopMonitoring## data is shown after the example response.
50 50  
51 -
52 -##<!~-~- SIRI container elements ~-~->
51 +##
52 +<!~-~- SIRI container elements ~-~->
53 53  <Siri version="1.3" xmlns="http://www.siri.org.uk/siri">
54 54   <ServiceDelivery>
55 55  \\\\ <!~-~- The timestamp on the MTA Bus Time server at the time the request was fulfilled ~-~->
... ... @@ -70,7 +70,8 @@
70 70  \\\\ ... More MonitoredStopVisit elements
71 71  \\\\ </StopMonitoringDelivery>
72 72   </ServiceDelivery>
73 -</Siri>##
73 +</Siri>
74 +##
74 74  
75 75  
76 76  === StopMonitoring Updates to Use Block-Level Assignment ===
... ... @@ -77,7 +77,8 @@
77 77  
78 78  ##StopMonitoring## results will now include buses that are scheduled to stop at the monitored stop according to the schedule for their assigned blocks, even if they are not yet on the trip that will serve the monitored stop. This occurs only when those buses have a block-level assignment; otherwise, they are not included until they reach the terminal and present evidence that they will continue on to serve the monitored stop. In general, this means that ##StopMonitoring## requests will have more results. The diagram below shows an example of this behavior.
79 79  
80 -[[image:wraparound.png||data-xwiki-image-style-alignment="center"]]
81 +(% style="text-align:center" %)
82 +[[image:wraparound.png]]
81 81  
82 82  This is indicated by:
83 83