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
  • Configuration of a Traffic Flow survey
  • Selection of the Tenant
  • Add Survey
  • Definition of key data (location, date und traffic types)
  • Add/edit cameras
  • Configuration of a cordon
  • Node
  • Trigger
  • Journey time Min/Max
  • Publish survey
Export as PDF
  1. Data Center
  2. Traffic Flow

Configuration of a Traffic Flow survey

PreviousTraffic FlowNextData analysis

Last updated 5 months ago

Configuration of a Traffic Flow survey

After successful installation and configuration of the BCA, open the web browser and enter the following address:

You can log in to the website with your customer login. If you have problems logging in or have forgotten your password, can help you.

To create a survey, first open the highlighted „Config App“ tab at the top right of the menu bar.

Selection of the Tenant

Next, select the desired tenant to continue with the configuration. The tenant can be used to group measurement series. If you require more than one tenant, please contact customer service. Switch to the “Traffic Flow” tab.

Add Survey

You have the option of filtering your surveys by date or text content. It is therefore advisable to select the name of the survey so that it can be easily found later and, if necessary, different groupings are possible using the text filter (e.g. location/project number).

A new survey can be created using the “Add element” button. A new field is created in which the name of the survey must be defined. Save the process with the blue button with the memory card symbol.

To edit a created survey, select the relevant survey by clicking on it. A user interface then opens below the list of created surveys. The selected survey can be configured using the highlighted “Edit” button.

Definition of key data (location, date und traffic types)

A window opens with the key data - Name, Alias, Start date, End date, Time zone and Traffic types.

Table 1: Definition and key data of a survey

Name

Describes the name of the survey that you initially assigned when creating the survey. If required, the name of the survey can be edited in the corresponding field.

As it is possible to filter the surveys by name, it is recommended to select a unique name.

Date

The start and end date define the period for the data evaluation. For the start and end date, 00:00 is automatically selected as the time, with the end date including the selected day.

Example:

For a survey on the 01.01.2023 from 0:00 to 23:59, the start date and end date are both 01.01.2023.

Alias

Describes a unique name with which the results of the survey can be retrieved via the API. The alias of the survey can be edited in the corresponding field. Note: Only alphanumeric characters (a-z, A-Z, 0-9) are valid here.

Time Zone

The time zone is set to the “Europe/Vienna” region by default.

It is recommended to select the local time zone of the survey in the menu.

Traffic types

The traffic types are the vehicle classes that are to be included in the evaluation for this survey. By pressing the Ctrl key, several traffic types can also be selected for a single survey.

In order to make the application possibilities of the evaluation more flexible, the selection of the survey can also be adjusted retrospectively. Note: Only traffic types with license plates are listed.

After successfully configuring the key data of the survey, save this process by clicking the save button.

Add/edit cameras

The next step is to assign the BCAs used to the survey. To do this, open the selection window by clicking on “Add/edit cameras” (see Figure 6). Add all the BCAs that you are using or have used for this survey.

Once you have selected your BCA, click on “Add selected camera” and it will appear in the “Cameras” table (see Figure 7).

Configuration of a cordon

Node

A traffic flow survey should consist of at least 2 nodes. Open the “Survey layout” section and navigate to the correct position on the map. Now add a new node using the pen tool.

Table 2: Node types

Node types

Cordon

Node for incoming and outgoing traffic in a cordon (closed area).

Trips that are evaluated always start and end at a cordon. They are then evaluated as transit traffic. If a journey has only been detected at a start node, it is evaluated as destination traffic in the area.

Midpoint

Nodes within the cordon.

Trips that are classified as transit traffic can be broken down into sub-routes in more detail using center nodes.

The following figure shows an example traffic survey with a cordon and which node types should be configured where:

Nodes A, B, C and D are cordon nodes. This is where the tracking of trips through the cordon, i.e. the area defined by the nodes, begins and ends.

Nodes E and F are midpoints and are used for a differentiated analysis of the sections over which the through trips have passed. For example, through traffic may have traveled from A to B on a direct route or via the midpoint E. This differentiation is possible using the “Show subjourneys” option in the evaluation.

Trigger

The node can be edited and triggers configured using the selection tool. Select the crossing line trigger of the corresponding device.

Table 3: Trigger parameter

Start direction and End direction

Available for cordon type nodes. Shown as an arrow between nodes.

  • Start of journey describes the beginning of a traffic flow, into the cordon.

  • End of journey describes the end of a traffic flow, out of the cordon.

  • The direction is defined by the counting line direction.

Example:

  • The trigger of the node Geyrstraße defines the Start direction.

  • The trigger of the node Amraser See Straße defines the End direction.

  • In this example of the Geyrstraße defines the Counting Line the direction IN (towards the city center) the direction into the cordon.

Journey time Min/Max

Min/max values between accounts can be specified for the traffic flows. Traffic flows outside the specified value ranges are not taken into account for the data analysis. A calculator based on speed and air distance is available.

Publish survey

Note!

The used directions are defined by the Counting Line of the Control Center.

If the configuration is error-free, the survey can be published. A published survey can now be viewed in the .

“Data App”
https://datacenter.bernard-gruppe.com
Support Center
Figure 1: Tenant & Survey
Figure 2: Adding a new survey.
Figure 3: Configuration of a selectet survey.
Figure 4: Add/edit cameras
Figure 5: Overview of the survey
Figure 6: New node
Figure 7: Example node types
Figure 8: Trigger configuration
Figure 9: Journey time Min/Max
Figure 10: Publish survey