Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on February 17, 2016, 05:53:37 pm

Title: TX: I-169
Post by: rickmastfan67 on February 17, 2016, 05:53:37 pm

Looks like we jumped the gun adding it to the site as it was officially posted just yesterday (02/16/16). http://www.aaroads.com/forum/index.php?topic=3624.msg2127291#msg2127291

Anyways, the main reason I made this thread is because of the point 'BakLn'.  Is there any reason it's there?  I've looked in Google Sat, and OSM, and there are absolutely no ramps that would be considered as connected to that road to justify a point for it.  Thus, I would recommend removing it from the file.

http://tm.teresco.org/devel/hb.php?r=tx.i169

Title: Re: TX: I-169
Post by: yakra on February 18, 2016, 01:32:20 am

BakLn is included because TX I-169 was a quick copy-paste job off of in-dev TX550. :)
If Google is to be believed (heh), it looks like I-169 is on the mainlanes, with TX550 on the frontage roads. Not far-fetched; there are several similar examples throughout the state.
Removing BakLn from I-169 and leaving it in TX550 will break the multiplex between these files, which is a Good Thing.
https://github.com/TravelMapping/HighwayData/pull/431

Heh. Ironic that the officials had their ceremony, complete with sign unveiling, at the NON-interchange...

Title: Re: TX: I-169
Post by: yakra on March 16, 2018, 09:43:15 pm

May have been a bit quick on this. Looking at Satellite View, there are indeed a couple ramps, just west of OldAliRd, joining the mainline near Abelardo Dr.

Title: Re: TX: I-169
Post by: yakra on March 26, 2018, 08:46:26 pm

https://github.com/TravelMapping/HighwayData/commit/bea0d766c8e99b4a42538065f708e61ac80fdc2c
Committed directly to master. Oops. Aah well. No harm done.