Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: US 89 on February 02, 2019, 10:21:14 pm

Title: CO: E470 should be moved to usasf?
Post by: US 89 on February 02, 2019, 10:21:14 pm
The E-470 highway in Colorado is currently listed in the Colorado State Highways, but it isn't a state highway. Colorado considers it to be the same thing as Northwest Parkway, which is currently in the usasf system. They even have similar CDOT reference numbers: E470 is 470B, while the Northwest Parkway is 470N.

In addition, the most similar case to this that I can find is CC 215 in Las Vegas, which is mapped as part of usasf: http://travelmapping.net/hb/?units=miles&u=null&r=nv.cr215

This should probably be in usasf, and maybe just as "E470", not as "COE470" since it isn't a CO state highway.
Title: Re: CO: E470 should be moved to usasf?
Post by: cl94 on February 02, 2019, 10:26:36 pm
I'm going to second this. E470 is a name. As far as the State of Colorado is concerned, E470 = Northwest Parkway as far as internal numbering (http://dtdapps.coloradodot.info/otis/HighwayData#/ui/0/0/criteria/470N/46.398/54.45). If I

Clark County 215 is precedent here, IMO. That is certainly the best comparison, given that both have numbers and neither are really "state highways". Since we're not mapping unsigned SR designations, E470 belongs over in USASF.
Title: Re: CO: E470 should be moved to usasf?
Post by: si404 on February 06, 2019, 06:31:35 am
Any objections?
Title: Re: CO: E470 should be moved to usasf?
Post by: froggie on February 07, 2019, 05:34:27 pm
Functionally, it's an extension of CO 470.  Why not just leave it as-is?
Title: Re: CO: E470 should be moved to usasf?
Post by: Duke87 on February 07, 2019, 08:26:27 pm
It won't affect anyone's travels either way. It's purely housekeeping.

As I see it the arguments in favor of a move are:
- The road is not maintained by the state of Colorado, rather by a multi-county agency. This could be interpreted as making the road a county route.
- While CDOT does have an internal numerical designation for the road, it is 470B, not E470
- The road is not signed with CO state highway shields. It has its own special shield.
- It is an odd case with few if any direct parallels, but the most similar situation is Clark County 215 in Nevada, which was put in usasf.

And the arguments against are:
- So what if it's county maintained, there are plenty of state routes out there that are county maintained in part or entirety. And it has a state route designation!
- So what if the internal designation is slightly different, there are plenty of cases where the internal designation for a road has a suffix that isn't signed in the field. See all state routes in Maryland with multiple segments for example.
- It is contiguous with CO 470, which is clearly a state highway by the same number. And it exists due to planning by the state, even if the state didn't build and doesn't maintain it.
- When in doubt, default to status quo. Ruling on the field stands unless there is clear and convincing evidence it should be overturned.


It makes no difference to me personally. I have no objection to moving it. I have no objection to leaving it as is, either.

It would be nice if we had an actual E470 shield for it though, instead of shoving "E470" in the CO shield which just doesn't look right.
Title: Re: CO: E470 should be moved to usasf?
Post by: Jim on February 07, 2019, 09:33:25 pm
I'm in favor of moving it to usasf and including the old COE470 .list name as an alt name so no user lists will break.
Title: Re: CO: E470 should be moved to usasf?
Post by: cl94 on February 07, 2019, 10:16:59 pm
It's worth noting that, in the field, E470 is clearly distinct from SH 470 and the state highway system. As far as presentation, E470 isn't too different from the Garden State Parkway. Heck, the newer posted E470 shields even have "SM" on them (https://goo.gl/maps/dR9KbwxpWaK2). Registered service mark = name.
Title: Re: CO: E470 should be moved to usasf?
Post by: si404 on February 08, 2019, 05:01:27 am
 Moving it, but breaking nothing. Reasoning being it's simple to do, and allows a proper shield.
Title: Re: CO: E470 should be moved to usasf?
Post by: vdeane on February 09, 2019, 06:47:48 pm
I wonder if this opens up a can of worms with ON 407/407 ETR.  Although CO 470/E470 resets mileage and exit numbers, and ON 407 doesn't.
Title: Re: CO: E470 should be moved to usasf?
Post by: rickmastfan67 on February 09, 2019, 08:07:43 pm
I wonder if this opens up a can of worms with ON 407/407 ETR.  Although CO 470/E470 resets mileage and exit numbers, and ON 407 doesn't.

I say 407 plays like PA-43/PA Turnpike 43 & PA-66/PA Turnpike 66 do.  That's how I've always thought it.
Title: Re: CO: E470 should be moved to usasf?
Post by: si404 on February 10, 2019, 04:00:21 am
Or the Florida Toll State Highways...
Title: Re: CO: E470 should be moved to usasf?
Post by: Duke87 on February 10, 2019, 11:40:11 am
The PA and FL examples are different though in that they only use a modified version of the state shield to signify tolling - PA's "toll" shields are still keystones, just color swapped and with the word "toll" added in; FL's are still the state outline, just with a frame added around it. 407 ETR, like E470, switches to a completely different and unique shield.

Title: Re: CO: E470 should be moved to usasf?
Post by: oscar on February 10, 2019, 12:05:27 pm
407 ETR, like E470, switches to a completely different and unique shield.

If anyone gets the idea of doing to 407 ETR what was done with E470, remember that the Canadian counterpart to usasf is still in devel status, unlike usasf which is active.
Title: Re: CO: E470 should be moved to usasf?
Post by: mapcat on February 10, 2019, 01:58:47 pm
It's ridiculous that cannf is still in devel.
Title: Re: CO: E470 should be moved to usasf?
Post by: froggie on February 10, 2019, 08:18:47 pm
Quote from: Duke87
switches to a completely different and unique shield.

This is the same logic that Tim kept going back to with Vermont and why the Vermont state routes were never finished under CHM.
Title: Re: CO: E470 should be moved to usasf?
Post by: vdeane on February 10, 2019, 09:48:49 pm
Not to mention that Ontario likes to make it VERY clear when you're switching from 407 ETR to ON 407: https://en.wikipedia.org/wiki/Ontario_Highway_407#/media/File:407_ETR_Ends_where_ON_407_begins.jpg

Not that I really see a huge need to split it, though not being familiar with Colorado, I'm not quite sure why CO 407 and E470 are separate when other roads like ON 407 and 407 ETR are together, aside from the mileage/exit number reset.
Title: Re: CO: E470 should be moved to usasf?
Post by: Duke87 on February 10, 2019, 11:46:21 pm
Quote from: Duke87
switches to a completely different and unique shield.

This is the same logic that Tim kept going back to with Vermont and why the Vermont state routes were never finished under CHM.

Indeed, which was hugely annoying and a fiasco we don't need to repeat. But in that case it was about whether to include the circle routes at all, which is far more consequential a decision than deciding which system a route or group of routes goes in.

For what it's worth I don't think 407/407 ETR should be split. Seems like unnecessary effort that wouldn't really accomplish anything beyond forcing users who've driven both portions to put an extra line in their list file. But I do acknowledge that valid arguments in favor of doing so do exist.