| View previous topic :: View next topic |
| Author |
Message |
afarina
Joined: 15 Jul 2010
Posts: 71
|
 Posted: Sat Jul 19, 2014 4:04 pm Post subject: PA: PA51 concurrency broken |
 |
|
Good afternoon,
It appears the concurrency is broken between PA51 and PA65TrkMcK. The northernmost point seems to be the one just off by the last decimal.
Also, the shaping of PA51 in that area seems to be a bit off. It looks like CorRd_S and the hidden shaping point right after it got switched in order, creating a disjunction with the V-shaped roadway. What I guess I'm trying to say is that it seems like the shaping point furthest north/west of the two between CorRd_S and PA65Trk_S looks like it should actually be between I-79 and CorRd_S.
Thank you very much! Cheers. |
|
| Back to top |
  |
 |
Wadsteckel
Joined: 01 Oct 2011
Posts: 16
Location: Pittsburgh, PA, USA
|
| Posted: Fri Aug 01, 2014 2:24 pm Post subject: |
|
|
Hi afarina,
Not sure what the admins will say, but since I live very close to this (just off of PA65 south of I-79, in fact), I'll put in my $0.02.
From what I see on CHM, the concurrency listed is correct. PA65TrkMcK comes off of the McKees Rocks bridge and joins PA51 on Island Ave. They split to the northwest at Neville Ave, where PA65TrkMcK crosses over to Neville Island via Neville Rd, and PA51 continues straight onto Robinson Blvd. Hope this helps.
Regards,
-Ed S |
|
| Back to top |
|
|
afarina
Joined: 15 Jul 2010
Posts: 71
|
| Posted: Mon Aug 04, 2014 12:05 pm Post subject: |
|
|
Hello, Ed.
Yes, you are correct. That is where the routes are concurrent in truth. It is the HB that is not recognizing them as concurrent because one of the coordinates for a point is off by a slight decimal on the site.
Thanks. |
|
| Back to top |
|
|
rickmastfan67
Joined: 14 Jul 2008
Posts: 2031
Location: Pittsburgh, PA
|
| Posted: Tue Sep 29, 2015 8:43 pm Post subject: Re: PA: PA51 concurrency broken |
|
|
| afarina wrote: | Good afternoon,
It appears the concurrency is broken between PA51 and PA65TrkMcK. The northernmost point seems to be the one just off by the last decimal. |
Yeah, it seems to be .000008 off. Fixing.
| afarina wrote: | | Also, the shaping of PA51 in that area seems to be a bit off. It looks like CorRd_S and the hidden shaping point right after it got switched in order, creating a disjunction with the V-shaped roadway. What I guess I'm trying to say is that it seems like the shaping point furthest north/west of the two between CorRd_S and PA65Trk_S looks like it should actually be between I-79 and CorRd_S. |
This one has been fixed for awhile in the new TravelMapping DB. |
|
| Back to top |
 |
|
rickmastfan67
Joined: 14 Jul 2008
Posts: 2031
Location: Pittsburgh, PA
|
| Posted: Tue Sep 29, 2015 9:23 pm Post subject: Re: PA: PA51 concurrency broken |
|
|
| rickmastfan67 wrote: | | afarina wrote: | Good afternoon,
It appears the concurrency is broken between PA51 and PA65TrkMcK. The northernmost point seems to be the one just off by the last decimal. |
Yeah, it seems to be .000008 off. Fixing. |
Fix submitted.
https://github.com/TravelMapping/HighwayData/pull/115 |
|
| Back to top |
|
|
rickmastfan67
Joined: 14 Jul 2008
Posts: 2031
Location: Pittsburgh, PA
|
| Posted: Mon Oct 26, 2015 5:58 am Post subject: |
|
|
Fix is live.
<< Locked >> |
|
| Back to top |
|
|
|
