-
Notifications
You must be signed in to change notification settings - Fork 82
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
[Check Improvement] MixedCaseNameCheck to support MixedCase Brands #540
Comments
@Bentleysb, @sayas01, @atiannicelli, please take a look. |
another examples where lowercase part of the name does not belong to the actual name: making them an upper case might confuse users. |
@Bentleysb, do we have false positive rate for this Check ? |
@vladlemberg, this check has always had problems with brand names. It has one of the higher FP rates at 17%, but much of that is skewed by a few countries. I don't think we want to totally drop checking for mixed case in the middle of words, but we may want to do so in certain cases. Perhaps we could just check for title casing on features tagged as shops or amenities? As for the non-brand name cases you mention ('Manhattan Bridge lower level', etc.) I could suggest that is exactly the kind of thing this check is looking for. If those are truly the names of those features then they should be title cased, but I suspect most should just be moved to the description or other tag. |
@Bentleysb, thanks for the respond. few more questions:
|
--Perhaps we could just check for title casing on features tagged as shops or amenities? |
@vladlemberg, It sounds like the check logic will need to be done first, or simultaneously to the autofix implementation. The |
@Bentleysb, could you assign this task to me ? |
@Bentleysb, to summarize:
It handled most common BrandNames. However, there are lots of legit BrandNames are still being flagged. I don't have a concrete solution here. |
@vladlemberg, that all looks good to me. As for adding French and Dutch prepositions, you can add that now if you like, but it is not essential for this update. Eventually we will need all languages if we want this to work everywhere, but that is expected to happen slowly. |
@Bentleysb, thanks for the clarification. One more question: I added "Rock-n-Roll" and "Rock 'n Roll" handling, however it brakes "Test-TesT" unit case, because I removed hyphen as a delimiter. What's your opinion ? |
@Bentleysb, sorry it brakes validNamePointHyphenTest: "Test-Test" |
or I can change pattern: |
Describe the bug
MixedCase Brands are not supported and being flagged.
Example:
FedEx, RadioShack, JCPenney etc..
Spanish and Italian "prepositions" are not supported.
Example:
del, de la.
To Reproduce
Run check against US data. Following names are being flagged:
https://www.openstreetmap.org/node/5269224921
https://www.openstreetmap.org/node/4354550152
https://www.openstreetmap.org/way/97720765
etc..
Expected behavior
do not flag legit mixed case brand names. and handle Spanish and Italian prepositions.
The text was updated successfully, but these errors were encountered: