LogoLogo
English
English
  • General
    • About this documentation
    • What's new
      • 2025.1
        • 2025.1 U3
        • 2025.1 U2
        • 2025.1 U1
      • 2024.5
        • 2024.5 U1
      • 2024.4
      • 2024.3
  • Products
    • BERNARD Mobility Analyser (BMA)
      • Scope of delivery
      • Data sheet
      • Mounting
    • Mobile BERNARD Mobility Analyser (BMA)
      • Scope of delivery
      • Data sheet
      • Installation
      • Charge battery box
    • BERNARD Character Analyser (BCA)
      • Scope of delivery
      • Datasheet
      • Installation
        • Alignment of the BCA
    • BERNARD Mobility Controller (BMC)
      • Data sheet V2.2
      • Operating instructions V2.2
    • B101 & B401
      • Scope of delivery
      • Data sheet
      • Installation
  • Solution areas
    • Traffic survey
      • Traffic counting
      • Turning movement counting
      • Traffic Flow
    • Adaptive traffic control
    • Parking
      • Barrier-free parking
      • Single space parking
  • Control Center
    • Devices
      • Configuration
        • Object classes
      • Device health
      • Schedule
      • Device monitoring
    • Administration
      • Monitoring alerts
      • License management
      • Device update
      • User management
    • Control center API
      • Data analytics API
  • Data Center
    • Counting
      • Configuration of the survey
      • Data analysis
    • Traffic Flow
      • Configuration of a Traffic Flow survey
      • Data analysis
    • Data Center API
  • Bernard Technologies GmbH
    • Support Center
    • Terms and Conditions
Powered by GitBook
On this page
  • What data can be generated?
  • What needs to be considered for a successful analysis?
  • Specifications for the environment
  • Hardware specifications
Export as PDF
  1. Solution areas
  2. Traffic survey

Traffic counting

Use cases for traffic scenarios

PreviousTraffic surveyNextTurning movement counting

Last updated 9 months ago

How to successfully perform traffic counts on specific urban roads and highways, including the classification of objects according to our (sub)classes. You want to know the traffic situation of an urban road or highway? Our software is the solution to record the number of all objects, broken down by object type (class) and direction.

What data can be generated?

For this use case, our software provides you with all the information you need for traffic counting. The counts of the vehicles including their classification can be recorded. The counts are divided into two directions (in/out). Furthermore, several counts can be carried out in one camera, e.g. the separate counting of each lane. In addition, it is possible to add a second counting line, calibrate the distance between them and estimate the speed of vehicles passing both lines. are recognized by our software.

What needs to be considered for a successful analysis?

Camera setup

In the table below you will find detailed information on the requirements, settings and positioning of the camera.

Setting
Recommended

Pixels Per Meter is a unit of measurement used to define the amount of potential image detail a camera provides at a given distance.

>30 PPM (object classes car, truck)

<60 PPM (object classes person, bicycle, motorbike)

Video resolution

1280 × 720 Pixel

Video protocol/codec

RTSP/H264

Focal length

2.8 mm - 12 mm

Camera mounting - distance to object center

Object classes car, truck:

5-30 m (2.8 mm Focal length)

35-100 m (12 mm Focal length)

Object classes person, bicycle, scooter:

3-12 m (2.8 mm Focal length)

25-50 m (12 mm Focal length)

Camera mounting - mounting height

Up to 10 m

Note: Mounting higher can help to minimize obstruction by large objects.

Camera mounting - vertical angle to the object

<50 °

Note: The correct vertical angle to the object should be achieved by setting the correct distance to the vehicle and the optimum mounting height.

0 ° - 90 ° Note: An angle of approx. 15 ° provides better results for classification, as more object details are visible (e.g. wheels, axles, etc.)

Specifications for the environment

Object speed

< 130 km/h

Day/Night/Lighting

During the day/well lit/night vision

Indoor/outdoor use

Exterior

Expected accuracy

(counting + classification if all environmental, hardware and camera requirements are met)

Counting >95 % (vehicles, bicycles) Classification of main classes: >95 % Classification of sub classes: >85 %

Hardware specifications

Supported products

BMA, mobil BMA,B101, B401

Frames Per Second (fps)

25

Using the camera parameters defined below ensures that the minimum required PPM value is achieved. Tip: Use the or a .

Camera mounting - horizontal angle to the object

​These classes
Pixels per Meter (PPM)
lens calculator from Axis
generic lens calculator