Curves
Table of Contents
- 1. Refined TODO for UDOT curves
- 1.1. DONE In curve display name, replace “UT” with “SR”
- 1.2. DONE Remove the part of the location name that shows a roadway feature (like east of stairs, etc) from display but retain in meta data.
- 1.3. TODO Match curve severity and ITIS codes to physical signage.
- 1.4. TODO Extend start of curve notification region to the MUTCD suggested distance from curve start.
- 1.5. DONE Extend curve notification region end point to the curve apex
- 1.6. TODO Review the TIM J2735 standard to see if we’re using heading degrees fully (or properly) and update if feasible without breaking Michael’s timeline (RIO determination needs to be made here).
- 1.7. TODO Get Michael a copy of each final TIM in JSON format for review
1. Refined TODO for UDOT curves
1.1. DONE In curve display name, replace “UT” with “SR”
1.2. DONE Remove the part of the location name that shows a roadway feature (like east of stairs, etc) from display but retain in meta data.
1.3. TODO Match curve severity and ITIS codes to physical signage.
Which curves are we targeting for this operation in 2373? Only SR-190 both itis codes and speed @ashton
1.4. TODO Extend start of curve notification region to the MUTCD suggested distance from curve start.
Which curves are we targeting for this operation in 2373? Only SR-190 What distance is that, per curve? @kjeld to spike/followup
1.5. DONE Extend curve notification region end point to the curve apex
Which curves are we targeting for this operation in 2373? Just power plant? yes not fully to the apex, slightly less @ashton send draft to michael
1.6. TODO Review the TIM J2735 standard to see if we’re using heading degrees fully (or properly) and update if feasible without breaking Michael’s timeline (RIO determination needs to be made here).
Seems like this can be worked in parallel, maybe even a different ticket? to reduce the implementation time we’re going to wait on this for now. @kstamm to break into seperate ticket
1.7. TODO Get Michael a copy of each final TIM in JSON format for review
Seems like this can be worked in parallel, maybe even a different ticket? blocked by notification region updates @kstamm to break into seperate ticket