Hi there,

You added way/1342511097 with no tags, could you please go back and tag it? Thanks!

Hi there,

In OSM, the housenumber needs to be added to "addr:housenumber", not "name". Can you please fix way/1340703920#map=18/43.821007/-84.773960 and all the houses surrounding it? Thanks!

Hi there,

On this intersection you made the crossing tags "traffic_signals;uncontrolled". Could you please go back and fix this? Thanks!

node/3750151579
node/3750151581
node/3750151582
node/3750151580

Hi there,

You created a way with no tags here: way/1341013415
Would you please go back and add tags? Thanks!

Hi there,

You created a way with no tags here: way/1341112663 could you please go back and tag it? Thanks!

Thanks!

Also, it's not my eagle eyes looking through every changeset, I just get reports from Osmose (osm.wiki/Osmose) about things like this.

Hi there,

On way/184849291 your lane counts don't match up (5+2=4) and on way/1129908908 you have lanes:forward=2 but turn:lanes:forward has 5 lanes. Could you please fix these? Thanks!

i prefer mapping them separately, because there's a lot of detail like backrest, seats, etc. that you can add. I would just approximate where they are with aerial imagery

Hi there,

For node/10067814800
node/475422045
node/12006687521

it's best not to "overload" nodes by giving them two primary functions. If a bus stop has a bench and/or bike parking, you should map those as a separate node.

Hi there,

Unfortunately I had to undo this change, as it broke several roads and areas. Please make sure you understand how to use the editor, specifically:
- Don't create roads overtop of existing roads
- Streets in addresses need to be spelled out in full, not abbreviated
- Pay attention to the warnings that the editor gave you before you saved, and fix them before saving

Hope this helps!

Hi there,

For the bus stops, direction=inbound/outbound should be used on the route relation rather than each individual stop, since individual stops can be part of different routes

Hi there,

Generally it's not correct to have two different ways for the same road unless there's physical separation (like the intersection below it). From what I can tell, there was nothing wrong with the intersection before, but I might have missed something, what made you think that turns weren't allowed before?

Hi there,

way/1065579479 is broken because the top right node (node/9785940352) makes it an unclosed way. Can you please fix this? Thanks!

Thanks for the response, in the future please don't delete tags like this, because very often people forget to put them back

Oh, i see, i'm not aware of any tagging for that then, sorry

Worth noting that "leisure=swimming_pool"+"https://wiki.openstreetmap.org/wiki/Tag:swimming_pool=lazy_river" (swimming_pool=*#Alternative_usage) seems to have more usage than leisure=lazy_river

> I'll change the highway from "water_path" to "path" for now, those ways were meant to indicate traffic flows within a pool area, both after exiting a water slide and for approaching stairs. Is there a tag that I can use to indicate that the path is used for these purposes, or simply to indicate that they are paths within the water?

I'm not sure those are meant to be tagged, a pool is inherently unroutable since it's a body of water, and I don't know of a standardized tagging for "suggested paths through water". Probably the best thing to do is look up other waterparks and see what tagging they have.

> (which this tag is also not listed on the wiki for highway, should I change it?),

No, the wiki should only be changed if there's a large usage of the tag

For the facebook question, it's the same as the website tag of the other changeset, the contact:facebook tag is a duplicate of the facebook tag, they aren't meant to be both specified in the same object, and the tag value is the full URL or pagename, not a group name (see facebook=*)

putting the group in source:service_times makes the most sense to me, but there's not a standard way in OSM to define two different facebook URLs for the same object

contact: is a tag namespace prefix, it's not a qualifier for the website tag. Basically they are identical tags, you can read about that here: contact:website=*

What you want to do would be best done using the website: prefix (website:*=*), so probably website:contact, but there's not a lot of support for that.

Hi there,

Why did you remove the crossing tags from this crossing?

landuse=grass is described as “A tag for a smaller areas of mown and managed grass for example in the middle of a roundabout” landuse=grass