TrafficXRoads: Guide
page 23
The “sink name” is used as an ID in payloads for communication with
the controller. Therefore, it is necessary that the UDP sinks are unique
throughout all the analytics. FLOW does not check whether the sink
name is unique.
If you have a controller that has integrated and supports the UDP data communication
with FLOW, the publishing of data is very easy. In FLOW we define a traffic detection task
that we want using available operators and on the last operator we place the desired UDP
sink that we give a unique name. Inside the traffic controller we identify the sink based on
its name and we use it as an input signal for traffic control.
Continuing the Object presence example from the previous chapter, we would add UDP
ZONE sink with a unique name (in our case we did this systematically CAM[X]-ZONE[Y])
to each of the final ZONE operators in NOW mode. This way we have created 3 detectors
of presence in the image CAM1-ZONE1, CAM1-ZONE2 a CAM3-ZONE3, that communicate
the information about presence/ absence of vehicle to the traffic controller using UDP.
The list of the created UDP sinks can be found in the analytics and is available on the
Diagnostics
page. The status of the zone is communicated to the controller under the
names listed in the
Name
row in the table.
