Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on April 21, 2024, 02:30:38 am

Title: BC: BC-1 issues
Post by: rickmastfan67 on April 21, 2024, 02:30:38 am
NEW -> 38 (https://maps.app.goo.gl/1TMYvWTbKFvFyCEr6) - While it's a 'Bus only' exit, you never know if somebody would need it if they traveled on said bus that uses it.
*59 -> 59 (https://maps.app.goo.gl/gj2xeEZvQPn5styo6) (not a closed interchange)
MarPraRd -> 411 (https://maps.app.goo.gl/K11ZUNpZuRi8rVr7A)
NEW -> CedDr (https://maps.app.goo.gl/kTKViucLr3VqsrKG6) (between +x133 & BalRd)
+x136 -> FordRd (https://maps.app.goo.gl/giJkoKyZqom2vxxx7)
SalRivRd -> 478 (https://maps.app.goo.gl/eotry6rvqmv1mmAQ8) & needs recentered, as it's well off the interchange there
GolViewRd -> 780 (https://maps.app.goo.gl/Fest8Z4qRussgeEE7)
+x243 -> needs recentered back on the highway, as it's pretty far north of it.
Title: Re: BC: BC-1 issues
Post by: oscar on June 27, 2024, 08:49:44 pm
Forgot about this -- just a reminder that I need to take care of this when I return from a short road trip.
Title: Re: BC: BC-1 issues
Post by: rickmastfan67 on June 28, 2024, 03:36:43 am
Forgot about this -- just a reminder that I need to take care of this when I return from a short road trip.

Good thing you didn't touch this tonight.  Caught one additional newly posted exit number.
Title: Re: BC: BC-1 issues
Post by: oscar on August 31, 2024, 05:21:54 pm
Changes made to both bc.bc001 and concurrent bc.tchmai files.

https://github.com/TravelMapping/HighwayData/pull/7671
https://github.com/TravelMapping/HighwayData/pull/7672

Good thing you didn't touch this tonight.  Caught one additional newly posted exit number.

I added two more points for new interchanges/GSVs: 428 in Chase, WhiLakeRd in Carlin. Hope one of those matches the one you found.
Title: Re: BC: BC-1 issues
Post by: rickmastfan67 on August 31, 2024, 08:54:11 pm
I added two more points for new interchanges/GSVs: 428 in Chase, WhiLakeRd in Carlin. Hope one of those matches the one you found.

No, didn't know about 428.  Didn't have any proof on that one for exit number or being open yet.  Hence why I didn't mention it to play it safe, as people have been know to jump the gun on OSM and put the wrong exit number.

What I had caught, was the number for '478', as when I made the original post, there was no GSV there due to the slight realignment.

==

Anyways, I 'did' just find another exit that should be added. LOL! (Sorry.)

21stSt in Salmon Arm
https://maps.app.goo.gl/Uks4WqSSrX9bRmce7

Didn't realize it was grade separated originally.
Title: Re: BC: BC-1 issues
Post by: Bickendan on September 01, 2024, 03:07:41 am
I like how the map shows BC 1 as a dual carriageway there, but GMSV shows it as a Super 4.
Title: Re: BC: BC-1 issues
Post by: oscar on September 02, 2024, 04:40:15 pm
Anyways, I 'did' just find another exit that should be added. LOL! (Sorry.)

21stSt in Salmon Arm
https://maps.app.goo.gl/Uks4WqSSrX9bRmce7

Didn't realize it was grade separated originally.

https://github.com/TravelMapping/HighwayData/pull/7675
https://github.com/TravelMapping/HighwayData/pull/7676
Title: Re: BC: BC-1 issues
Post by: rickmastfan67 on September 24, 2024, 02:34:14 am
I like how the map shows BC 1 as a dual carriageway there, but GMSV shows it as a Super 4.

Google loves doing that.  Even when there's a center turn lane, they'll 'split' the highway when it shouldn't be.  One thing I've always hated about them.

Anyways, with everything fixed that I've mentioned here in this thread, I'll go ahead and mark it as solved. :)