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

add Tanuki data, fixes osmlab#921 #2550

Merged
merged 1 commit into from
Apr 6, 2019
Merged

add Tanuki data, fixes osmlab#921 #2550

merged 1 commit into from
Apr 6, 2019

Conversation

DmitriiKh
Copy link
Contributor

No description provided.

@matkoniecz matkoniecz merged commit f110960 into osmlab:master Apr 6, 2019
@matkoniecz
Copy link
Contributor

Thank you! This pull request is now merged so your work is now part of name-suggestion-index project.

@Adamant36
Copy link
Collaborator

Probably should have included the Ukrainian name:whatever it is also. I think that's how we do it now if name:en=whatever is added. I guess it can be added later though.

@matkoniecz
Copy link
Contributor

Ukrainian

Why? See http://overpass-turbo.eu/s/HKA

Though name:ru probably may be added (with the same value as name tag).

@Adamant36
Copy link
Collaborator

name:ru then. Google translate said it was Ukrainian for some reason. So that's what I went with.

@DmitriiKh
Copy link
Contributor Author

Thanks!
Let me check if I get it right.
name:ru Тануки
name:en Tanuki
name ? Should it be the same as ru or en? Do you have a preference for this?

@matkoniecz
Copy link
Contributor

name:ru Тануки
name:en Tanuki

Yes.

name ? Should it be the same as ru or en? Do you have a preference for this?

In this case Russian, name is for name actually used on the ground and this restaurant chain is in Russia. So I expect that people in Russia use "Тануки" rather than "Tanuki".

It is trickier with company operating under multiple names in different countries, we use multiple entries with country restrictions to cover that.

@DmitriiKh
Copy link
Contributor Author

DmitriiKh commented Apr 6, 2019

I see. Thanks for the explanation :) Would you like me to make a change to add name:ru Тануки and maybe "countryCodes": ["ru"] ? Or it can be done next time?

@matkoniecz
Copy link
Contributor

Feel free to make a new PR!

and maybe "countryCodes": ["ru"]

Some entries are appearing outside Russia. It may be worth checking is it actually supposed to be present there, maybe also some countries should be also in countryCodes list.

@DmitriiKh
Copy link
Contributor Author

Okay. There are also three restaurants in Ukraine. Therefore it should be "countryCodes": ["ru", "ua"], "name": "Тануки", "name:ru": "Тануки", "name:ua": "Танукi", "name:en": "Tanuki" I think.

@Adamant36
Copy link
Collaborator

Adamant36 commented Apr 6, 2019

the country codes are correct. You only need either ru or ua for the language though. Usually whichever one the sign is in. We normally only use English and one other language, either the main language of the business or in rare cases the dominate language of the area where its located.

@DmitriiKh
Copy link
Contributor Author

Thanks. I'm gonna keep "name:ru": "Тануки" as this is the main language of the business.

@DmitriiKh
Copy link
Contributor Author

I've checked tanuki.kz (Kazakhstan) and have found out that there is a one more restaurant of the same brand.
This restaurant is not on the map yet but someone will add it later I guess.
Therefore it could be either "countryCodes": ["ru", "ua", "kz] or no countryCodes.
What do you think would be better?
I would go with no countryCodes because this brand can easily open new restaurants in other post soviet countries in the future.

@Adamant36
Copy link
Collaborator

Using the three country codes is fine, they aren't supported in iD editor yet anyway. So having them there won't cause problems. Its always better in my opinion to have some information versus no information also.

@DmitriiKh
Copy link
Contributor Author

Okay. Then it is gonna be adding "countryCodes": ["ru", "ua", "kz] and "name:ru": "Тануки"

@bhousel
Copy link
Member

bhousel commented Apr 6, 2019

Using the three country codes is fine, they aren't supported in iD editor yet anyway.

Good news, @quincylvania implemented this recently! openstreetmap/iD#6124
The country scopes will work in the next version.

@matkoniecz
Copy link
Contributor

they aren't supported in iD editor yet anyway.

countryCodes are supported in Vespucci

@bhousel
Copy link
Member

bhousel commented Apr 6, 2019

the country codes are correct. You only need either ru or ua for the language though. Usually whichever one the sign is in. We normally only use English and one other language, either the main language of the business or in rare cases the dominate language of the area where its located.

Also about this - I think we should relax this rule a little bit for countries where they speak several languages. It's ok to put a few languages that are spoken interchangeably there.

For example, for the BY Post offices issue, I left both :be, :ru, and :en languages in there, because in that country they really do speak both, and the signs are both.
#2482 (comment)

@Adamant36
Copy link
Collaborator

"Also about this - I think we should relax this rule a little bit for countries where they speak several languages."

I agree with that. I think there can be a few languages added in some cases were multiple languages are spoken in the place without things getting out of hand. Plus, it means a lot less explaining to do when it comes up. Which I'm all for.

@bhousel
Copy link
Member

bhousel commented Apr 7, 2019

Plus, it means a lot less explaining to do when it comes up. Which I'm all for.

Same 💯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants