usapr: Puerto Rico Territorial Highways

[mapcat]

PR102: So I'm assuming that this does not actually connect to PR120 or 121, right?

As far as I can tell, yes. The Manual de Descripción de Rutas says that PR102 ends at the intersection of PR120 & PR121, which it describes as Quinoñes & 65 de Infantería, but the descriptions of 120 & 121 show that they end a few blocks away from that intersection. There's no imagery, so I'm assuming that the PR102 description just hasn't been updated to reflect some relinquishments in the other routes.

[compdude787]

Okay, I am finally continuing the review.

PR110: CllAHer -> CllAmeHer (note that there's an accent mark over the "e" in "Ame" according to OSM, but I'd omit that because it'd be fairly difficult for people to type the e with the accent mark). Also, is there a reason why the northern end point is just a hundred feet west of the CliRd waypoint? GMSV doesn't show an End sign there, and I have to wonder if that's the right place to put the End waypoint.
PR110RAgu: Signage for this one is a bit weird. First there's a sign here that says "INT [intersection?] 4010", then a bit further up, you see another sign that says 110R is to the left, and then at the beginning of 110R there's a reassurance shield that indicates that the route number is actually PR 4010! So not sure if this route should be changed to PR 4010 or not. (note that all the street view in the area has the same May 2016 date)
PR110RMoc: fine
PR111: PR4128 appears to be unsigned.


That's all for now.

[mapcat]

Thanks for catching 4010. The documentation showed that it had changed, but I only saw the 110R sign at the intersection. The northern end of 110 is listed in the manual and the log as the east gate of the airport, and satellite imagery shows that the gate is just west of that intersection, so that's where I thought it should go. Similar situation with 107 coming into the airport from the SW, although it looks like I placed that endpoint short of the gate. I'll fix 107 in tonight's pull.

[compdude787]

I am now continuing my review.

PR112: fine
PR113: fine
PR114: fine
PR115: fine
PR116: fine
PR117: fine
PR118: fine

[yakra]

Suggest adding a point to PR181 to complement PR876@ToPR181

[mapcat]

Suggest adding a point to PR181 to complement PR876@ToPR181

Seems like a good idea. I'll add that this weekend.

[mapcat]

https://github.com/TravelMapping/HighwayData/pull/2342

[mapcat]

Evin (compdude787) told me that he's unable to continue with the peer review, so if anyone would like to help out, I'd appreciate it. He took care of most of the long routes.

I have one DTOP map (sent my other copy to him) so anyone who wants to look at it can PM me and I'll send photos of it. The online version still doesn't work.

[yakra]

pr.pr7025;+X145358;;;HIDDEN_TERMINUS;
was a good test case while I was working on the graph generation-based datachecks, but I'm done with it now.

[Markkos1992]

Evin (compdude787) told me that he's unable to continue with the peer review, so if anyone would like to help out, I'd appreciate it. He took care of most of the long routes.

I have one DTOP map (sent my other copy to him) so anyone who wants to look at it can PM me and I'll send photos of it. The online version still doesn't work.

I'll go ahead and take over the Puerto Rico peer review as part of my spamming you over KY/OH minor stuff.  You can send me photos of the DTOP map via email. 

[mapcat]

Thank you! I will get that to you later this week.

[Markkos1992]

PR 119:  PR 4119 shows up on OSM as PR 485.  Otherwise no issues as I can tell best using OSM and the Here Maps.  I am slightly confused about the area around PR 124, but I think it is correct.  Also I normally would have mentioned changing the shaping point southwest of PR 486 to a visible point, but there is no road name.

[mapcat]

PR 119:  PR 4119 shows up on OSM as PR 485.  Otherwise no issues as I can tell best using OSM and the Here Maps. 

According to the info in the spreadsheet I sent you, there's only one 485, but the route I mapped matches the description of 4119. The document is from 2015, so maybe there has been a change, but unfortunately there's no GMSV available at that intersection (get used to that). I would not trust OSM over other sources, or even my own intuition here honestly.

4-digit routes that *don't* start with a double digit are relatively new, and often renumbered spurs (ramales). So a number like 4119 is often an indication that the route used to be a spur of 119 (ie 119R) in the 4xxx sector. Not saying that happened here, but you'll notice it in other places, and if the numbers don't match, that's one reason.

EDIT 1: The online map is working now: https://dtop.pr.gov/mapa-de-regionales/

Looks like they changed that road to 485. I will update it.

EDIT 2: Just noticed that the online map is (c) 2011. It looks like it's not been updated recently, since PR 66 is shown as under construction east of 188. So maybe it's not going to be all that helpful after all.

[Markkos1992]

PR 120:  Assuming that this and PA 121 do not reach PR 102. 

1.  A point labeled "ToPR357" would be useful at the "roundabout" north of PR105_E.  Same for "ToPR120" on PR 357 here.
2.  OSM and the Here Maps disagree on the routing north of the point I just mentioned.

PR 121:  I would change PR2 to CllMarVega, but this may be better off left as-is. No other concerns.

PR 122 (Lajas and San German): Fine.

PR 123:
1.  Add a point at Calle Puerto Viejo (CllPueVie).
2.  It seems to me that the one-way split of PR 123 continues all the way to PR 2R.  It is practically impossible to follow northbound through Downtown Ponce.
3.  The Ponce inset shows PR 500 extended to PR 123 even though the spreadsheet does not.  (maybe a "ToPR500" or "PR500Con" since I do not see a road name here)
4.  Have there been any updates on PR 9?
5.  I recommend changing PR501_S to PR501 and PR501_N to PR501Pon.  (looking at the route, the latter may be too long)
6.  Is PR 516 at the right location?
7.  Are you sure that there are one-way sections of PR 123 and PR 5516 at PA 521? (Maybe the point here should be relocated??)
8.  Is PR 6111 truly concurrent with PR 123?
9.  I recommend points on PR 10 and PR 123 at the connector north of PR 111.  Note to make sure that PR 123 does not cross PR 10 here in Mapview.
10.  I recommend a shaping point at the turn after PR 6613 to help keep PR 123 for being put on top of it.
 
PR 124: Fine.

PR 125:  Fine.  However, I also saw signs for PR 111R at the eastern end of this route.

PR 127:  I am not sure that PR 398 makes it to PR 127. No other issues.

PR 128:  Should PR 4431 mostly instead be PR 431? 

I also do not like CamGar being there, but there is nothing else viable here.

PR 129: Maybe add a point at AveCollTos near PR 2.  Maybe also add a point on PR 2 at AveJoseCed.  Otherwise no other comments.

PR 130:  OSM and the Here Maps show a PR 130R.  Obviously I cannot prove its existence.  No further comments.

PR 131:  The labels are fine.  I am unsure how you determined where the south end is.

PR 132: 
1.  Is there a segment of PR 383 that should connect to this road?  (or is this PR 3384?)
2.  Is CllNMain correct?

PR 133:  Fine.

PR 134:  Fine.

PR 135:  Fine.

PR 136 (Guayanilla(N)):  Fine.

PR 136 (Guayanilla(S)):  Fine.

PR 137: 
1.  I think that this route should be flipped.
2.  I would change PR155_A to PR155_N and PR155_B to PR155_S.

PR 138:  It looks like the south end of PR 138 is at PR 14/PR 153.  The part from PR 153 back to PR 14 is now PR 238.

PR 139:
1.  I do not see a road at CamLaRob.
2.  Replace the shaping point after CamLosRob with a visible point at Camilo Tres Palos Ramali.
PR 139R:  Fine.

PR 140:
1.  Is PR528 at the right location?
2.  Are you able to clarify whether the future hidden points for PR routes are still a thing?
3.  A shaping point is needed west of PR141 as it sneaks outside of tolerance.

PR 141:
1.  Is the PR144 point at the southern end at the right location?
2.  Is LomaZar a correct label?

PR 142:  This one looks fine.

PR 143:  Should PR511 instead be PR5011?

PR 144:  No other issues beyond Number 1 under PR 141.

PR 145:  Fine.

PR 146:  Fine.

PR 148:  The route shown is fine, but the spreadsheet seems to indicate that another section exists along PR 156 somewhere.

PR 149: 
1.  The PR149R labels should be edited to be for PR5149.  Also does PR 149 actually intersect PR 589 at PR149R/589?
2.  The northern segment of PR 668 is signed as PR 6668 (at west intersection with PR 149, at east intersection with PR 149).

PR 150: 
1.  Maybe add a point between PR5561 and PR557 for shaping purposes.
2.  It looks like PR 5150 should instead be a branch of PR 553.

PR 151:  Fine.

PR 152:
1.  Is the south end of PR 810 at the right location?
2.  Is CamMonGon a continuous route?  I am unsure if it is a useful visible point.
PR 152R:  Fine.

PR 153: 
1.  Google Maps shows the south end of this route as a one-way split.
2.  Does PR 545 still connect just northwest of PR 153?
3.  PR138_E should be PR238. (see PR 138)

PR 154:  Fine.

PR 155:
1.  Is the south end of this route at the right point?  There seems to maybe be a one-way split around PR 14.
2.  Maybe add another shaping point around the Perchas curve.  I added one at the peak that got near tolerance that added over .3 miles to the route.
3.  I would change PR137_D to PR137_S and PR137_E to PR137_N.

PR 156:
1.  Maybe add a shaping point between PR 569 and PR 7772.
2.  Should PA774_W be PA774Bar and PA774_E be just PR774?
3.  The PR7156_E intersection is signed as PR 777.

PR 157:  Fine.

PR 159:
1.  Should PR6617_W be PR6617Mor and PR6617_E be PR6617?  Also on PR6617Mor, the "M" in the name should be capitalized with PR159_W becoming PR159.
2.  Neither the spreadsheet nor the map show PR 817.

PR 160:  Fine.

PR 161:  Fine.

PR 162: 
1.  I think that the PR 14 labels should be switched.
2.  Is the north end at PR 156 correct?

PR 163:  CllEduRub should be AveEduRub.

PR 164:  A "ToPR164" should be added on PR 5 at the "ToPR5" connector.  Otherwise fine.

PR 165: 
1.  It looks like PR8861 needs to be added.
2.  Should BlvdLev be PR868?  I guess not because I did not see any signage.
3.  I would ignore the exit numbers here.  No visual evidence except for 15A (and that one is completely by itself at PR22(22).
PR 165R:  Is there a concurrency with PR 861?

PR 166:  Fine.

(Quick Note on PR 53:)  6a should be 6A.  (I think this also affects I-PR3.)

PR 167:
1.  The spreadsheet indicates that PR 7780 intersects this route unlike that map.  Even GSV sort of indicates a connection.
2.  This photo indicates that the southern PR 826 could be PR 8126.
3.  Is PR 855 completely one-way?

PR 168: Fine.

PR 169:  Is there anything related to Exp834 that I should be aware of for later?  I do not see anything showing this as actual PR 834.  Otherwise fine.

PR 170:  Is CllPer a correct label? (maybe should also be relocated)

PR 171: 
1.  Should "FutPR731" be made a visible point in the area?
2.  The shaping point north of PR733 could be made into a visible point...

PR 172:
1. Is there actually a concurrency with PR 173?  The HERE Maps show PR 173 as one way.
2.  The CllFCHad label seems like is it incorrect (should be CllAntBar).

PR 173:
1.  See number 1 under PR 172.
2.  GSV seems to indicate there is a loop around PR 728.
3.  CllLop should be CamLop I think.

PR 174:
1.  CllSie does not seem to be correct.
2.  PR 832 is not signed looking at GSV.  I would link it if I could prove this from PR 833.

PR 175:  Fine.

PR 176:  Fine.

PR 177:  A point should be added at AveNor due to an interchange there.

PR 178:  PR3_W should be PR3.  (On PR 3, PR178_W should be just PR178.)

PR 179:  The shaping point north of PR748 should be replaced with a nearby visible point.

PR 180:  The shaping point between PR3 and PR701 should be replaced by a visible point at Calle J(OSM)/Calle Villa Sol (HERE Maps).

PR 181: 
1.  Are the south end at PR 3 and the point at PR 757 in the right location?
2.  It looks like the PR980 point needs to be moved south a bit.
3.  I would change PR876_S to PR850/876.
4.  AveParkGar looks like it should be PR877_N making PR877 PR877_S.

PR 182:  Fine.

PR 183: It looks like a point should be added at what may be (or currently is) PR 34.

PR 184:  Is PR 7184 missing or is there just a graph connection missing there?

PR 185:  Fine, though I am not 100% confident on the existence of PR 9185.

PR 186:  PR 9966 seems to be signed as PR 966 for some reason.

PR 187:  Fine.
PR 187R:  Fine.

PR 188:  Fine.

PR 189:  Should PR 9189 be added?  It is signed.

PR 190:  Should there be points on AveMon (or AvePasGig) around PR26(13)?

PR 191:  What led to this route being split in two?  Otherwise seems fine as I think it goes north of PR 955.

PR 192:  Fine.

PR 193:  I recommend changing PR3_B to PR3_W and PR3_C to PR3_E (presuming the Frontage Rd part is actually not part of PR 193).

PR 194:  It looks like PR3_S should become PR3 and recentered onto the nearby roundabout.  Also is this route concurrent with PR 195?

PR 195:   Is CllPla correct and at the right location?  Also is this route concurrent with PR 194?

PR 196:  PR 34 is shown as signed heading east from PR 1.

PR 198:  PR 204 seems to be signed as PR 9939 here.  PR 9939 is in the correct spot though.  Maybe this is an error.

PR 199 (San Juan):  It looks like a point is needed at PR 837.  ToPR837 should be AveSanIgn.
PR 199 (Bayamon): Fine.

PR 200: 
1.  Is the western end correct?
2.  Should PR201_E be just PR201? 
PR 200R:
1. CLLPinPet should be CllPinPet.
2.  Does this road really end at the dock?

PR 201:  Should PR200_E be just PR200?

[Markkos1992]

PR 203:  Fine, presuming that SenGur is the only usable label there.

PR 204:  See PR 198.

PR 205:  Does not seem to be posted from PR 31 or PR 53 (signed as "PR 31").  I am unsure if this should be included.

PR 206:  Fine.

PR 212:  This is signed as part of PR 4494.

PR 250: 
1. Should DewDock be CulFry?
2.  Is it worth replacing the hidden shaping point with a visible point?

PR 251:  Fine.  Google Maps shows a PR 252 that I am pretty sure does not exist.