Be Counted!
Be Counted!
Be Counted!
| Getting Started | Start counting! | /pages/QWgNg5OYFiWT7xs6h4Ql | |
| Help & FAQ | Find answers to common issues In addition to discussions, issues, and chat. | ||
| Contribute | Contribute back to the open source project |
| Getting Started | Start counting! | /pages/QWgNg5OYFiWT7xs6h4Ql | |
| Help & FAQ | Find answers to common issues In addition to discussions, issues, and chat. | ||
| Contribute | Contribute back to the open source project |
| Build It! | See our Build your own device (DIY) guide. The software is open source and components are available retail. | Customize to your heart's content. | /files/ZKm0OlesF6jVCQmt9QBP | /pages/bCpWjdihegZYApPZoFDC |
| Buy It! | (coming soon) | Purchase a pre-built traffic monitor or kit from the Roadway Biome Project. | /files/bpG8fGPldxUEFeVcaf1x |
LED Display showing daily counts capture with the traffic monitor
Full set of Traffic Monitor components ready for assembly
Carefully attach the AQ ribbon cable with notch towards outside of RPi5
Traffic monitors ready to count
Back with VESA mount holes, 1/4"-20 mm screw insert, strap slots, and safety tether hole (lower-left)
Bottom of the standard enclosure with arca-swiss quick release plate and 1/4"-20 mm screw insert
Traffic Monitor on a 16-foot telescoping tripod to count event participants
Researcher recording manual confirmation counts with a Traffic Monitor on a camera tripod plugged into a portable power station
Long-term deployments with permission on private rooftops and gate entrances.
Quiet road, monitoring downhill movement
Busy business district, nearly straight-on object movement on wide road
Busy business district, side-on monitoring focused on pedestrian and bike crosswalk
Neighborhood Greenway, an ideal spot to monitor roadway utilization for bikes, pedestrians, and cars
Neighborhood Greenway mounting spot, South-facing
Neighborhood Greenway mounting spot, North-facing
Detection events may occur anywhere in the camera field-of-view (FOV)
Properly configured Frigate Zones
Frigate > Settings > Debug to see how your object detection settings are working
########
# This file contains node-red environment variables loaded by node-red.service
# Read more at https://nodered.org/docs/user-guide/environment-variables
# and https://fedoraproject.org/wiki/Packaging:Systemd
# Uses:
# - variables can be used in settings.js by calling `process.env.ENV_VAR`
# - node property can be set by calling `${ENV_VAR}
#
########
# traffic monitor open source software release version
TM_VERSION='0.5.0'
# used in settings.js for credentialSecret
NODE_RED_CREDENTIAL_SECRET='myNodeRED1234'
# database locations, relative to user directory defined in settings.js
# will be relative path to store SQLite databases
TM_DATABASE_PATH_TMDB='/db/tmdb.sqlite'
# mqtt broker for incoming Frigate events
# Settings below set up the aedes broker node
TM_MQTT_BROKER_HOST='localhost'
TM_MQTT_BROKER_PORT='1883'
# mqtt user, leave blank for no authentication
TM_MQTT_BROKER_USERNAME=''
# mqtt password, leave blank for no authentication
TM_MQTT_BROKER_PASSWORD=''
# defines system USB serial port for radar
# run `ls -lat /sys/class/tty/ttyACM*` to list devices
TM_RADAR_SERIAL_PORT_00='/dev/ttyACM0'
TM_RADAR_SERIAL_PORT_01='/dev/ttyACM1'
TM_RADAR_SERIAL_PORT_02='/dev/ttyACM2'
TM_RADAR_SERIAL_PORT_03='/dev/ttyACM3'
Monitoring tab sample
Frigate zones configured with 12 zones drawn on a busy 5-way intersection
Example of manual, hand-written confirmation counts through various intersections (left image matches above zones)
| Table Name | Description | PII Included |
|---|---|---|
| deployment | History of location details for device and sensors: includes latitude, longitude, bearing. | No |
| events | Object Detection confirmed events. Generated by Frigate with required information attached. | Potential (if included in Frigate sub-label or attribute) |
| radar_dov | DetectedObjectVelocity (DOV) readings from Radar API, ON command | No |
| radar_timed_speed_counts | TimedSpeedCounts readings from Radar API @O command with `@ | No |
| radar_raw_speed_magnitude | Show speeds and magnitudes in descending order by magnitude. OS and OM commands with O3 | No |
| radar_raw_speed_magnitude_single | Same as above, but only the first speed and magnitude value, for easier analysis. OS and OM commands with O1 | No |
| radar_oc_payload | Object detection capability, including vehicle length. OC command, with OPS9243 firmware | No |
| comments | Operator-entered time stamped entries for Traffic Monitor status, deployment, location, conditions, construction, etc. Used for downstream analysis. | Potential (operator-entered free-text) |
| Attribute | Description | SQLite data type | Valid values |
|---|---|---|---|
| id | UUID for object detection. Will be generated by `source` Frigate-generated from MQTT event `end`. Radar-generated from flow. | TEXT, PRIMARY KEY | Frigate: Unix timestamp in seconds concatenated to a hyphen and randomly-generated 6-alphanumeric value; e.g. "1721144705.617111-fg3luy" Radar: Unix timestamp in seconds concatenated to a hyphen and randomly-generated 8-alphanumeric value concatenated with a hypen r '-r'; e.g. "1721144705.617111-fg3luy4x-r" |
| camera | Name of camera for object detection (defined in Frigate config). Frigate-generated from MQTT event `end`. | TEXT | Free-text |
| label | Object label assigned by Frigate. Frigate-generated from MQTT event `end`. | TEXT | Assigned by model, based on Frigate available objects |
| sub_label | Additional informatoin assigned to Frigate event. Frigate-generated from MQTT event `end`. | TEXT | Assigned via Frigate HTTP API |
| top_score | Model inference score for object label. This is the highest score as object moved through field of view. Frigate-generated from MQTT event `end`. | REAL | 0-1 value |
| frame_time | Unix timestamp in seconds for when the object was optimally identified by Frigate for the field of view. Frigate-generated from MQTT event `end`. | REAL | Unix timestamp in Seconds |
| start_time | Unix timestamp in seconds for when the object first entered the field of view. Frigate-generated from MQTT event `end`. | REAL | Unix timestamp in Seconds |
| end_time | Unix timestamp in seconds for when the object exited the field of view. Frigate-generated from MQTT event `end`. | REAL | Unix timestamp in Seconds |
| entered_zones | JSON array list of zones in order the object entered each zone. Specified zones are used for various calculations. Frigate-generated from MQTT event `end`. | TEXT | Free-text via Frigate; expected: - "zone_capture" - region for counting objects - "zone_radar" - radar detection field of view (FOV) - "zone_near" - area closest to radar, for determining visual direction - "zone_far" - area furthest from radar, for determining visual direction |
| score | Model inference score for the object to initiate tracking. Computed score as object moves through field of view. Frigate-generated from MQTT event `end`. | REAL | 0-1 value |
| area | Width*height of the bounding box for the detected object Frigate-generated from MQTT event `end`. | REAL | 0-24000000 |
| ratio | Width/height of the bounding box for the detected object; e.g. 0.5 is tall (twice as high as wide box) Frigate-generated from MQTT event `end`. | REAL | 0-24000000 |
| motionless_count | Number of frames the object has been motionless Frigate-generated from MQTT event `end`. | REAL | Integer count; e.g. 0 |
| position_changes | Number of times the object has changed position Frigate-generated from MQTT event `end`. | REAL | Integer count; e.g. 2 |
| attributes | Attributes with top score that have been identified on the object at any point Frigate-generated from MQTT event `end`. | TEXT, JSON | JSON object with key:value pairs; e.g. {"face": 0.86} |
| direction_calc | Assigned object moving direction relative to device placement; i.e. "outbound" is moving away from device. | TEXT | "outbound" or "inbound" |
| speed_calc | Assigned speed/velocity calculated for entire time object was in the camera's field of view. | REAL | Positive, Negative corresponding to inbound and outbound direction, respectively |
| provenance | Source(s) of event detection. List any sensor on the device that captured or created this event. The first item in the array is considered the primary source. | TEXT, JSON | JSON Array with every sensor that confirms the same event. e.g. Camera sensor: frigate, Radar sensor: radar |
| radarName | Radar sensor name that is associated (via config) with the camera during the event, regardless if event was confirmed by radar (see provenance). | TEXT | Free-text, defined from configs |
| deployment_id | Each ID represents a unique deployment configuration and/or location for the device. This acts a foreign key link to the `deployment` table, `id` column. | TEXT, FOREIGN KEY | `deployment`.`id` foreign key, may be null |
Maximum speed/velocity calculated for all measurements object was detected in the radar zone.
`DetectedObjectVelocity` from API
Roadway with many regions being sent to be checked for object detection because of motion and shadows.
Example of a potential near-miss scenario zone tracking set up. Zones everywhere!