-
Notifications
You must be signed in to change notification settings - Fork 15
Common compare function for checking feature names #133
Comments
A couple of compare functions work with feature names. Ex: We should 👀 if there are opportunities to merge them into this common compare function. |
From @nikhilprabhakar's post here: #110 (comment)
User Should the name compare function do this check as well? |
Changing the order of words is an interesting scenario. Ex: The name of the feature was modified from |
Minor name modifications can be ignored for a while. Ex: The features name was modified from
The name was modified from |
There are times when the case of the name (uppercase / lowercase) does not matter much. We can ignore these for a while. Ex: The name was modified from |
Thank you for your feedback @bsrinivasa, 😃 |
For the first iteration of this compare function, let's do the following checks:
cc: @amishas157 |
Everyday a lot of features get names and many features names gets deleted. Found an edit where the feature tag and Examples : This kind of name changes are 100% incorrect and we need to flag it as part of our compare function. The name combination can look like :
Would like some suggestions on this. |
Adding names and name translations happen pretty often on OpenStreetMap. Yay!!! Quite of few compare functions currently flag any edits to features that satisfy a particular criteria. Ex:
Edited a major lake
flags any edits to features in the list of major lakes.Edited an osm landmark
flags any edits to a custom list of landmarks on OpenStreetMap.Edited a name tag
flags any edits to feature name.Edited an old monument
flags any edit to monuments on OpenStreetMap.For a large majority of cases, the new names or translations added are 👍
How about we move the name checks to a common
profanity compare function
and flag any other kind of edit from the ^ compare functions? Theprofanity compare function
in turn will focus just on identifying problems with values ofname:*
.cc: @amishas157 @geohacker
The text was updated successfully, but these errors were encountered: