Did you get around to documenting the tags? I have no preference, feel free to update this one.

node/9556168334

Shouldn't have made it to OSM.

node/9556168333

record_type shouldn't be in OSM.

This is testing a new MapComplete theme. Don't worry, I'll clean up the data.

It's a duplicate of disused:shop. I'm trying to stop the build up of shops that shop=shoe & disused:shop=book like this:

node/1977957768

By chance, the next one I looked at:

node/1977957768

Just looking at the current OSM data there is no way to identify which is correct, is it a disused shoe shop, or a in use book shop.

Looking at the history we can obviously see it's a book shop, but data consumers can't.

Hey, I don't think you should be adding disused:shop=* and shop=vacant on the same node. Just disused:shop=* is enough.

While both identity an empty store front, having both can lead to shop=* being updated with disused:shop=* not getting removed.

node/1559470913

Oh yeah, thank you

Do you know if this is staying closed forever? I heard all the Metros were changing into Express or Superstores

I just fixed your last one.

node/9322986243

Can you at least try to map it right.

Hey, just a heads up house numbers go in `addr:housenumber` not `name`.

Fixed in #114315238

Hey,

We call this "mapping for the renderer" and we don't do it. OSM should be as correct as possible, it's the tooling that creates the maps that should be making it pretty.

I've readded the name in #114315059

Looks good, thank you

I saw some of your work in Treharris when I was mapping individual properties. Your buildings made that job much easier, thank you.

Cleaned up in #113543554.

Address nodes shouldn't be on the way.

Cleaned up in #113543554

Thanks for this, it looks good!

I've been remote mapping Merthyr Tydfil for a couple of weeks now, good to see somebody local also contributing. :)

Are you sure this is an Aldi?
FHRS Open Data has it as a Lidl.

way/853037363
https://ratings.food.gov.uk/business/en-GB/1029115

Yeah, I made that tile server. Run dataset through ogr2ogr to fix the projection locally.

Something like:
ogr2ogr -s_srs "+proj=tmerc +lat_0=49 +lon_0=-2 +k=0.9996012717 +x_0=400000 +y_0=-100000 +ellps=airy +units=m
+bounds=-9,49,2,61 +no_defs +nadgrids=/home/cj/.local/share/QGIS/QGIS3/profiles/default/proj/OSTN15_NTv2_OSGBtoETRS.gsb" -t_srs EPSG:4326 "outfilename" "infilename"

If you don't have QGIS installed you can get OSTN15_NTv2_OSGBtoETRS.gsb from https://www.ordnancesurvey.co.uk/business-government/tools-support/os-net/for-developers

Just a heads up, if you are gonna work with this dataset you need to project it properly. Aligning to it with JOSM bad projection isn't going to help.

way/995571275
This one specifically is about a meter out.

Nice one, I extended the sidewalk to a more accurate point, I guess that's what caused this. Kinda surprised JOSM didn't warn me about it.