layer=* implies one building is over or under another, but if both are at ground level then it's unlikely adding a layer=* is the correct way to resolve overlapping buildings.

changeset/173856773

layer=* implies one building is over or under another, but if both are at ground level then it's unlikely adding a layer=* is the correct way to resolve overlapping buildings.

changeset/173856773

layer=1 implies one building is over the other, but that's unlikely here they are both likely at ground level.

Edgeroi is already mapped at relation/5793377 as a place=hamlet. I've reverted this change since it created a duplicate place for Edgeroi.

unit 3 is already mapped at node/12416900561 and this address is already mapped as addr:unit=1.

I've reverted this change.

you can add multiple buildings in one changeset, then save at the end rather than creating a changeset for each building.

Thanks for fixing it, sorry from the outside it looked like apartments but I didn't check any signs or entrances.

What's there now? If it's a construction site best to use landuse=construction.

Where was the data for these sourced from?

relation/2386039 already exists so node/13133160273 is a duplicate.

Nice work!

you can add service=driveway to specify the type of service road and also driveway=pipestem to mark it as a shared driveway.

sorry my mistake, you've already applied that to the true boardwalk sections

sounds like it should also have bridge=boardwalk

reverting since this doesn't look right and no comment or justification was given.

relation/9487066 is the route_master

fyi note/4618878 regarding node/7911236708/history

Thanks! Yes that was my mistake, fixed now.

node/5261267190/history

from what I can see, there's no restrictions on walking or cycling over the ford so I'll remove those access tags you added.

I've restored the way but changed the tags to be a private driveway rather than public street.

reverted

reverted