-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Validator for punctuation characters #234
Comments
Note that some of these characters are expected in street names:
A reasonably sophisticated text-to-speech engine can handle these punctuation characters well.
It makes sense to limit this check to street names. Business names can have a wider variety of punctuation (@ $ !). |
Thank you @dannykath, I merge the branch into master, now I am working to release the detection into to-fix. |
Working around those issues, I found some Telenav users are fixing those issues to in the highways: e.g: https://osmlab.github.io/osm-deep-history/#/way/206914585 , https://osmlab.github.io/osm-deep-history/#/way/8941557 @daniel-j-h, I found some issues which you could suggest to fix them. |
As mappers attempt to map both |
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
The text was updated successfully, but these errors were encountered: