Permit Alphanumeric Prefix in RPP HN
App users can create RPPs with alphanumeric prefixes but WME allows neither the creation, nor editing of RPPs containing them.
Suggest at least allowing N, S, E, W prefixes on HN portion of an RPP to pass checks on save.
In Wisconsin, a large part of the state's addresses use alphanumeric HNs.
Other than the fact that 2/3 of the land mass in Wisconsin and much of northern Illinois have addresses in either a partial grid (e.g. W8743) or full grid (e.g. N37W8743) format, users can create their own RPPs with these, but editors cannot. Very frustrating telling a user that they must do it themselves, we can't help. (We do have an ugly hack though: https://wazeopedia.waze.com/wiki/USA/Wisconsin#Alphanumeric_House_Numbers)
For Point and Area Places, we cannot use the in WME either. But there we can log into the app and fix the address there. With RPPs, you much be at the location.
Yes, would be nice to have HNs work too, but understand more coding is needed to do that due to indexing/sequencing. So just hoping for at least RPPs to, especially where GMap addresses (fallback search) are unavailable or way off.
Cefin E Otero commented
It should allow any letter, allow HNs to start with a letter and allow hyphens as well.
For example: F14, E-66, I86A, 185DD, 199-A
Been asking for this for years. Hundreds of thousands of places can't have addresses entered because they start with a letter.
In addition, parts of Iowa have hyphenated HNs. For example, the primary HN might be 1248 each house on the street will have an additional number - 1248-1, 1248-2, 1248-3 etc. Here's a PL on an unnamed road with addresses from the closest street so RPPs are needed: https://waze.com/editor?env=usa&lat=42.40772&lon=-91.76387&zoom=6&segments=17360303,522819895