| View previous topic :: View next topic |
| Author |
Message |
yakra
Joined: 30 Jul 2008
Posts: 2600
Location: Area Code 207
|
 Posted: Sat Aug 08, 2009 4:31 pm Post subject: CO I-25 |
 |
|
CO I-25 14A appears to be closed already.
There's some construction in the area, going south thru the 13B & 13A area, but I have no knowledge of when or what the results will be. |
|
| Back to top |
  |
 |
andytom
Joined: 14 Jul 2008
Posts: 412
Location: Beaverton, OR
|
| Posted: Mon Aug 10, 2009 2:57 pm Post subject: Re: CO I-25 |
|
|
| yakra wrote: | CO I-25 14A appears to be closed already.
There's some construction in the area, going south thru the 13B & 13A area, but I have no knowledge of when or what the results will be. |
Checked the CDOT website. Looks like a multi-phase project with the current phase to be finished in 2011. I'll check back every few months until the new configurations become apparent and make the changes then. Looks like some of those close interchanges that we've been talking about elsewhere are being spread out a little.
--Andy |
|
| Back to top |
 |
|
yakra
Joined: 30 Jul 2008
Posts: 2600
Location: Area Code 207
|
| Posted: Mon Aug 10, 2009 8:37 pm Post subject: |
|
|
| Should 14A get a *, before the rest of the changes come in? |
|
| Back to top |
|
|
andytom
Joined: 14 Jul 2008
Posts: 412
Location: Beaverton, OR
|
| Posted: Tue Aug 11, 2009 4:17 pm Post subject: |
|
|
| yakra wrote: | | Should 14A get a *, before the rest of the changes come in? |
I'd rather just make it as one change. If it's still there at the end, it'll still be in the list. Otherwise, I'll just + it.
--Andy |
|
| Back to top |
|
|
yakra
Joined: 30 Jul 2008
Posts: 2600
Location: Area Code 207
|
| Posted: Tue Aug 11, 2009 7:42 pm Post subject: |
|
|
| andytom wrote: | | I'd rather just make it as one change. If it's still there at the end, it'll still be in the list. Otherwise, I'll just + it. |
True, it may be best to make the change at the end, in case it does in fact end up reopening.
But remember the difference between * & +:
* Used to denote a historic, closed interchange, for those who'd actually used it as a waypoint when it still existed.
+ was created to allow renaming existing points points potentially already in use by a traveler without breaking their LIST file.
I think it should be *ed and thus still shown - a new traveler could create an account, for example, and this point included could affect the total mileage from their past travels. |
|
| Back to top |
|
|
|
