Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: yakra on September 30, 2021, 02:42:41 pm
-
Another pair of waypoints uncovered by an oddly specific shell script...
8(E) threw me off at first. Looks like an instance of wayptlabels.php#noconc (https://travelmapping.net/devel/manual/wayptlabels.php#noconc); at first I interpreted E as meaning East, but it probably means Express? Is it actually signed as an Exit 8 though; is it really a proper use of a secondary exit number sequence? I'd almost suggest fudging it to 8A, but then, if we don't have Two separate interchanges numbered (https://travelmapping.net/devel/manual/wayptlabels.php#nextsuffix) 8...
AFAIK, there haven't been enough instances of these express-lane-only exits to develop a consistent approach nationwide (site-wide?).
FWIW TX I-69 (https://travelmapping.net/hb/showroute.php?r=tx.i069) has several, unnumbered.
BraPkwy(E) should just be BraPkwy though, as we're no longer dealing with exit numbers to disambiguate at this point.
-
It was mainly just a fudged # with a (E) added to it. Couldn't seem to find any #'ing. Plus looking at the MM's along it, it starts out at 6 oddly there.
Not sure what (if anything) I should rename it too.
-
Another case of there not really being any good option.
-
Could always just split out the 'Express' lanes and give them they're own file with an 'Express' banner. That's about the only other option to be honest since they do technically have different end points than the main route.
-
If 8(E) were to soldier on, I don't think the world would end. There's been stranger stuff.
-
So, we'll declare this as a 'no-build'. :)