[Transportation] Referencing time-bounded conditions (closures, work zones, incidents) to segments / GERS?

[travelcamnet]

The point-events thread (#354) and the schema gap noted there got me thinking about the transient side. Segments + GERS are a great anchor for static attributes, but a lot of real-world road state is time-bounded — closures, work zones, incidents, seasonal load/clearance limits — appearing and clearing on a segment over hours or days.

Is there any roadmap or thinking on how time-bounded conditions would be referenced against segments (linear-referenced + a validity window), or is the expectation that consumers keep that as a separate overlay keyed to GERS IDs?

Context for why I ask: I work on road511, which normalizes 30+ US/Canada DOT 511 feeds (incidents, closures, work zones, restrictions). We carry our own conflation step to match those to road geometry today, and GERS looks like it could simplify that join if transient data had a referencing pattern. Curious whether that's in scope for Transportation or intentionally left to consumers.