1ec5
commented
7 years ago Note that some of these characters are expected in street names:
'– e.g., “O’Flaherty Street”();– common in bilingual areas,– e.g., “Martin Luther King, Junior Drive”:– Finnish and Swedish-– e.g., “Cincinnati-Dayton Road”.– e.g., “8.Dezember-Straße”
A reasonably sophisticated text-to-speech engine can handle these punctuation characters well.
If we can't do this on the name tag on all ways can we at least check it on a subset of all ways e.g. highways, ramps, etc. and then check specific tags such as name, ref, destination - basically all tags used for generating guidance instructions from?
It makes sense to limit this check to street names. Business names can have a wider variety of punctuation (@ $ !).
dannykath
Rub21
Can we write a validator for punctuation tokens in tags? I don't know how high the false positive rate would be but how often do punctuation characters such as
occur.
If we can't do this on the name tag on all ways can we at least check it on a subset of all ways e.g. highways, ramps, etc. and then check specific tags such as name, ref, destination - basically all tags used for generating guidance instructions from?
What I'm mostly concerned about is routing engines announcing weird punctuation characters in guidance instructions to the user.
cc @srividyacb