Looks much better. Turn restrictions come up a lot and the more people maintaining them the better the routing will be.

If it's a restriction only for trucks, they are a little more complicated. Are cars allowed to make the turn?

Almost correct....

You added the turn restriction correctly, but the check-date/ source should be added to the turn restriction itself (not the node).

Go back to the turn restriction editor, scroll down to the relationships and click on "No Left Turn" and you can add it there (and remove the tags from the node afterwards).

The source for turn restrictions is rarely added cause they're always implied to be signs, but it can be just be source=sign. There are so many turn restrictions, the convention isn't to add a source=sign. Instead implicit=yes is added when it's not signed, which means it's legal to make that turn but it's not advised (usually safety, causes traffic jams, or it's physically not possible for larger vehicles cause of walls or it's too tight).

Based off the new information in Note #5385809, do you mind reverting this change so we can properly update the access and barriers?

Sorry a freak high intensity storm has knocked out my Internet has been out for almost a day. I'm at a store on my phone. I don't think a revert was warranted unless they also removed the signs otherwise the mistake could be repeated. No I haven't been through recently, I was just investigating the note.

Just a heads up, the demolished prefix tag is added to prevent non local people (like me) from accidentally readding demolished feature from aerials. It also keeps the feature from being rendered / routed on.

Since the purpose is to keep people from accidentally readding, I personally leave them till at least the default aerial no longer shows the feature.

But if you're maintaining the area, it's not worth a revert.

It seems like a silly tag, but it has a real purpose.

osm.wiki/Lifecycle_prefix

You're making progress, but there's one more thing you need to fix.

The service_times tag has a unique format:
service_times=*

In your case it should be "Su 08:00,10:00"

OSM has a lot of tags, forutnately you don't have to learn them all to contribute.

OSM has a very flexible tagging system, but the web editor you're using (known as iD) just has a bunch of defaults so new editors are less likely to mess it up.

You will need to merge both the tags for church and a studio into one node.

Use ID to create a temporary church node and add some of the religious information. Then scroll down to the tag section, there is a Text button and it makes copying multiple tags easier.

Copy those tags from the dummy node into the text tag field of the original node. Delete any duplicate fields (like name). Then you can delete the church dummy node.

You can then upload that.

You can also draw an outline of the building if you want. It's not uncommon to have a building outline and a POI (node) on top of it.

Ok, there's a few issues. Currently the church is just labeled as a podcast studio. I'm assuming cause of it's building it's actually a church that holds services and they record the podcasts there. Is that correct?

I looked up the parcel maps and there is a public space for it. Since it was previously mapped, I added a prefix labeling it abandoned.

This will keep it from being used to route and rendered while also letting future mappers be able to add it back if it every gets added back.

You added it correctly. The only thing you needed to do is hit Q after drawing it to "square" it which just makes it look nicer. I took the liberty of updating it for you.

Now you have to power to add most missing buildings and addresses.

Beautiful work on the basins.

131 is probably have trouble with trucks getting stuck in front of their home, so they bought a private sign and put it up to try to solve the problem. There is no public turn around there and backing up is challenging.

I would recommend just changing the access to hgv=no for that section and leaving it public to people walking/biking/cars.

I would just make sure the driveway is mapped as access=private and also put access:delivery=no on the driveway.

That should make everybody happy.

It's a public road according to the parcel map.

Just cause an owner claims it is private doesn't make it true. It just means he put a private sign up on public land.

Go check the parcel map and contact the city.

Hi. I'm a rare mapper who works on speed limits. Often the speed limits get out of date or mapped incorrectly cause they're extremely tedious to do correctly, missing a single sign (or a sign getting knocked down) causes a lot of headaches. And our street side information can become out of date.

I'm not native to the area so I have to use older street side imagery or mapillary. I noticed near the bridge over Meramec River you changed a speed limit down from 60 mph to 55 mph, but the older imagery has a 60 mph going West right after the bridge.

Which is valid?

That's some quality building outlines. Always nice to see it.

A lot of your buildings aren't square. hit the Q key when done and they'll look better.

Thanks for noticing. I try to map to the best of my abilities. Hopefully it makes for a map people feel confident using and feel good contributing to.

I reverted this change. The correct course of action to is to change it to a path, and update the access tag to private which I did. I also added the fences and gates.

OSM maps private roads all the time, if we just delete them people may readd them incorrectly.

Some of the highest quality building work I've seen. Great job.

I removed the park and conflated the address into the building for you.