I’ve moved the US School Zone guidance from the Google Doc to the Wazeopedia.
1 Like
In section 4. General info. Exclude road types. Optional. Users entering the School Zone any segment that is “excluded” will not receive a School Zone alert. doesn’t read smoothly for me.
If it read as Users entering the School Zone where any segment that is “excluded” will not receive a School Zone alert. flows better for me.
1 Like
How about:
Exclude road types. Optional. Users entering the School Zone on any segment that is “excluded” will not receive a School Zone alert
Maybe: 
Exclude road types. Optional. Users entering the School Zone on any segment type that is “excluded” will not receive a School Zone alert
1 Like
Thanks for your feedback @jm6087 and @tenetienne.
I’ve posted a fix for the highlighted readability issue to the wiki:
Exclude road types. Optional. Users entering the School Zone on any road type that is “excluded” will not receive a School Zone alert
I think it should be entering “from any road type”
Do we have guidance on how to handle two intersecting school zones (for the same school) with different speed limits on the same road type?
Example: https://waze.com/en-US/editor?env=usa&lat=30.24819&lon=-92.01967&marker=true&zoomLevel=18&permanentHazards=337230
MLK SZSL is 20mph, while Patterson is 25mph.
I have it configured as overlapping polygons, which the staff sheet indicates is acceptable. I’m just not sure if the differing SLs will cause undesirable behavior. (In my mind, at worst, drivers may see a blip in the SL while they cross the intersection??)
Overlapping is fine. With grouping of notifications as its currently implemented, the user will get only one alert as they approach/enter the first polygon.
As for School Zone Speed Limits, we don’t know what will happen yet, as HQ hasn’t built it yet. But this is one of the common implementations of school zones, so I will assume/hope that HQ will consider it when developing the School Zone SL features.
1 Like