For changes that need to be made on usatx routes before activation
Routes can be found here: http://tm.teresco.org/devel/hb.php?sys=usatx
missing: 45 (frontage roads), 114, 121, 151, 183, 191, 225, 267, 288, 358, 360
165 follows Comal to 7th
183A is not a state highway
234 continues north to I-37 at its west end
240 has a three-way intersection with itself west of I-44 exit 14?
what's with the gap in 364?
550 continues beyond 48 to FM 3248
SH 114 BUS in Roanoke...The western terminus is shown to be the Litsey Rd/ SH 114 intersection instead of the actual terminus.
SH 356: The portion of it within the Dallas City Limits was recently removed from the state highway system, but they failed to mention this in the highway designation files.
Quote from: NE2 on November 06, 2015, 06:35:31 PM
missing: 45 (frontage roads), 114, 121, 151, 183, 191, 225, 267, 288, 358, 360
165 follows Comal to 7th
The missing ones are mostly under usansf.
165 is only signed within the state cemetery...should we go by signage or the highway designation file?
Quote from: NE2 on November 06, 2015, 06:35:31 PM
missing: 45 (frontage roads)
TX45 is included in the USANSF set. Re the frontage roads, I see that 45 is a toll road -- so it looks like TX45 proper is on the frontage roads for Toll 45. As noted re Loop 49, the toll roads can get a little fudgey for the sake of including a route in TM that's not technically part of its respective system in TXDOT's eyes. So 45 gets included either way, but I don't see a need to differentiate its tolled mainlanes from the free frontage roads.
Quote from: NE2 on November 06, 2015, 06:35:31 PM
114, 121, 151, 183, 191, 225, 267, 288, 358, 360
I created a file for 267, but never added it to the system CSVs.
Fixed in my fork of the repo.The rest are included in the USANSF system, and will be moved over to USATXS when it's activated.
(Grumble. I meant to make note of this in the OP, but it slipped my mind when it came time to make the actual post.)
Quote from: NE2 on November 06, 2015, 06:35:31 PM
165 follows Comal to 7th
Quote from: snowedin on November 06, 2015, 10:48:51 PM
165 is only signed within the state cemetery...should we go by signage or the highway designation file?
Going by signage. A little more discussion on the old forum (http://clinched.s2.bizhat.com/viewtopic.php?p=16647#16647).
Quote from: NE2 on November 06, 2015, 06:35:31 PM
183A is not a state highway
Routes such as this (and TXLp49, etc.), I'm fudging on a little for the sake of getting them included in TM.
Quote from: NE2 on November 06, 2015, 06:35:31 PM
234 continues north to I-37 at its west end
Extended in my fork of the repo.Quote from: NE2 on November 06, 2015, 06:35:31 PM
240 has a three-way intersection with itself west of I-44 exit 14?
Not completely sure I follow you here. Are you talking about 3rd St and the "Oklahoma Cut Off"?
East of the OKCut, 3rd is just Loop 267. (Signage at Exit 14) (https://www.google.com/maps/@34.102892,-98.542874,3a,66.8y,234.6h,89.27t/data=!3m4!1e1!3m2!1sRUsOy9uem3IYeBjj_cHzQQ!2e0)
West of the OKCut, it's a 240/Lp267 multiplex.
This whole area was a bit tough to wrap my head around. It took lots of poring thru the designation files, understanding the historic designations of each route at the dates noted therein, and looking at HistoricAerials and GMSV before I finally got it.
Quote from: NE2 on November 06, 2015, 06:35:31 PM
what's with the gap in 364?
Going by signage.
Quote from: NE2 on November 06, 2015, 06:35:31 PM
550 continues beyond 48 to FM 3248
SH 550's designation file (https://www.dot.state.tx.us/tpp/hwy/sh/sh0550.htm) appears to desccribe not SH 550, but FM 511. This happens every now and again, a designation file describing a different route from the one intended. FM3248 already has a waypoint,
northwest of TX48.
The Statewide Planning Map has 550 ending at 48, so I went with that.
Quote from: Brian556 on November 06, 2015, 08:12:34 PM
SH 114 BUS in Roanoke...The western terminus is shown to be the Litsey Rd/ SH 114 intersection instead of the actual terminus.
This was informed by my point placement on TX114 proper. The point was placed where it is because it provides access to the westbound lanes, and it looks like this is where the interchange is going to go once the mainlanes are eventually built inside the frontage roads. Discuss.
Quote from: Brian556 on November 06, 2015, 08:12:34 PM
SH 356: The portion of it within the Dallas City Limits was recently removed from the state highway system, but they failed to mention this in the highway designation files.
Should the cutoff be made at Elm Fork Trinity River?
Do you have a link to the minute order?
I'll submit a pull request to make the changes noted above shortly.
Quote from: yakra on November 08, 2015, 03:06:15 PM
Quote from: NE2 on November 06, 2015, 06:35:31 PM
550 continues beyond 48 to FM 3248
SH 550's designation file (https://www.dot.state.tx.us/tpp/hwy/sh/sh0550.htm) appears to desccribe not SH 550, but FM 511. This happens every now and again, a designation file describing a different route from the one intended. FM3248 already has a waypoint, northwest of TX48.
The Statewide Planning Map has 550 ending at 48, so I went with that.
FWIW (not much), when I was in Brownsville in 2013, I drove what there then was of SH 550, and for some reason found it necessary to continue south of 48, to old route 48 (Capt. Donald Foust Rd.) or as far as I could go without entering the port's restricted area. I don't recall whether I saw a sign saying 550 continued beyond 48, or just didn't see an End 550 sign at the interchange with 48.
Absent better info, I agree with what the state map says.
I just checked the grid map (http://www.dot.state.tx.us/apps-cg/grid_search/_includes/countymapbook/Pages/412.pdf); it also has 550 ending at 48.
Pull request merged.
The changes noted above are now live in the TravelMapping HB.
NASA1: Is this a TX state route? NASAPkwy -> NASAPkwy_W
TX4: Mex/TX - surely ought to be MEX/USA or MEX/TX or something.
TX8: TX/AR - is AR41's border point also on google's placement of the border, rather than OSM's? Both probably should be fixed.
TX9: points not on route
TX15: point at CR7?
Quote from: english si on November 18, 2015, 10:49:01 AM
TX8: TX/AR - is AR41's border point also on google's placement of the border, rather than OSM's? Both probably should be fixed.
If the point placement is from a shapefile, this might just be an instance of Google more accurately defining the border than OSM.
Quote from: english si on November 18, 2015, 10:49:01 AM
TX4: Mex/TX - surely ought to be MEX/USA or MEX/TX or something.
Should not be MEX/TX. Either [country abbrev]/[country abbrev], or [state or other subdivision abbrev]/[state or other subdivision abbrev] is OK, but no mix-and-match of country/non-country abbreviations.
There are exceptions on the US/Canada border, but best to reduce rather than add to them.
NASA1: Yes, this is state highway (https://www.dot.state.tx.us/tpp/hwy/sh/shnasa.htm). (As is OSR (https://www.google.com/maps/place/Old+9+Rd,+Comfort,+TX+78013/@31.026959,-96.114188,3a,36.8y,200.23h,86.53t/data=!3m4!1e1!3m2!1sLzvr01wVhsFlwY6dCxf50Q!2e0!4m2!3m1!1s0x865b8d329b3d5483:0x8ac0c775afedcdea). Weird, huh?) I believe the "NASA Pkwy" designation just refers to the at-grade frontage roads underneath NASA1 itself.
TX4: Changed to MEX/USA.
TX8: I grabbed the coords again from the Statewide Planning Map, and got this (http://www.openstreetmap.org/?lat=33.568905&lon=-94.412530). It may not match Mapnik, but it matches MQOpenMap. USAAR is not yet in development.
TX9: Recentered all its points, and some of US190 & US190BusCop.
TX15: Please clarify.
TX152: I'm curious why there is a waypoint at FM2743 instead of US83 in Wheeler. These roads are only a block apart and US83 seems to be a better choice for a waypoint if only one is needed here (IMHO). At least, that's where I turned off TX152 when I passed through town.
TX205 has no waypoint for I-30.
TX54 has no waypoint for I-10BL.
Quote from: bejacob on November 28, 2015, 09:19:54 PM
TX152: I'm curious why there is a waypoint at FM2743 instead of US83 in Wheeler.
Quote from: mapcat on November 28, 2015, 11:54:34 PM
TX205 has no waypoint for I-30.
TX54 has no waypoint for I-10BL.
Looks like copy/paste fail on my part. All three added.
Edit: Or, should I say, all four. TX54 has a one-block multiplex with I-10BL.
TX66:
* FM 1777 is mislabeled FM1177.
TX240:
* The TX171 label looks like it should be something else. JefSt perhaps?
Quote from: ntallyn on December 19, 2015, 04:35:00 PM
TX66:
* FM 1777 is mislabeled FM1177.
Fixed.
Quote from: ntallyn on December 19, 2015, 04:35:00 PM
TX240:
* The TX171 label looks like it should be something else. JefSt perhaps?
Changed to FM171. Heh. And this file has the real FM1177 in it. :D