Is there something I need to do to have waze differentiate between “N” & “North” when editing roads?
The client frequently calls “N st” “North Street” erroneously…
I don’t know if “S st” translates to “South street”, “E st” to “East street”, etc…
If it’s stuck at N->North; I propose the following:
a) Change the model for naming abbreviations to use a period after each abbreviation, eg: “N.” as “North”.
b) Have waze push a DB change to rename current abbreviations “N”, etc to “N.”, etc.
This actually brings me to my second question: Is there a list on the wiki of what gets verbally translated at the client side to what?
N->North
Bus->Business
rd->Road
…
And my final question: How can one get a naming convention added?
Co->County
CR->County Road
Prky->Parkway (This one may actually already exist)
PS: I tried searching the forums for this, but the search function suxors…
No it was ANY use at all. I ran into this old Cartouche bug with landmarks often. You’d put something in like this:
World’s Fair Park
Which would then become:
World/'s Fair Park
Then if you edit ANYTHING, even geometry, it would then become:
World///'s Fair Park
And so on.
It was a problem where things were getting escaped for the database, but then not sanitized going back to the client. So the single quote and any slashes would each keep getting escaped over and over again.
All that said, I am not sure if it is still a problem in the old editor. I don’t think it is a problem in the new editor.