Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Bitmapped on January 16, 2023, 08:09:37 pm

Title: OH: OH 4 Rerouted in Dayton
Post by: Bitmapped on January 16, 2023, 08:09:37 pm
In 2021, OH 4 was rerouted in Dayton to move more onto the US 35 freeway. It now continues its concurrency with US 35 west to Gettysburg Avenue, where it then heads south to its original alignment at Germantown Street/Pike.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: Markkos1992 on January 16, 2023, 08:27:01 pm
I am very much happy that my OH 4 plans for my Columbus Meet Trip are east of I-75.   :D
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: mapcat on January 16, 2023, 08:38:11 pm
GMSV (September 2022) still has the signs on the former route. I'll make the adjustment once signage is changed.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: neroute2 on January 16, 2023, 08:40:12 pm
Signs from 2 months ago in GSV show that the intersection of Gettysburg and Germantown has not been updated, but signs intersecting the freeway at McGee have been. Is this change reflected in non-signage official stuff?
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: mapcat on January 16, 2023, 09:03:25 pm
Signs from 2 months ago in GSV show that the intersection of Gettysburg and Germantown has not been updated, but signs intersecting the freeway at McGee have been. Is this change reflected in non-signage official stuff?

Looks like SLDs have it on 35 now between Gettysburg and Germantown. https://github.com/TravelMapping/HighwayData/pull/6293
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: Markkos1992 on January 17, 2023, 05:35:41 pm
Looking at the pull request before being pulled, I think US35_W should have just been moved instead of creating a new US35 point considering that OH 4 is already getting an updates entry for the realignment anyway.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: mapcat on January 17, 2023, 07:36:03 pm
Looking at the pull request before being pulled, I think US35_W should have just been moved instead of creating a new US35 point considering that OH 4 is already getting an updates entry for the realignment anyway.

US35_W is in use and moving it to the new location might give a user the false impression that there's no need to update the file. I could call it US35_N if you don't like it without a suffix (35 was drafted S-N even though it's signed W-E). Or I could just delete it entirely and break some more lists than I already did by removing BroSt.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: Markkos1992 on January 17, 2023, 07:53:38 pm
Doing a quick search on Github, here is who is currently using US35_W:

Bitmapped (reported reroute, I expect to update the list file accordingly)
hoss6884 (updates fairly regularly)
afarina (last updated 3 weeks ago)
bhemphill (last updated April 24, 2022)
nezinscot (updates fairly regularly)
Ib3kii (updates fairly regularly)
froggie (last updated November 18, 2022)
charliezeb (updates fairly regularly)

So oddly enough, everyone here is a somewhat frequent updater (except for maybe bhemphill).  Moving the US35_W label is probably fine IMO.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: yakra on January 17, 2023, 10:33:37 pm
and break some more lists than I already did by removing BroSt.
BroSt is in use in only bhemphill.list & mahon881.list.
Adding it as an AltLabel for GetAve_S would map both of their travels correctly, and bhemphill.log would get an "Equivalent waypoint labels mark zero distance traveled in line: " notice.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: mapcat on January 17, 2023, 11:24:28 pm
and break some more lists than I already did by removing BroSt.
BroSt is in use in only bhemphill.list & mahon881.list.

How did you confirm that? I did a search yesterday and got several pages of .lists that included both OH4 and BroSt, most of which only said "showing top 2 matches", making me think there were probably more, and I didn't want to open 50-some .list files just to be sure.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: yakra on January 17, 2023, 11:57:29 pm
How did you confirm that? I did a search yesterday and got several pages of .lists that included both OH4 and BroSt, most of which only said "showing top 2 matches", making me think there were probably more, and I didn't want to open 50-some .list files just to be sure.
https://github.com/yakra/tmtools/blob/master/shell_scripts/whouses.sh
That's the script I used to identify .lists broken by the New England exit renumberings (https://github.com/TravelMapping/HighwayData/issues?q=label%3A%22exit+renumbering%22+is%3Aclosed).

Unfortunately, it doesn't work on noreaster, likely due to FreeBSD <-> Linux differences. :( Not inclined to investigate ATM.
Want to try it out on noreaster? First, in your home directory (in @mapcat's case. More generally, whatever the parent directory of HighwayData & UserData is), download it via:

curl https://raw.githubusercontent.com/yakra/tmtools/master/shell_scripts/whouses.sh > whouses.sh

Then set permissions to make it executable. You'll only need to do this once. (For whatever reason, running it via sh whouses.sh won't work properly, so we need to run it directly.)

chmod +x whouses.sh

Then run it like so (just don't try to open anything in Firefox ;)):

./whouses.sh oh.oh004 BroSt

You can also search for multiple labels at once:

./whouses.sh oh.oh004 GetAve McCSt BroSt US35_W

...though depending on your use case, you may or may not prefer to just search for one at a time.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: Jim on January 18, 2023, 07:14:45 am
https://github.com/yakra/tmtools/blob/master/shell_scripts/whouses.sh

This seems worthwhile to have in the main DataProcessing repository.
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: froggie on January 18, 2023, 08:49:30 am
froggie (last updated November 18, 2022)

I've been on 35 west of Dayton, so this change has zero impact to me.  I suspect I may not be the only one...
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: yakra on January 18, 2023, 09:01:26 am
I've been on 35 west of Dayton, so this change has zero impact to me.  I suspect I may not be the only one...
Zero impact on: afarina bhemphill Bitmapped charliezeb froggie hoss6884 Ib3kii

Moving US35_W to the current multiplex split would break only nezinscot.list.
He updates fairly regularly. Do with this info what thou wilt. :)
Title: Re: OH: OH 4 Rerouted in Dayton
Post by: mapcat on January 18, 2023, 04:40:03 pm
This seems worthwhile to have in the main DataProcessing repository.

Definitely agree. Thanks Eric!

I've been on 35 west of Dayton, so this change has zero impact to me.  I suspect I may not be the only one...
Zero impact on: afarina bhemphill Bitmapped charliezeb froggie hoss6884 Ib3kii

Moving US35_W to the current multiplex split would break only nezinscot.list.
He updates fairly regularly. Do with this info what thou wilt. :)

Okay, moving (and amending the updates entry). Thanks again.