Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on June 19, 2017, 04:43:09 am
-
Still using the old 'AR549' label for I-49 in both US-71 & US-59's files.
==
On a side note, should we extend AR I-49's (Texarkana) file just a tic to sync up with with US-71/59's files for now? I mean, TX isn't going to be building any part of I-49 any time soon. And it would be nice for the HB to link to the route. It's that or create a separate TX I-49 file right now.
-
Still using the old 'AR549' label for I-49 in both US-71 & US-59's files.
https://github.com/TravelMapping/HighwayData/pull/1390
On a side note, should we extend AR I-49's (Texarkana) file just a tic to sync up with with US-71/59's files for now? I mean, TX isn't going to be building any part of I-49 any time soon. And it would be nice for the HB to link to the route. It's that or create a separate TX I-49 file right now.
It would be nice, yes, but I can't quite justify it right now. All the tilemap sets, the TXDOT Statewide Planning Map, and AHTD shapefiles all have the AR/TX border about where the AR/TX point is now, just a bit east of the US59/71 roadway. TXDOT designation files don't have any mention of I-49, yet. Effectively, we just have... some ramps, that lead between TX US59/71 and I-49 proper in Arkansas.