Hi there, addr:street tags shouldn't be abbreviated, I've corrected the tag for this changeset.

Hi there, addr:street tags shouldn't be abbreviated, I've corrected the tag for this changeset.

Hi elipoloos, ways 1239370889 and 1239370887 appear to be overlapping, if these are two buildings they should be mapped individually and have no overlap.
---

Published using OSMCha: https://osmcha.org/changesets/146210108

way/1240077531 looks to be more than a singular house, this should be split into two ways if this is the case
---

Published using OSMCha: https://osmcha.org/changesets/146308328

railway=tram_level_crossing shouldn't be placed on traffic lights, it should only be on nodes where a tram line and a highway intersect.

Reverted changeset, road is part of bicycle network, no signage on most recent streetview, no comment after 1 week

changeset/146264991

This is the only changeset comment they've made in over a year. @DBCA, please read osm.wiki/Good_changeset_comments for why you shouldn't just be putting "area control" for your changeset comments.
---

Published using OSMCha: https://osmcha.org/changesets/146119166

I have to agree with ouchjars, unless there is signage prohibiting cycling on the road (from memory there isn't but it would be good to confirm) then we shouldn't put bicycle=no. Recent Kartaview images don't show any signs preventing cycling, and this road (as well as the cycling track alongside) are part of Bike Direct. I think this changeset needs to be reverted.
---

Published using OSMCha: https://osmcha.org/changesets/145943837

Changeset reverted, please tag the specific house, not the landuse=residential area.

changeset/145821107

Is there a reason the segregated tag was removed here? If the cycleway is designated for both bicycle and foot, and there's not separate sections for each, then segregated=no is correct.
---

Published using OSMCha: https://osmcha.org/changesets/145719246

Is way/833398124 actually named Dirt Track or is this just descriptive?

Hey, separate nodes should be created for the stores, the name should represent the building as a whole.
---

Published using OSMCha: https://osmcha.org/changesets/145793552

Is this unit 18, house number 50? If so, it probably should be tagged as addr:unit=18, addr:housenumber=50

Are these private, or would customers be a better tag? Last time I was in the area these were available for customers of the adjacent businesses.
---

Published using OSMCha: https://osmcha.org/changesets/145784729

I'd recommend trying to figure out why doing what you were trying to do wasn't working, instead of just going "screw it" and causing problems. Merge might be the wrong option, there might be a different option to do what you're trying to do.

OSM is collaborative, which means people are going to have issues if you do the wrong thing, and will call you out on it if you're making invalid/incorrect edits or not following the general expectations of mappers. People also have less tolerance for those editing for golf simulators because of constant vandalism as a result of it, which includes other changes you've made like setting a peninsula to water.

OSM doesn't have a concept of an area, a closed way that's tagged appropriately can be treated as an area. If your software doesn't correctly treat that as an area, then the software needs to be fixed. iD should be able to extend a way to make into a closed way with no problems.

Closed ways will be treated as an area if a tag that indicates an area is added, i.e. landuse, building, or area=yes. There's no concept of an area object in OSM, they're just a closed way that's appropriately tagged.

If the original addition was bad, it might have been done with whatever imagery was available at the time or GPS tracks, if something isn't great, improve it.

There isn't a concept of lines vs areas in OSM, they're open and closed ways. If you need to you can set area=yes on a closed way, but usually other tags will indicate whether it's an area or just a line that loops on itself. i.e. landuse tags will indicate an area, highway usually won't.

Areas are just closed ways, to convert a line (open way) into an area (closed way) you just need to move/extend the current way, and then end it on the first node of the way.

That's because "Keep the history" is one of the things OSM tries to live by. If you can just change what already exists (include an existing node in a new way, or expand/change the existing way), that's always preferred to just deleting and recreating the object.

Might be worth giving osm.wiki/Good_practice a quick read for more info.