Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TX forum items, 2024-01-05 #7137

Merged
merged 4 commits into from Jan 6, 2024
Merged

TX forum items, 2024-01-05 #7137

merged 4 commits into from Jan 6, 2024

Conversation

yakra
Copy link
Contributor

@yakra yakra commented Jan 6, 2024

https://forum.travelmapping.net/index.php?topic=6019
Ping @mapcat because you were there.
Ping @Markkos1992 because you're good at finding errors.
https://forum.travelmapping.net/index.php?topic=5958
https://forum.travelmapping.net/index.php?topic=5994
https://forum.travelmapping.net/index.php?topic=5986


2024-01-05;(USA) Texas;I-40 BL (Amarillo);tx.i040blama;Waypoint TXLp335_W moved approx. 0.9 mi west from FM 2590.
Ping @aaroads @deathtopumpkins @flroads @marnen

2024-01-05;(USA) Texas;TX Loop 335;tx.lp0335;Removed from a demolished curve & FM 2590 (Soncy Rd) and relocated onto Hollywood Rd & Helium Rd between waypoints *OldTXLp335 & FM2590_N.
Ping @TXStormchaser @aaroads @bejacob @deathtopumpkins @flroads @mapcat @mapmikey @marnen @theweatherman561 @theRadison

2024-01-05;(USA) Texas;I-20;tx.i020;Waypoint 138 moved from FM 715 (now labeled 137A) to TX 140/158.
Ping @TXStormchaser

2024-01-05;(USA) Texas;TX 158;tx.tx158;Waypoint I-20(138) moved from FM 715 (now labeled I-20(137A)) to TX 140/158.
Ping @bejacob @jonfmorse @keithcavey @Markkos1992

@jteresco jteresco merged commit 0c850ef into TravelMapping:master Jan 6, 2024
@mapcat
Copy link
Contributor

mapcat commented Jan 6, 2024

Loop 335 looks good to me

@Markkos1992
Copy link
Contributor

I am fine with TX 158. I do not plan to look at Amarillo.

@@ -7227,6 +7227,12 @@ date;region;route;root;description
2015-11-29;(USA) Tennessee;US 641;tn.us641;Extended southward from the former ending intersection with I-40 along TN 69 & TN 114 to a new southern terminus at US 64
2015-10-25;(USA) Tennessee;I-269;tn.i269;Route added
2015-10-25;(USA) Tennessee;I-269 Future (Memphis, TN);tn.i269futmem;Extended southward from the interchange with TN 57 to a newly opened interchange with I-269 (Exit 2)
2024-01-05;(USA) Texas;I-20;tx.i020;Waypoint 138 moved from FM 715 (now labeled 137A) to TX 140/158.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be '137B' for FM 715 instead of '137A'? It's fine in the I-20 file. Just wrong here on the update entry.

@@ -7227,6 +7227,12 @@ date;region;route;root;description
2015-11-29;(USA) Tennessee;US 641;tn.us641;Extended southward from the former ending intersection with I-40 along TN 69 & TN 114 to a new southern terminus at US 64
2015-10-25;(USA) Tennessee;I-269;tn.i269;Route added
2015-10-25;(USA) Tennessee;I-269 Future (Memphis, TN);tn.i269futmem;Extended southward from the interchange with TN 57 to a newly opened interchange with I-269 (Exit 2)
2024-01-05;(USA) Texas;I-20;tx.i020;Waypoint 138 moved from FM 715 (now labeled 137A) to TX 140/158.
2024-01-05;(USA) Texas;I-40 BL (Amarillo);tx.i040blama;Waypoint TXLp335_W moved approx. 0.9 mi west from FM 2590.
2024-01-05;(USA) Texas;TX 158;tx.tx158;Waypoint I-20(138) moved from FM 715 (now labeled I-20(137A)) to TX 140/158.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yakra Same as the other comment. Should be 'I-20(137B)' instead of 'I-20(137A)'. (It's fine in TX-158's file, just the update entry needs to be fixed.)

@rickmastfan67
Copy link
Contributor

Ping @TXStormchaser @bejacob @jonfmorse @keithcavey @Markkos1992

Yakra meant 137B, not 137A. ;)

@TXStormchaser
Copy link

I guess... If that's how TXDOT wants to number the same exits 137-138, then that works...

yakra added a commit to yakra/HighwayData that referenced this pull request Jan 7, 2024
@yakra
Copy link
Contributor Author

yakra commented Jan 7, 2024

Woulda made more sense IMO if they'd left it as it was, but whatchagonnado.
#7142

@rickmastfan67
Copy link
Contributor

Isn't the first time a state did something stupid like this.

And it probably will not be the last.

jteresco added a commit that referenced this pull request Jan 7, 2024
eeffaann pushed a commit to eeffaann/HighwayData that referenced this pull request Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants