search

sfcta / dta

Automatically exported from code.google.com/p/dta
GNU General Public License v3.0
4 stars 5 forks source link

Custom Priorities File #134

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Add code to output a custom priority file for 2-way stop sign intersections 
with the same facility type.

Original issue reported on code.google.com by alsu...@pbworld.com on 13 Aug 2012 at 5:04

GoogleCodeExporter commented 9 years ago 
Re-assigning this to Lisa as she is already working on the custom priorities 
file for the two-way stops at centroid connectors.

Original comment by alsu...@pbworld.com on 22 Aug 2012 at 1:40

GoogleCodeExporter commented 9 years ago 
Since intersections with custom tfollow attributes are also affected, it makes 
sense to just do this for all two-way stops.

Original comment by lisa.zorn@sfcta.org on 27 Aug 2012 at 4:59

GoogleCodeExporter commented 9 years ago

Original comment by lisa.zorn@sfcta.org on 27 Aug 2012 at 5:06

GoogleCodeExporter commented 9 years ago

Original comment by elizab...@sfcta.org on 29 Aug 2012 at 1:35

GoogleCodeExporter commented 9 years ago 
This file has been implemented, keeping this issue open for the last bit: 
implementing two-way stop control custom priorities.  I should be done with 
this early this week.

Original comment by lisa.zorn@sfcta.org on 24 Sep 2012 at 4:38

GoogleCodeExporter commented 9 years ago 
Fixed in Revision 404b04661be6

The importUnsignalizedIntersections.INFO.log now reports:
  10  : Failed to map
  29  : Ignored because they're signalized
  1845: Setting as allway-stop (including 122 questionable, with more stop signs than incoming links)
  0   : Setting as allway-stop in lieu of custom priorities
  918 : Setting as twoway-stop without custom priorities
  1022: Setting as twoway-stop with custom priorities

Original comment by lisa.zorn@sfcta.org on 26 Sep 2012 at 5:47