Add One-O-One stores

[ClarSco]

One-O-One is a chain of convenience stores in Scotland.

According to its website (https://one-o-one.co.uk/) it has 45 branches across the country

[UKChris-osm]

Thank you @ClarSco

Would "One O One" be more accurate?

I don't think they uses dashes in the name, just their web address?

Also, you can use gb-sct as the locationSet to target Scotland.

[ClarSco]

Both hyphenated and unhyphenated usage seems common across the relevant websites, though the hyphenated version appears more often in formal/legal contexts, which is why I defaulted to the hyphenated version. Here's a rough breakdown of their usages:

Places that use the hyphenated version

• Companies House as "ONE-O-ONE CONVENIENCE STORES LIMITED"
• all web addresses
• the copyright line at the bottom of their website is styled as "ONE-O-ONE CONVENIENCE STORES LIMITED"
• the parent company (Scotsman Group) list the shops under "ONE-O-ONE RETAIL" or "One-O-One Retail"on their website
• Their "premium" stores appear to style the logo as "One · O · One Provisions Co." (using interpuncts rather than hyphens).

Places that use the unhyphenated version:

• The address section on the main website
• The body and "hamburger" menu text on the Scotsman group's website
• The non-premium logo, used on most shop fronts/main website

Places that use both with similar frequency:

• The terms & conditions section of their website.

[ClarSco]

Also, you can use gb-sct as the locationSet to target Scotland.

Good point. Will change this as the Store Growth section of the website is explicit about them only looking expanding within Scotland.

[ClarSco]

I should also add: in the FHRS database, many of these stores are listed under an older name of "G101", "G101 Off-sales", or similar. I doubt that many stores will have been tagged as such in the OSM, but if this is something that can be handled via the NSI, that would be great (though I don't know the appropriate schema).

[UKChris-osm]

I thought I'd check overpass, and as it seems there are already a few entries within OSM that use the hyphen version, it makes sense to maintain that.

There is something we call matchNames that you can add to your entry, underneath locationSet, that you can add case-insensitive keywords that would match up, such as:

"matchNames": ["g101", "g101 off-sales"],