Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on November 06, 2019, 06:30:07 am
-
According to the below linked post from AARoads, the bypass is planned to be opened on November 21, 2019. I am unsure quickly searching the forum if it will be posted as NC 11 or NC 11 Bypass.
https://www.aaroads.com/forum/index.php?topic=100.msg2454145#msg2454145
-
This picture from reply #3077 in the NC thread (credit: mrHappy1261) shows a BGS calling it NC 11 Bypass
https://prnt.sc/pqw0u9
-
NC 11 Bypass Greenville file created and in the queue
-
I drove it earlier today, and can confirm that it's signed as Bypass NC 11 (not just the new SW segment, but also the NW quadrant of the bypass, which had previously been only US 264). Also, the old route appears to be still signed as vanilla NC 11.
https://www.aaroads.com/forum/index.php?topic=100.msg2457758#msg2457758
-
mapmikey, was looking @ the file that Jim uploaded for you for the Bypass file, and noticed that you have the 'southern' junction labeled as 'NC11_S'. It does have an exit number 112 (https://www.aaroads.com/forum/index.php?topic=100.msg2457864#msg2457864), and I think it can legitly be added.
-
mapmikey, was looking @ the file that Jim uploaded for you for the Bypass file, and noticed that you have the 'southern' junction labeled as 'NC11_S'. It does have an exit number 112 (https://www.aaroads.com/forum/index.php?topic=100.msg2457864#msg2457864), and I think it can legitly be added.
My interpretation of the manual (http://travelmapping.net/devel/manual/wayptlabels.php) is that NC11_S is correct.
For auxiliary routes connecting to the parent route at both ends, mention only the parent route (even if it is concurrent with other routes) and add direction suffixes.
For spurs that connect only once to the parent route, simply mention the parent route for that end and ignore any concurrent routes.
These two rules override other directions.
-
I think a route with exit numbers for it's entire length would overrule that.
-
I think a route with exit numbers for it's entire length would overrule that.
Speaking of which:
NC43 -> 75(264)
NC33 -> 77(264)
NC11_N -> 80(264)
These two rules override other directions.
Hm, well sonofagun. I'm with rickmastfan67 that surely exit numbers would overrule this.
Sometimes the manual does get a bit murky; we gotta speculate on what the intended meaning was/is... Should we add a caveat to clarify to the manual? Something like "These two rules override other directions, except for routes using exit numbers as waypoint labels."?
-
I think a route with exit numbers for it's entire length would overrule that.
Speaking of which:
NC43 -> 75(264)
NC33 -> 77(264)
NC11_N -> 80(264)
These two rules override other directions.
Hm, well sonofagun. I'm with rickmastfan67 that surely exit numbers would overrule this.
Sometimes the manual does get a bit murky; we gotta speculate on what the intended meaning was/is... Should we add a caveat to clarify to the manual? Something like "These two rules override other directions, except for routes using exit numbers as waypoint labels."?
Note that I would’ve used the US 264 exit numbers in the 11 bypass file but the US 264 file doesn’t use them either.
-
Note that I would’ve used the US 264 exit numbers in the 11 bypass file but the US 264 file doesn’t use them either.
I think that since US-264 seems to use exit numbers for almost 50% of it's length, it's safe to convert it on the site.
-
Note that I would’ve used the US 264 exit numbers in the 11 bypass file but the US 264 file doesn’t use them either.
I think that since US-264 seems to use exit numbers for almost 50% of it's length, it's safe to convert it on the site.
i will do this on my next update.
Note that there is no Exit 112 on the NC 11 Bypass itself. Exit 112 is mainline NC 11 northbound approaching the bypass...
-
Note that there is no Exit 112 on the NC 11 Bypass itself. Exit 112 is mainline NC 11 northbound approaching the bypass...
Ah yes. This changes things.
-
Note that there is no Exit 112 on the NC 11 Bypass itself. Exit 112 is mainline NC 11 northbound approaching the bypass...
Ah yes. This changes things.
Could debate that because of the placement of the 'exit' tab. lol.
-
Hm yeah. Fnord.
Amusing innit, how the exit are mileposted starting seemingly from NC11 itself, then continue onto the child route... Heh.
-
Just happened to notice this, but the exit numbers along the US-264 part were incorrectly added.
They were added as 'US264(*)' style labels, when they should have been '*(264)' labels due to the Bypass using exit numbers it's entire length.
Thankfully, this only effects 2 exit labels.
US264(75) -> 75(264)
US264(77) -> 77(264)
-
To go back to the old set of comments about bannered routes and their labels with the parents: the aim of the override rule is that the labels are reliable. If you've travelled on US123 and at the towns of Abcoude you take the business route before rejoining the mainline and then at Defsville you take the bypass route before again returning to vanilla 123, you don't need to click through and see what the labels are on the bannered routes as they would be: US123_S and US123_N.
We don't do that consistently (despite the rule) rendering it pointless.
As for this route, yes, use exit number first. And I look forward to this all being redone with new exit numbers before too long after Greenville get NC DoT to give the North-South proposed freeway corridor via the city an I-x42 or I-x87 number (and I'd expect the 'magic' blue and red shields to go up long before the freeway is extended to either parent and perhaps before the parents even reach the planned termini!).