NV: Broken concurrences in Carson City

[oscar]

There are two out-of-synch points along the newly-completed Carson City Bypass, resulting in missing I-580 mileage in my stats.

-- I-580's exit 38 waypoint has different coordinates from the corresponding waypoints for US 50 and US 395

-- US 395's US50_W waypoint is out of synch with the corresponding waypoints for I-580, US 50, US 50BusCar, and US 395BusCar

Less important relabel suggestions:

-- for I-580, US50/US395 => US50/395 +US50/US395

-- for US50BusCar, US395_S => US50_W +US395_S

[si404]

-- for I-580, US50/US395 => US50/395 +US50/US395

Sorry, that was me rush changing a point labelled 'End'.

[ntallyn]

If we're still keeping US50BusCar (see http://forum.travelmapping.net/index.php?topic=2159.msg7244#msg7244), shouldn't the western endpoint be US50_W instead of US395_S?

[oscar]

My latest pull request solves this topic, though I'll need a follow-up pull request to change the US 395 exit numbers concurrent with I-580 to xx(580) format (differs from the US 50 exit number format, since US 395 has its own set of exit numbers non-concurrent with I-580, while US 50 doesn't).

[yakra]

Just to complicate things!!

It would appear the I-580 exit numbers are based on US395 mileage, and that if US395 were upgraded to I-580 in situ, the exit numbers would be the same.
Thus, US395 would qualify as having "its own" exit numbers... Leave as-is?

[vdeane]

Leaving them as-is sounds good to me!