Skip to content
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

Pub names #4926

Closed
UKChris-osm opened this issue Feb 24, 2021 · 1 comment
Closed

Pub names #4926

UKChris-osm opened this issue Feb 24, 2021 · 1 comment
Labels
question Not Actionable - just a question about something

Comments

@UKChris-osm
Copy link
Collaborator

If I have this correct, the NSI started with just names, and no brand usage?

pub.json seems to have a great deal of British Pub names currently in it, such as Cross Keys, Cricketers, Red Lion, Victoria, etc.

This isn't unexpected, as I'm sure the planet scan picked these up, but as they are just names, and not necessarily brands, what would be the best way to handle these?

Remove the "brand" tag from each and keep the name, or filter them all out? The reason I ask is because I see no reason why they shouldn't be suggested as a name if someone starts typing "The Red" and is suggested "The Red Lion", but would this work if no brand / operator data exists either?

@UKChris-osm UKChris-osm added the question Not Actionable - just a question about something label Feb 24, 2021
@bhousel
Copy link
Member

bhousel commented Feb 26, 2021

Good questions! I changed some of this a few days ago (see #4906 and #4924) and need to update the contributing guide.

If I have this correct, the NSI started with just names, and no brand usage?
pub.json seems to have a great deal of British Pub names currently in it, such as Cross Keys, Cricketers, Red Lion, Victoria, etc.

Yes the scripts originally just looked in the name tag, but we can collect and compare other tags now.
Also we had lists of which k/v pairs we would collect, and amenity/pub was probably not in the original list.

This isn't unexpected, as I'm sure the planet scan picked these up, but as they are just names, and not necessarily brands, what would be the best way to handle these?

Now we can attach properties to categories (#4906), I've added per-category exclude lists, so amenity/pub can be like fast food or restaurant categories..

in data/brands/amenity/fast_food.json we have this now:

    "exclude": {
      "generic": [
        "^(bistro|buffet|büfé|fast food|food court|kantine|frituur|imbiss|kiosk|lanchonete)$",
        "^(pizz(eri)?a|fish (and|&) chips|tacos)$",
        "^(бистро|пиццерия|столовая|ша(ве|у)рма)$",
        "^caf[eé](t[eé]r[ií]a)?$",
        "^d[oö]ner( kebab)?$",
        "^fri[tz]erie$",
        "^istanbul( kebab)?$",
        "^kebab( house)?$",
        "^snack(s)?( bar)?$",
        "^sushi\\s?(bar|house)?$",
        "^ラーメン(屋|店)?$"
      ],
      "named": [
        "^(ali baba|antalya|asia[ -](bistro|imbiss|wok)|(berlin|city) döner|city (grill|pizza)|kebabai|kfc/taco bell)$",
        "^(marmaris|pizza (house|time))$"
      ]
    }

These exclude lists (#4924) are lists of regular expressions.

They work like this:

  • generic - a generic word that is probably not really a name. For these, iD should warn the user "Hey don't put 'food court' in the name tag".
  • named - a real name like "Kebabai" or "China Wok" that is just common, but not a brand. For these, iD should just let it be. We don't want this in NSI, but we don't want to warn users about it either.

So for pubs with common names that aren't brands, we can add them to the "named" section to exclude them from the index.

The reason I ask is because I see no reason why they shouldn't be suggested as a name if someone starts typing "The Red" and is suggested "The Red Lion", but would this work if no brand / operator data exists either?

This is one of those things that sounds like a good idea, and iD has had it for a while, but it is causing a lot of problems, so I'm trying to move away from autocompleting names:
openstreetmap/iD#8304
openstreetmap/iD#8271
openstreetmap/iD#6055

I think there's still a lot of value in having wikidata-backed brand presets for users to choose from, and have the validator suggest these where it makes sense, but autocompleting names is causing more problem and surprising the users.

@bhousel bhousel closed this as completed May 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Not Actionable - just a question about something
Projects
None yet
Development

No branches or pull requests

2 participants