Parking Lot Roads - Differentiate Aisles & Roads
It would be nice to have a way of setting PLRs to be able to use speed data (versus a set speed) while having the same penalty settings (i.e., the road has no penalty between the two PLR settings). This would be useful in large parking lots area such as sporting venues and malls, where set speed is fine for aisles and minor roads but speed data would be useful for finding the fastest entrance/exit on it's higher volume roads. With the set PLR speed, you are almost always getting the shortest route of PLRs, even if that lot exit is much busier and slower (or if say the right turn lane out the lot is fast but a left turn is slower than using a different lot exit).
This could be a checkbox on PLR segment settings, or potentially a new road type (with the current one named "Parking Lot Aisle" and the new speed data type taking on the "Parking Lot Road" name).
Can you please share some more details and examples for this issue which you would like to address in this suggestion?
This will help us to better understand what will be the best solution.
Very good point, Bob, but I believe the point would be to create a new category of road, like a "Parking Lot Collector." It would not route drivers through it from one public road to another, but it would have a lower penalty than regular PLRs to get people around such huge parking lots more efficiently. The roads that are now PR in your example would be the Parking Lot Collector Roads.
The PL Collectors could also get traffic-jam detection when comparing entrances/exits for bigger parking lots.
Bob Cunningham commented
Hi! North Shore Mall in Peabody MA is an example. Marking these as Local Street would allow "cutting through" the mall property which is undesired. We have solved the issue by marking these as Private Roads and it functions fantastic - but technically does not meet the criteria for Private Road.
There is at least one segment there which is marked as a Private Road but might cause an issue if someone parks there (would detect a traffic jam).
Here are some real-world examples.
- Preferred route (using road): https://waze.com/editor?env=usa&lat=33.92573&lon=-84.33952&zoom=7&segments=513842615,513842616,513842618,513842623,513842624,513842628,513842629,507788537
- Non-preferred route (using aisle): https://waze.com/editor?env=usa&lat=33.92573&lon=-84.33952&zoom=7&segments=507788537,513842613,513842612,513842615
- Preferred route (using road): https://waze.com/editor?env=usa&lat=33.92559&lon=-84.33890&zoom=7&segments=513842623,513842618,78153223,513842640,513842645,513842646,513842625,513842633
- Non-preferred route (using aisle): https://waze.com/editor?env=usa&lat=33.92559&lon=-84.33890&zoom=7&segments=513842623,513842617,513842625,513842633
The problem with aisles is that each parking slot is like a small intersection where cars can come out, while "roads" move faster and are less risky to take (even if it sometimes looks like there are more intersections - with aisles - on those roads).
A solution could be a new road type, but that may be confusing for novice editors, or allowing Routing preference (Unfavored/Neutral/Preferred) on PLRs. This routing preference would carry a different default speed (i.e. 10/20/30 km/h), vs. the one default speed of 20km/h.
Here is an example: https://waze.com/en-US/editor?env=usa&lat=42.71186&lon=-73.81114&marker=true&zoom=5&segments=65278838,75894143
In this situation, Waze wants a user to turn left out of the parking lot road (sometimes a difficult turn) and use Wolf Rd to head to the second segment. This is a 0.8 mile route with 2 traffic lights on a heavy-traffic road.
In reality, turning right (rarely has a wait) and taking a route through the PLRs to the roundabout is quicker at the PLR's real-world speed limit (and likely even faster when considering real-time speeds), has only one stop sign, and is 0.6 miles (0.2 miles shorter).
We would not want to use a local street here, as that could potentially cause shortcutting through the mall's property between the roundabout and Wolf Rd (and vice versa). A private road would also not be appropriate, as that will cause a double penalty since another road type transition is added. These outer roads have no parking spots, but are set as PLR because that PLR penalty is needed - it would be great to have a way to tell those segments to use real-time data over a set speed (especially when the PLR set speed here is less than half the speed of the speed limit) while keeping the road type penalty. This also has the bonus suppressing traffic displays, which we don't really need to see once already on the mall property.
The principle is to tier the parking lot roads like we do with, say, Local Street and Primary Street. In large parking lots, there are roads within that are more for circulation and less for actually parking -- the request here is to be able to identify the two types separately and for the routing engine to give a preference on the higher class, perhaps even use a non-fixed speed data process.