Correct source link: https://capitolhillcorner.org/2024/10/12/first-look-at-butterworths-photo-essay/

What is the purpose of removing this information? It does not seem straight forward or reliable to have to derive an address from the branch tag.

A bunch of these edited Starbucks appear to be standalone locations where the branch is named for a nearby store, not a store they are actually inside.

Hi - before adding tags to ways like this, please check if they are already a member of a relation. There is already a well-tagged relation for this stadium and no need for a duplicate: osm.org/relation/7370103

Hi - it looks like your edit of the KeyBank Center traces the Bing imagery a bit too literally. Compare with the Digital Globe or Mapbox layers to see that the Bing imagery has some significant perspective distortion, The previous shape was fine.

Hi! The golf course you added already exists as a relation here osm.org/relation/2816630 - no need to tag the outer way.

Hi! What is the source for your change to Capital University? It now includes some commercial-looking areas as well as a church and Bexley city hall, which doesn't seem quite right.

Also Drexel Avenue got disconnected from Main Street - is that intentional?

Hi, please only add things that really exist.

What was duplicate? The wikidata tag now seems to point to the wrong entity

Hi. Is 9876867676 meant to be a telephone number? Also curious about the strange name and denomination for a restaurant.

The information at this wiki link (osm.wiki/WikiProject_Canada#Crowdsourcing_buildings_with_Statistics_Canada) is extremely sparse - is there more complete process documentation somewhere? The same import deleted hundreds of buildings I mapped by hand in Stittsville and I don't see a significant increase in quality from the Ottawa data. The usual import process would have been to keep or update the existing features rather than clearcutting.

There seem to be a lot of issues with this data. Many of the addresses duplicate data that was already in OSM. In other cases this one changeset includes redundant data. For example, you added 4 nodes for this 1 address:

osm.org/node/4431044818
osm.org/node/4431044819#map=19/45.26627/-75.93767
osm.org/node/4431044820
osm.org/node/4431044821

Same for many other addresses in that area.

These ways should not have coastline tags - they are part of a water multipolygon, not the coastline. There are no other coastline tags on the St Lawrence until further downriver http://overpass-turbo.eu/s/i5L

I clicked too fast - this change actually connects two touching pieces of island on Lac Saint-Louis into one.

I've been doing some experiments with using Wikidata and OSM to generate lists & rankings of famous landmarks around the world. This one caught my eye because I was surprised to see it on the list (I didn't know it was a museum) and also because there were 2 buildings with the same label.

Hi, this change and your other recent one (#33925972) are very strange. A mistaken upload? These large buildings should be deleted.

I should add that the situation is similar for sidewalks - many roads in DC are already tagged with `sidewalk=left/right/both` and don't need separate paths mapped.

Hi, I noticed you've added several independent cycleways for bike lanes that are part of the main road way. These bike lanes are already captured by the `cycleway=lane` tag on the road - eg osm.org/way/48018640 . Per the wiki I think it would be best to remove the ways you added since the bike lanes are not physically separated from the road osm.wiki/Key:cycleway#Dedicated_cycle_lanes

natural=coastline should only be applied to ways, not relations. See osm.wiki/Tag:natural%3Dcoastline

I've changed the relation's tag back to natural=water since it had disappeared from many renderings.

Hm, perhaps a navigation system should try to navigate to the terminal buildings and not the centroid of the whole airport. I'm not sure what the best approach is for mapping entrances to large facilities to help with routing.

While it helps solve a routing issue, having multiple aeroway=aerodrome objects for the same airport causes problems in several other areas such as search, data management, data analysis, and rendering.

A node isn't necessary, it's duplicating all the information on the way: osm.org/way/55204821