Skip to content

Measurement Point Configuration

The Measurement Point configuration defines metadata for a traffic survey location. This information is required when generating official reports, particularly for Poland's GPR (General Traffic Measurement) system.

Overview

Measurement-point properties are used to:

  • identify the survey location in reports,
  • generate GPR-compatible XML reports for Polish road authorities,
  • organize and catalogue measurement data.

Identification fields are stored in PropertiesConfig. File and result times come from the canonical measurement data, while the time shown in a report can be configured independently in the reporting tab.

Configuration fields

Point name (PointName)

  • Purpose: Primary measurement-point identifier
  • Format: Any text
  • Default: Empty string
  • Used for: GPR point-number identification

The point name is the primary identifier of the survey location. In a GPR context, it usually represents:

  • a GPR point number, for example "41118",
  • a road identifier, for example "DK79",
  • a custom location code.

Sanitization: The system automatically removes a "# " prefix and trims whitespace.

Extra point name (PointExtraName)

  • Purpose: Additional description or secondary identifier
  • Format: Any text
  • Default: Empty string
  • Used for: Additional location information

It can describe:

  • a direction, for example "Towards Kraków",
  • location details, for example "Before the intersection",
  • an additional identifier.

Point-name suffix (PointNameSufix)

  • Purpose: Suffix appended to the point name
  • Format: Any text
  • Default: Empty string
  • Used for: Report naming and file organization

It is useful for:

  • version tracking, for example _v2,
  • identifying a survey session, for example _autumn,
  • configuration variants, for example _vehicles_only.

Measurement time

The GUI, media, and persisted results always use the canonical time recognized from the recording and server data. If the date cannot be recognized, the application displays a warning before the job is uploaded. The user can continue, and the results remain available on a technical timeline beginning at 1900-01-01.

Dates in GPR documents, XML, and other reports come from the result time after an optional report start time is configured. The configured report start time does not change file times or data saved by the server.

Report time range

The reporting tab can restrict a report to a selected time range. The slider moves in five-minute increments and filters the prepared data by event time. By default, its handles cover the entire location. Moving either handle stores both the beginning and end of the selected period.

This range does not change the material processed by the server. It is applied locally when creating a report. For recordings without a recognized date, the application displays a technical timeline beginning in 1900; the slider then displays only hours and minutes.