Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on September 24, 2024, 09:26:53 pm

Title: BC: BC-1 Business (Chase)
Post by: rickmastfan67 on September 24, 2024, 09:26:53 pm
With the reroute of BC-1 to the south of town onto a new 4-lane alignment, the 'southern' end of the Business route has changed locations, as the old JCT has been completely removed.

This would require a 'closed' point & a new point on both BC-1 & BC-1 Bus.

However, on the Business route, I would also include a 3rd point, @ Frontage/Chase (https://maps.app.goo.gl/PGV7PYL9ZQqa4NBV7), as the old route of BC-1 was using that up till sometime between Oct '21/Sept '22.
Title: Re: BC: BC-1 Business (Chase)
Post by: oscar on September 26, 2024, 02:23:21 am
I'm on the road right now, will address when I'm back home.
Title: Re: BC: BC-1 Business (Chase)
Post by: rickmastfan67 on December 25, 2024, 02:48:05 am
will address when I'm back home.

Are you home yet?  :P  lol!  Just messing with ya. ;)
Title: Re: BC: BC-1 Business (Chase)
Post by: oscar on February 19, 2025, 06:33:24 pm
Here are several pull requests:

https://github.com/TravelMapping/HighwayData/pull/8189/files
https://github.com/TravelMapping/HighwayData/pull/8190
https://github.com/TravelMapping/HighwayData/pull/8191
https://github.com/TravelMapping/HighwayData/pull/8193

PR #8189 includes two commits, per your suggestion in another topic that I combine commits to reduce the number of pull requests. But I got distracted in the middle of this project, and wasn't able to pick up where I left off, so my other commits are in separate pull requests 8190, 8191, and 8193. Too much hassle for me to fold together a small number of pull requests, and I'm not planning to try that again.

However, on the Business route, I would also include a 3rd point, @ Frontage/Chase (https://maps.app.goo.gl/PGV7PYL9ZQqa4NBV7), as the old route of BC-1 was using that up till sometime between Oct '21/Sept '22.

I don't understand this, though I think I've probably taken care of this in the above pull requests.
Title: Re: BC: BC-1 Business (Chase)
Post by: rickmastfan67 on February 19, 2025, 07:07:11 pm
I don't understand this, though I think I've probably taken care of this in the above pull requests.

You sorta did, but as a 'shaping' point (+X570732).

If you look @ the Esri WorldImagery layer, you can see the 'old' BC-1 route where it connects to the Business route.  That's where I was suggesting the extra point on the Business route so that people could at least claim that small segment of the Business route if they were on the OG BC-1 before the reroute there.

Here's the exact location:
+X570732 http://www.openstreetmap.org/?lat=50.800524&lon=-119.701442
Title: Re: BC: BC-1 Business (Chase)
Post by: oscar on February 19, 2025, 11:23:18 pm
I don't understand this, though I think I've probably taken care of this in the above pull requests.

You sorta did, but as a 'shaping' point (+X570732).

I just sent in a pull request to tweak and relabel +x570732 as FroRd.

I also fixed some Datacheck errors from that and other pull requests earlier today.