Mike,

If a road seems misaligned please check other imagery sources before moving it. Eva Avenue was reconstructed slightly to the west, and Bing does not have updated aerial imagery yet, if you look at Maxar Premium you can see the road's new location. I have reverted this changeset back.

Thanks.

Hey there,
Houses typically do not have names and their address definitely should not go in the name tag. The addr:* tags are all that is needed. See the houses on the other side of Saint Peters Howell for reference.

Thanks.

Mike, again, drawing knuckles as loops is incorrect. I have reverted your changes to the knuckles in this changeset.

Please refer to my earlier comments on one of your other changesets for further information: changeset/118211471

To explain a bit why this is important: if you draw the knuckles as loops your routing software may tell you to 'take the second left' and as a driver you might miss your turn because you were looking for a second street past the knuckle. Drawing them as a single way indicates to the driver that there's only one entrance to where you're turning. And as someone who relies on OSM data for their job, having correct accurate information is important to me personally.

Also worth mentioning that if you want to draw the actual shape of the knuckles, that's fine, but there's a dedicated area:highway=* tag for that that should be drawn separately from the main routable road network.

Hey Mike, it is incorrect to draw road 'knuckles' (sometimes called 'eyebrows') as a loop of road unless there is an *actual* physical barrier creating that loop. The correct way is to add a short stub with a highway=turning_circle at the end, you can also add the turning_circle=knuckle tag to indicate that this feature is a road knuckle instead of a normal cul-de-sac. Thanks. Please refer to the following wiki entries for further information: highway=turning_circle turning_circle=*

Short weekend closures of the interstate (or any road for that matter) for bridge demolition should NOT be updated to access=no/highway=construction. OSM is not a real-time traffic source, and these short closures are not necessary to add. If a data consumer who, for example, only updated their data quarterly pulled this data then this 3 day closure would be live in their system for the next 3 months. Only Broadway over I44 (+ the ramp from the express lane) are closed until 2023. Additionally, the express lanes are not permanently closed and are scheduled to re-open before the end of February per a MoDOT press release. Please verify your closure information with official sources in the future. You also (accidentally) changed a number of administrative segments to highways. Please be careful when selecting ways and make sure you have ONLY selected the ways you intended to change. I've gone ahead and resolved all these issues.

I responded to this in your private message to me.

Not in my opinion, no.

This section of 141 doesn't have any driveways/entrances directly off of it, so although there's no separation between the directions (aside from a double-double yellow line) this is still effectively somewhat access-controlled (and thus retains it's trunk status.)

K has way too many driveways/intersections close together to be a trunk, and same goes for Lindbergh outside of the section already designated as trunk; north of 270 and south of Manchester Lindbergh has far too many driveways/intersections.

Correct, roads do not need to be divided to be considered trunk.

141 was built to be a ring road and designed to be an alternate to 270 and should retain it's trunk classification for the whole length.

Why are we downgrading 141 from Trunk to Primary through here?

141 clearly meets Trunk standards for just about it's entire length.

Hi, has Megan Drive actually been removed in reality or do you just not want people driving through that particular section?

If it's the latter then deleting the road from OSM is NOT the way to go about it. Simply adding a gate and setting the access to 'private' on the gate and road is the correct way to prevent people from being routed through there.

Hi, sorry to keep poking at your changesets but while this may be a census designated place Defiance should be left a place=hamlet. In OSM a hamlet is described as a community with 3-199 residents. As of the 2010 census Defiance had an estimated 155 residents. Towns are reserved for large populated areas with populations between 10,000 & 50,000.

See this wiki article for further information: osm.wiki/United_States_admin_level#Unincorporated_areas

This would be better left as highway=unclassified (or service and drop Hayford Road down to service as well.)

Use the smoothness=* key to indicate poor road condition. Judging by the satellite imagery I'd go with intermediate

Whoops, the creek was actually already joined to the park boundary in several spots by someone else and I could've swore I had unglued all those nodes, but I must've missed one. Guess that's what I get after scolding someone else for accidentally moving a node, hah.

Strange that josm never warned me about a waterway crossing itself though. Just ran the validator again and it correctly identified it so perhaps both me & josm missed it the first time around.

Either way, the stream has been unglued from the state park boundary and the node has been put back where it's supposed to be.

Hi, it looks like you might have accidentally dragged a node from a road in Rio de Janeiro all the way up to Iowa.

I've gone ahead and reverted that specific change putting the node back where it belongs. (Changeset for reference: 74070419)

Please be more careful when editing in the future as to not drag features between continents.

Hi there, I'm sure it was done accidentally but you renamed a section of Manchester Road to 'Laser Me' with this changeset. I have reverted this changeset (with changeset/71730601)

I have correctly added your business with changeset/71730658.

Let me know if you have any questions.

I shot you a private message as the complex formatting and hyperlinks that my reply has aren't really supported in changeset comments.

I see you have review_requested on this changeset, but I'm assuming you're not done with this edit, right?

Just asking since both the O'Fallon & St. Peters relations are now broken and misaligned in some places. Also Old Knaust Rd has been knocked out of alignment.

And, don't trust the county map completely(if that's what you're working off of) as it is wrong in multiple areas. I had already gone through the St. Peters relation and it is(was) 100% accurate according to city records (Which are more up-to-date than the county's records).

Relations can be very tricky to work with (Especially since you're using iD, which I don't believe has full relation support), so let me know if you need any help with modifying them.

Be careful when editing around power lines. You accidentally attached this parking lot node to the power line: node/6209502538

I went ahead and fixed it for you.

Lowe's looks fine to me except for one small issue: on the contractor loading roof the driveway that goes underneath it is not connected to the roof on the north side. The node where a way transitions from covered=yes to not covered should always be connected to the building. (The south side is correctly done)

Also, my personal preference is to tag the building though, but that's just me. You can find multiple arguments for or against tagging the building vs tagging a point within the building. So feel free to keep tagging POI's as single points if you prefer.

The turn lanes look good to me. You have the correct number and they're facing the right direction which is what's important, lol.