Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on January 30, 2016, 09:36:23 am
-
I just discovered a few exits that are way off-centered along I-73/74 and need to be fixed in the data.
Exit #58, effects (current label in the "[]" part):
NC I-73 [58]
NC I-74 (High Point, NC) [58(73)]
NC US220 [I-73(58)]
Exit #41:
NC I-73 [41]
NC I-74 (High Point, NC) [41(73)]
NC US220 [I-73(41)]
NC US220AltCan [US220_S]
Exit #25:
NC I-73 [25]
NC I-74 (High Point, NC) [25(73)]
NC US220 [I-73(25)]
==
On a side note, I think we should also add in a '72B' point for I-73/I-74/US-220 @ Albemarle Road just North of the current Exit #72 for US-64/NC-49. Why you may ask? Well, even though it's not more than .5 miles from Exit #72, it has the missing movement for SB I-73/I-74/US-220 to gain access to WB US-64/NC-49 as that moment couldn't be fit into the main exit. It also allows people to go directly onto WB NC-49, and people might want to properly map where they got off in that area. Plus it has 3 out of 4 ramp moments itself (just lacking an off-ramp from I-73/I-74/US-220 NB). I think that alone should qualify it for the site, even though it's distance is less than .5 miles.
72B http://www.openstreetmap.org/?lat=35.687666&lon=-79.830812
-
On a side note
...
72B http://www.openstreetmap.org/?lat=35.687666&lon=-79.830812
Neither for nor against.
If implemented , I would do 72 -> 72A.
-
On a side note
...
72B http://www.openstreetmap.org/?lat=35.687666&lon=-79.830812
Neither for nor against.
If implemented , I would do 72 -> 72A.
Reason I suggested '72B' is because that's what it's posted as.
-
Right. 72B is 72B. I was getting overly specific (again) and suggesting 72 -> 72A.
-
I have submitted this change to Jim for update
Mike