Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on December 05, 2023, 01:24:22 am
-
77 - South Colorado St (https://maps.app.goo.gl/1WfJU1sSNUxBqF3D6) (Opened sometime between Jan '13 & Feb '16.)
82 - East Monahans Pkwy (https://maps.app.goo.gl/doApZEL4k4Ju844E8) (Opened sometime between Jan '13 & Jul '14.)
137 -> 137A
138 -> 137B (https://maps.app.goo.gl/byMVCGxbbMNGe4Ey6)
138A -> 138 (https://maps.app.goo.gl/DhznauyN3FWiUKga6) (might make this area's numbering better)
154 -> needs recentered. They reconfigured this interchange completely. I-20BLSta will also need to be updated.
226A -> *226A (Closed between Jan '19 & Jul '19 (https://maps.app.goo.gl/YuSVbqUsHS1qMsrAA).)
NEW -> 412 - Frontage Rd (https://maps.app.goo.gl/BnMNh5ahdFTd6GP16) (opened sometime between Jun '19 & Dec '19)
452 -> BarRd (https://maps.app.goo.gl/fJApVeosAFT31JSZA) (no exit number posted)
-
77 - South Colorado St (https://maps.app.goo.gl/1WfJU1sSNUxBqF3D6) (Opened sometime between Jan '13 & Feb '16.)
82 - East Monahans Pkwy (https://maps.app.goo.gl/doApZEL4k4Ju844E8) (Opened sometime between Jan '13 & Jul '14.)
154 -> needs recentered. They reconfigured this interchange completely. I-20BLSta will also need to be updated.
NEW -> 412 - Frontage Rd (https://maps.app.goo.gl/BnMNh5ahdFTd6GP16) (opened sometime between Jun '19 & Dec '19)
Done.
137 -> 137A
138 -> 137B (https://maps.app.goo.gl/byMVCGxbbMNGe4Ey6)
138A -> 138 (https://maps.app.goo.gl/DhznauyN3FWiUKga6) (might make this area's numbering better)
Grumble. Of course 138 is in use.
This was signed as 138 from both directions in the (https://www.google.com/maps/@31.9792321,-102.046459,3a,45.5y,74.13h,85.65t/data=!3m10!1e1!3m8!1sSTJpDxVivZ67lIDMrsyb6g!2e0!5s20130501T000000!7i13312!8i6656!9m2!1b1!2i39?entry=ttu) past (https://www.google.com/maps/@31.9796913,-102.0450314,3a,37.5y,74.43h,88.35t/data=!3m10!1e1!3m8!1sFxY5VGLVMxkzxhw6DnZz4Q!2e0!5s20181101T000000!7i13312!8i6656!9m2!1b1!2i39?entry=ttu), which IMO is better, as it's operationally one thing, a "double half interchange". But whatcha gonna do. TM's exit numbering should reflect what's out there in the field, for better or worse. :( Changed.
This is one thing I don't like about TX. With the density of interchanges in more urban areas combined with the way frontage roads and their ramps are often laid out, a small reconfiguration like this can result in renumberings that though minor can break .list files.
Arguably a minor break; everyone gets 0.21 mi more on either I-20 or its frontage roads they'd intentionally excluded here.
I-20 affects: 25or6to4
TX158 affects: bejacob dharwood Ib3kii jonfmorse justjake keithcavey markkos1992 rlee
GitHub users have been pinged.
226A -> *226A (Closed between Jan '19 & Jul '19 (https://maps.app.goo.gl/YuSVbqUsHS1qMsrAA).)
Heh. Pretty obviously permanently closed. But still signed in July '19 if you back up 8 clicks. (https://www.google.com/maps/@32.4126763,-100.7013117,3a,75y,330.33h,86.55t/data=!3m10!1e1!3m8!1sPVIxnLo_D9INTcbv6ZwEHA!2e0!5s20190701T000000!7i16384!8i8192!9m2!1b1!2i39?entry=ttu)
And 226B is still 226B as of July '23, even if there's no longer a corresponding 226A. *Shrug.*
Marked closed.
452 -> BarRd (https://maps.app.goo.gl/fJApVeosAFT31JSZA) (no exit number posted)
C'mon, guys! It's a proper exit, with signs and everything! How hard is it to slap an exit number on it?
(https://4.bp.blogspot.com/-I2K3FNM5or0/WWaG-qrAu2I/AAAAAAAAAho/emMgxQzudIYowqxQPZ42pDyowqN9t8qJACLcBGAs/s1600/DMeye.png)
*Ahem.* Changed. 🤮
https://github.com/TravelMapping/HighwayData/pull/7137
-
Minor mistake in the update entries Yakra.
https://github.com/TravelMapping/HighwayData/pull/7137#discussion_r1443801094
You called the FM-715 exit as '137A' in both update entries for I-20 & TX-158 instead of '137B'.
-
https://github.com/TravelMapping/HighwayData/pull/7142