Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on September 23, 2018, 04:41:27 am

Title: TX: I-35
Post by: rickmastfan67 on September 23, 2018, 04:41:27 am
Some minor issues I saw when I just randomly decided to look at the route to see if any new exits had been added and were missing from TM.

1) Missing -> 125 == about half way between exits 124 & 127.
2) 217 should probably be moved a tad to the south and centered on Kyle Crossing.
3) NEW -> 219 == Probably center it @ Robert S. Light Boulevard based on the BGS's for the exit.
4) NEW -> 321 Callan Ranch Road (shown as Telephone Rd in OSM)
5) [I-35Gai] NEW -> 503 == About .8 miles from 504, enough IMO to justify a separate point.
Code: [Select]
503 http://www.openstreetmap.org/?lat=33.712770&lon=-97.161412
504 http://www.openstreetmap.org/?lat=33.724665&lon=-97.161348
Title: Re: TX: I-35
Post by: yakra on September 23, 2018, 02:31:42 pm
1) Missing -> 125 == about half way between exits 124 & 127.
3) NEW -> 219 == Probably center it @ Robert S. Light Boulevard based on the BGS's for the exit.
4) NEW -> 321 Callan Ranch Road (shown as Telephone Rd in OSM)
5) [I-35Gai] NEW -> 503 == About .8 miles from 504, enough IMO to justify a separate point.
https://github.com/TravelMapping/HighwayData/pull/2245

2) 217 should probably be moved a tad to the south and centered on Kyle Crossing.
This one, I'm of a bit of a different mind on. TX interchanges have their own unique wibble & wobble, often being spread out for some distance over the frontage road system. As you've no doubt seen. While I'd normally go with where the major crossroad is located, here I think may be more worthwhile to center the point on RM967, allowing a graph connection for when the RM roads are eventually drafted. I think there are some other examples of this around Texas, though I'm hard pressed to come up with any off the top of my head. It's been a while. To be fair though, what I have a more clear memory of is a case of multiple bridges/crossroads over the freeway, one of such being the FM road. I'm less sure about a case like this where the other highway just ends at the frontage road.
OTOH, I've ended routes at the frontage road (http://travelmapping.net/hb/index.php?r=tx.lp478) in some cases, though I've not always been consistent (http://travelmapping.net/hb/index.php?r=tx.lp395) in this approach. The way TX works, we're bound to have some routes without graph connections at the end; I recently saved a list of examples from the usatxl system (http://forum.travelmapping.net/index.php?topic=62.msg11391#msg11391) (and there may be more examples from other systems I didn't root out.)
Title: Re: TX: I-35
Post by: yakra on September 26, 2018, 12:30:48 am
Talked myself into it.
https://github.com/TravelMapping/HighwayData/pull/2255
Solved!