When mapping/updating supermarket chains in Geneva, I noticed few discrepancies in the Name Suggestion Index (NSI) for supermarkets and convenience stores in Switzerland. This is used to do presets in iD-editor:
If other mappers use those presets, it might be worth updating them.
For Aldi, Aligro, Lidl, Manor, Migrolino, the settings can probably be the same for Switzerland
For Denner, Coop, VOI Migros Partenaire, they should be language specific (French in my list).
For Migros, operator is specific to the Geneva area.
Aldi is probably the most problematic, as it lists now “Aldi Süd”.
The entry for VOI adds text in German (and removes Migros from the name). There is a similar problem with Swiss Post (which adds the operator in German, not French).
If the operator is preset, operator:ref:CH:UID could be included as well (in the link in the table).
Are we able to split NSI entries by language region for name? Or do you suggest to add name:$LANGUAGE to NSI?
Name Suggestion Index Adds operator in German, and correct operator$LANGUAGE for $Language in [en, fr, it, rm].
Do you suggest to remove the operator, or - maybe preferably - only have the language-agnostic operator:wikidata?
I don’t know the detailed workings for NSI, but the result for the map should be that name and operator is correctly added. For the ones in my list, I’d expect the values there. Some Swiss companies have different brand names/company names in each language (Coop, Denner, Post(e), VOI Migros Partenaire), others don’t (Aldi Suisse SA, Aligros/Demaurex, Lidl Schweiz AG, Manor Food).
For Post(e): CHE-435.551.225 suggests the operator should be “Post CH AG”, “Poste CH SA”, “Posta CH SA” depending on the language of the region. I’d add that and remove the operator:language-tags. operator:wikidata without operator seems problematic.
Differs on the intended outcome. Linking all the entries together with a single key is easier, making a map for language regions with showing “correct” name on the map is easier with many language-specific keys.
Yes, the matching for boundaries.osm.ch is performed on BFS-Number value, which is in the swissBOUNDARIES3D and in the OpenStreetMap data, both under a different key.
I think we should ultimately move swisstopo:BFS_NUMMER to something else (maybe simply ref:bfs).