| Version 4 (modified by jdalbey, 6 years ago) (diff) |
|---|
CPTMS Camera Controller
Specification
See the User Interface Prototype in the Subversion repository: trunk/webapps/cptms/CameraDisplay.html
Purpose:
Display four camera views of current CPTMS highway conditions in a grid layout.
Functions;
- The user selects which of the four displays is to be updated.
- The user selects which route (highway) is to be displayed. The list of routes is 1 5 22 55 57 73 74 91 133 142 241 261 405 605.
Once a route is selected, the camera drop down box filters the camera choices to just those on the selected route. - The users selects a camera. The chosen camera view appears in the selected display.
Data Sources
- cptms/data_layers/cctv_locations_D12.gson is a static file containing the filename and locationName (among other things) for all the CCTV cameras.
- webapps/dynamicdata/highway_status.json is updated every 30 seconds with traffic flow. The camera display controller reads this file every 30 seconds and obtains the "color" property for each camera currently being displayed. It then chooses the corresponding image to display from the cptms/images folder. lime = freeflow, yellow = slow, red = stopped.
The complicated part is that the highway status data doesn't include where the CCTV cameras are. Luckily CPTMS already has the algorithm for determining where the nearest CCTV camera is for a given VDS. This could be used as is (do an exhaustive search), or write the converse algorithm that given a CCTV will find the traffic flow at the nearest VDS.
Attachments
-
CameraDisplayPrototype1.png
(610.3 KB) -
added by jdalbey 6 years ago.
Screenshot of UI prototype
-
CameraDisplayPrototype2.png
(611.1 KB) -
added by jdalbey 6 years ago.
-
CameraDisplayPrototype3.png
(844.0 KB) -
added by jdalbey 6 years ago.
-
CameraDisplay.html
(2.7 KB) -
added by jdalbey 6 years ago.
UI Prototype
-
highway_status.json
(313.0 KB) -
added by tanmay 6 years ago.
-
cctv_locations_D12.gjson
(53.4 KB) -
added by tanmay 6 years ago.

