Measuring Point Configuration¶

The Measuring Point configuration allows you to define metadata about the traffic measurement location. This information is essential for generating official reports, particularly for GPR (Generalny Pomiar Ruchu) system used in Poland.

Overview¶

Measuring point properties are used to: - Identify the measurement location in reports - Provide temporal context (date/time) for traffic data - Generate GPR-compliant XML reports for Polish road authorities - Organize and catalog measurement data

These fields are stored in PropertiesConfig and are particularly important for Polish road traffic measurement standards.

Configuration Fields¶

Point Name (`PointName`)¶

Purpose: Main identifier for the measurement point
Format: Free text
Default: Empty string
Used for: GPR point number identification

The point name is the primary identifier for the measurement location. In GPR context, this typically corresponds to: - GPR point number (e.g., "41118") - Road identifier (e.g., "DK79") - Custom location code

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

Point Extra Name (`PointExtraName`)¶

Purpose: Additional description or sub-identifier
Format: Free text
Default: Empty string
Used for: Secondary location information

Can be used for: - Direction description (e.g., "Kierunek Kraków") - Location details (e.g., "Before intersection") - Additional identifiers

Point Name Suffix (`PointNameSufix`)¶

Purpose: Suffix appended to point name
Format: Free text
Default: Empty string
Used for: Report naming, file organization

Useful for: - Version tracking (e.g., "_v2") - Measurement session identification (e.g., "_autumn") - Configuration variants (e.g., "_vehicles_only")

Point Date (`PointDate`)¶

Purpose: Date when traffic measurement started
Format: YYYY-MM-DD (ISO 8601)
Default: Empty string
Used for: Report headers, data organization, GPR XML generation

Critical for: - Temporal analysis of traffic patterns - Seasonal traffic comparisons - Official GPR report requirements - Archival and cataloging

Point Start Time (`PointStartTime`)¶

Purpose: Time when traffic measurement started
Format: HH:MM:SS (24-hour format)
Default: Empty string
Used for: Precise timestamp synchronization, GPR XML generation

Important when: - Video files lack proper timestamps - Synchronizing multiple cameras - Generating time-based traffic reports - GPR 5-minute interval reports

GPR (Generalny Pomiar Ruchu) Integration¶

What is GPR?¶

GPR (General Traffic Measurement) is Poland's national traffic counting system managed by GDDKiA (General Directorate for National Roads and Motorways).

GPR requirements: - Standardized XML format for data submission - Specific point numbering system - 5-minute aggregation intervals - Detailed road and location metadata

GPR XML Report Generation¶

Point Lookup: System searches for point in database by PointName
Metadata Population: If found, fills in:
Road category (kat_dr)
Road number (nr_dr)
Road segment (odcinek)
Locality (miejscowosc)
Additional lanes (jezd_dod)
Classification type (klasyfikacja)
Direction Matching: For each traffic direction (L, P, etc.):
Retrieves direction metadata from database
Includes destination (kier_miejsc)
Includes chainage (pikietaz)
Includes GPS coordinates
Temporal Data: Uses PointDate for day grouping in XML:
Validation: XML is validated against official GDDKiA XSD schema:

Missing Data Handling¶

If point is not found in database: - Default values used: "@MISSING@" - XML still generated but marked as incomplete - User should update database or manually fill fields

Vera system import¶

The system can import GPR points from CSV file:

CSV Format Requirements: - Semicolon separator (;) - Required columns: - Numer odcinka → Point number - Kategoria drogi → Road category - Numer drogi → Road number - Nazwa odcinka → Segment name (format: Start-End) - Miejscowość → Locality - Pikietaż punktu pomiarowego → Chainage (format: P:value;L:value) - Jezdnie dodatkowe → Additional lanes flag - Klasyfikacja techniczna drogi → Technical classification

Database Storage¶

Location: temp/gpt_point.json
Format: JSON with Pydantic validation
Singleton: Only one database instance per application
Auto-save: Modified data saved on application exit