https://www.waze.com/editor/?env=usa&lon=-122.04059&lat=37.25295&layers=933&zoom=6&segments=79526173
Please unlock SR-9 to allow connection of Jacks Rd in its proper place. Hakone Gardens entrance was misnamed as Jacks Rd, the proper entrance to Jacks Rd was missing, connections that did not exist were present from Hakone to the incomplete Jacks Rd. I have completely changed Jacks Rd, removed the Jacks Rd name from Haone’s entrance, moved HNs to the new alignment of Jacks Rd. Just need to connect it to SR-9. I don’t have all of the missing HNs yet - will add them as I can research them. I am R2.
I unlocked several segments of SR-9. Glad you cleaned up the area, I really enjoyed a recent visit to Hakone Gardens. I’d recommend the entire driveway for the gardens be set to PLR for uniformity’s sake, even though the actual parking lot is only at the end. Especially since the sign for Hakone Gardens is right out on SR-9, so drivers understand they are turning into the property and not onto a city street.
Uh-oh, does that mean my assignment is to find what else you saw and clean that up too? :o I took care of Hakone’s driveway, connected Jacks, shortened Pamela and realigned/simplified a stretch of SR-9. What am I missing?
What does your research say about the little private road adjacent to the PLRs to Hakone Gardens?
The PLRs to Hakone look good. As I was there not long ago and recall the way out of the parking lot, I am uncertain drivers need the turn instruction to get out (also given the road markings visible in the aerials). I’d favor a seamless exit here…
Also, the Point Place for Hakone gives a puzzling address. Is it correct?
Finally…this is all a bit odd, because I could swear I looked at this area after I used Waze to get to Hakone. I am almost positive the parking-lot roads were already complete there. So it seems likely something happened…when we’re both satisfied it might be best for me to lock the new setup.
The “private road” doesn’t exist. Removed.
The PLR to Hakone was previously named Jacks Rd, all the way from SR-9 to the end of the parking lot, and the real Jacks road was shown as a spur off of it (at the point where the downhill one-way section rejoined the driveway). I added the Point Place from the app (hence the picture) and didn’t update the address it automatically assigned. Updated now, along with the phone number and website (and the HN on Big Basin Way is there now as well).
I had added the one-way sections to reflect reality, and because I was afraid drivers exiting on the downhill one-way loop would snap to the end of Jacks Rd before they got back to the two-way part of the driveway - they deviate so far from the uphill part of the road that they are closer to Jacks Rd. I didn’t think about the turn instructions they would get. Simplified.
Since a piece of the real Jacks Rd was there, but without its connection to SR-9, I just disconnected it from the Hakone driveway, added the connection to SR-9, corrected the alignment to match reality (based on my drive trace), and moved the HNs off the Hakone driveway to the remaining Jacks Rd (and added a couple of HNs). So your memory of the Hakone driveway being there is correct - it was just misnamed. I don’t think anyone else messed with it between your trip and my edits.
Good work! And I must apologize, I wasn’t clear about the split-PLR setup. I did like it! It was only the turn instruction for exiting visitors that I felt may have been unnecessary.
Would you like to put the divided PLR back? As long as the merge for exiting visitors gives no instruction I’d be completely in favor of it. Sorry not to have been clear.
OK, I think I have the exit angles flat enough to avoid turn instructions. I missed the fact that the pavement arrows don’t allow for an exiting driver to turn left and go back into the park. If you want to lock any of this up you can, but I don’t think it’s necessary. This area has apparently been messed up for quite a while without causing any grief.
As long as the angle is less than 40°(the threshold is actually closer to 45° but it’s best practice not to make the junction too close to the threshold) and there is no competing “best continuation” also within that angle, there won’t be a turn instruction. So making angles very tight in simple situations is something you do for U-turns at bowtie-type intersections or for cosmetic reasons, both of which are of course fine.
I took the liberty of tweaking things a tiny bit more to conform with the road appearance as well as with the cloud of GPS points, and have locked them at 3.
One thing you might be curious about – I shifted the section of the PLR in the actual parking lot over to the west. It would have been exactly perfect where it was, but I was concerned about routing people to Hakone who were actually headed for 20915 Hidden View Lane (it would depend on the exact placement of the Google pin for that address, I didn’t check that, I just did it for best practice since Google pins are usually in the middle of the building). On top of that, as a sort of belt-and-suspenders approach, I added the House Number for 20915 Hidden View based on what was visible in SV imagery.
This looks done to me. Good work, I’m glad you cleaned up Jacks Rd, that must have been a mess!
Strangely. the Google pin for 20915 is actually on the other side of the road. And Waze has no house numbers for any other addresses on Hidden View. I guess I need to make a trip down that road next week and see what’s what.