You're right. Neither link works on mobile for some reason, but the old one appears to work on "desktop view" on my phone. I'll investigate when I'm back at my computer this week.

I'm comfortable being fairly aggressive in removing address data from potential "store in store" Starbucks locations since it was flagged to me as being more prone to error than normal store data. But I'm happy to restore some of it if you all can articulate a better way for me to identify these "store in store" objects than the `branch` tag method I used for this changeset!

Hi tguen. Unless I'm misunderstanding, the website value on that way appears to be the same before and after my edit, so I don't think I touched it.

See changeset/151668196. Should all be fixed.

The thinking is just that these Starbucks are ones that are inside other stores (grocery stores, Targets, etc) that should have their own addresses, and thus these addresses are significantly more likely to be incorrect (either from parsing or because the source data is bad) and/or irrelevant.

Ok, should be fixed here: changeset/151571627. The regex I used on the branch tag was "^(Target|Safeway|Kroger|Albertsons|Harris Teeter|Hy-Vee|Vons|Fred Meyer|King Sooper|Giant|Ralphs|Fry's|Jewel|Macy's|Smith's|Dillons|Pavilions).*"

* I should say, remove the address tags, not the nodes themselves.

Yeah, there may be a way to use the `branch` values to find and remove some of the Starbucks within other stores. I'll look into it!

Hi DarkDays. I see you've done a lot of these website imports. Is this documented anywhere? What is the source you're using?

I'll keep an eye on the next release and see if the data is any better. Otherwise I'll strip the bad opening_hours tags off.

Huh, thanks for flagging. It looks like this is pretty widespread and not just simply a 10:30->22:30 change, so I'll probably just remove the `opening_hours` tag from all the Wendy's objects I modified.

Hi MxxCon. I'm confident I didn't add this tag, but it's a good reminder to wipe these out when I see them. I've created a JOSM validator rule so that it gets flagged whenever these come up in the future.

Hi Woodpeck. Can you point me to where these "foreign keys" are? I believe I only added very standard keys (address, phone, website, various names), and "ref" for the hotel reference code. Under what key do you think that info would fit better? The community discussion for this import is here, as linked in the wiki page in the changeset tags: https://community.openstreetmap.org/t/proposed-import-of-all-the-places-data-onto-existing-hotel-pois-in-the-us/109552 . Thanks!

Should be fixed now. Thanks.

Should be fixed now

Hey, feel free to change it. I updated other tags in this changeset.

This is not correct. 66 has a speed limit of 55, not Langston.

Hi InsertUser. The community discussion was here, also already linked in the wiki page: https://community.openstreetmap.org/t/proposed-import-of-all-the-places-data-onto-existing-grocery-store-pois-in-the-us/108611

That's a good question, and I honestly don't know enough about public transportation tagging to know if it's incorrect. I would pose the question in the #public_transport channel in the OSM US Slack, and someone who knows more would be able to weigh in.

Thank you, sorry about that.