i fixed it changeset/186953524

I'm not sure what your goal was in editing it, but it seemed like you broke the Westminster administrative boundary, removing the admin level, and also edited the wiki data to point to a British city?

long road :p

Hi, most of this changeset is solid, but minor issue: please don't delete footway=link ways connecting two nearby features unless something else is added to connect them. Footway=link does not generally correspond to a physical feature, so it can be left in place as long as it is reasonably traverseable and useful for routing purposes, even without a physical footway.

footway=link

Hi, it seems like in this changeset you accidentally snapped some corners of the houses you made to be attached to the Westminster City Limits administrative boundary line. In the future, when you're trying to work with features that are very close to other features, you can hold down the "Alt" key on your keyboard while dragging a node, and it will no longer snap to nearby objects, as long as you are holding the key down.

Something else I would recommend would be to go into the "Map Data" tab on the right side of your editor, and in that window, if you scroll down, you can choose to change the visibility of certain things in the "Map Features" section. I personally always have the "Boundaries" section set to invisible, since it is very rare that you actually need to edit that, and it oftentimes gets in the way of things.

I'll go ahead and fix the issue here, so don't worry about this one, just keep it in mind for the future :)

Hi, it's good to see you back with some more changes around here :)

When mapping townhouses, or in general buildings that share a wall/are physically connected, you should map them so that they have shared corners, with no gap between them. When making a new area in the editor, you should notice that you can "snap" a point to another existing point while drawing the area, in this case you want to snap the shared corners together.

Also, with townhouses, when you are selecting the kind of feature they are, it's better to select the "Townhouse" feature preset, instead of the "House" preset, when searching. Or, if you don't want to bother mapping every unit individually, you can draw an area encompassing a full row of townhouses as one area, and pick the "Row of Townhouses" preset.

Hi, welcome to OpenStreetMap, I'm glad to see a new face helping add to the map around Westminster :)

some tips for future edits:
-try not to follow the roof line too literally when adding buildings, the way aerial imagery is displayed can skew the roofs based on their height and create some odd angles that aren't necessarily representative of what the buildings look like in reality. Most buildings in the real world are comprised primarily of simple 90 degree angles, and ideally the building in OpenStreetMap should show that, being a trace of where the walls would be, rather than the roof angles, if that makes sense. Something that can help with this is, once you have traced the basic outline of a building, you can right click it, and select the "square" option, which will automatically make any angles close to 90 degrees snap to exactly 90 degrees, helping to clean up the geometry.

-open up the "background settings" menu on the right of the editor, and have a look through the different aerial imagery available. By default, the editor will show you the Maryland 6 inch layer, but different layers may show more detail and more relevant information for what you're trying to do. I personally find myself primarily using the Maryland 3 inch layer, as it has more detail in the imagery (3 inches per pixel as opposed to 6 inches per pixel), but it's good to swap around image sets, as the 3 inch layer is a decent bit older (~2017), so it doesn't always have the most up to date information. Also, be careful when editing around existing features, because different imagery sets have different "offsets", basically errors in the horizontal and vertical directions, so different things may show as off by a few meters, depending on the layer you are looking at. Try to keep things aligned with objects that already exist on the map nearby when you can

Hopefully this doesn't come across as discouraging, I'm happy to see a new user in the area, and I hope you'll stick around to make our maps better for everyone :)

that's a long walk :p

please try to keep changesets within reasonable geographic boundaries

Please try to keep changesets somewhat geographically consistent, this changeset has minor changes in York, PA, as well as unrelated changes in Raleigh, NC, leading to an unnecessarily large bounding box.

please avoid such geographically large changesets unless absolutely necessary, 4 different changesets you made are spanning multiple continents

please avoid changesets that span massive geographical areas

please avoid committing very geographically dispersed changesets, one changeset per region helps massively with readability