FICTIONAL ROAD EVENT EXERCISE
Yenra | October 11, 2026
Guide: https://yenra.com/geospatial-solutions/
CSV: https://yenra.com/geospatial-solutions/road-events-example.csv
These are invented educational records, not real road assets or a live network.
Assumptions: R17 is a continuous calibrated route from 0.00 to 10.00 miles;
measures increase along it; measure differences represent along-route distance.
Network version: training-2026-01. No coordinate geometry is supplied.
Fields:
event_id: unique event identifier (text)
route_id: measured route identifier (text)
event_type: point or line
from_measure: single point measure or beginning of a line event (decimal miles)
to_measure: end of line event; empty for point events (decimal miles)
units: miles
network_version: identifier of the compatible measured route release
description: fictional event description
Open the CSV as a comma-delimited UTF-8 table in a spreadsheet or text editor.
For GIS use, first separate point and line rows and supply a compatible measured
route; map the point measure to from_measure and line limits to both fields.
Questions:
1. Is C01 inside P01? Yes: 2.00 <= 2.40 <= 3.50.
2. P01 length? 3.50 - 2.00 = 1.50 miles.
3. I01 length? 4.00 - 3.00 = 1.00 mile.
4. Overlap? 3.50 - 3.00 = 0.50 mile.
5. Unique combined interval? 4.00 - 2.00 = 2.00 miles.
6. Sum of event lengths? 2.50 miles, including the overlap twice.
Quality checks: IDs must resolve; required measures must exist; units/version
must match; line measures must increase; all measures must lie within 0-10.
An 11.20 measure is out of range. A 4.00-to-3.00 interval needs investigation.
Define endpoint membership explicitly when counting point events at boundaries.
Real calibration gaps or discontinuities require the network owner's rules;
simple measure subtraction may not represent physical mileage in such networks.