Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: mikeandkristie on August 07, 2024, 07:57:28 pm

Title: OR: Unconnected Point on Concurrency
Post by: mikeandkristie on August 07, 2024, 07:57:28 pm

I noticed this when looking at our updates from visiting Oregon and Washington.  This would be in Astoria, where US 101 Business ties back into US 101 on the northern end.  For one short segment, the business route overlay with OR202.  But, OR202's point at US 101 does not actually join with it.  I copied the coordinates and there is a slight variation once you get to the 4th decimal place.

US101BusAst w/ US101 (Connects)  - Coords.: 46.182936°, -123.860743°
OR202 w/ US101 (Doesn't Connect) - Coords.: 46.182891°, -123.860807°

Mike

Title: Re: OR: Unconnected Point on Concurrency
Post by: Bickendan on August 09, 2024, 02:46:15 am

I'll need to make sure OR 202 matches both points on US 101B.

Title: Re: OR: Unconnected Point on Concurrency
Post by: Jim on August 09, 2024, 08:56:37 am

@Bickendan I can make this quick fix if you don't have time now.  Seems very clear what needs to happen.

Title: Re: OR: Unconnected Point on Concurrency
Post by: Bickendan on August 09, 2024, 07:39:14 pm

Go for it!

Title: Re: OR: Unconnected Point on Concurrency
Post by: Jim on August 09, 2024, 08:32:06 pm

https://github.com/TravelMapping/HighwayData/commit/ce0157b000b4c4a0474ef005b3de1d994f8efe60

Title: Re: OR: Unconnected Point on Concurrency
Post by: mikeandkristie on August 14, 2024, 07:55:09 pm

Thank you.

Mike