Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Transportation Operations topic
No spam. Unsubscribe anytime.
Engineers explain level‑of‑service standards, data expectations and mitigation options
Summary
Presenters explained how level‑of‑service (A–F) is used to evaluate impacts, that chapter 6 requires LOS D per movement as a minimum, and that mitigation options include turn lanes, signal timing, or scope reductions when impacts cannot be mitigated.
Traffic engineers explained how they measure intersection operations and determine mitigation: analyses use industry software and report level of service (LOS) by movement; Castle Pines' Chapter 6 sets LOS D as the minimum acceptable level for each movement and overall. "Chapter 6 says level of service d for each movement and overall is the minimum standard," one engineer told the council.
Engineers also explained data expectations: traffic counts two years old or newer are preferred for volumes, crash data generally uses a five‑year window, and applicants must include correct roadway geometry and signal timing inputs. If a proposed development degrades LOS below acceptable thresholds, mitigation may include adding turn lanes, right‑turn lanes, adjusting signal timing, or — in some cases — reducing the scope or density of the proposed development. Queueing and the risk of backing into adjacent intersections are additional operational concerns that reviewers look for when assessing mitigation needs.
Where crash history or special local issues exist (for example, nearby schools or known congestion corridors), engineers said they will request additional analyses or counts to ensure the TIS addresses localized safety concerns. Staff recommended applicants coordinate early with the city to minimize iterative cycles.
