Thanks, I will put this on my calendar and get it done by the end of this week, I won't have this issue with the computer.

I figured out the issue, there is a setting called "smart punctuation" in iOS and it does this.

If you have the overpass query feel free to share here and I will correct those out of TX after then.

This is weird to be honest.

I’m using iOS keyboard (English), may need to review this when I’m back to the computer. If you can change please do that.

Don’t remember

Thank you!

osm.org/way/15309013

The height limit is simply wrong!

Where do you live? Are you physically in the US? What kind of terrible data source was being used here?

osm.org/way/15309013/history/

Yeah, you did change swimming pools to building, must be very smart I guess.

osm.org/way/1125823351#map=19/39.523240/-75.817002

I don’t need data source in PA, I’m the source because I drove there before.

Wiki can be edited by anyone, I don’t agree with it.

Having two lanes != road is not one way, so technically speaking if I want to say it is one lane and not one way, that’s also correct.

For Austin Trl near Eagle Rd: osm.org/way/1347398441/history#map=19/41.188342/-76.460292

Sometimes an exception can be given by not (cutting the segment into two & explicitly mark that tiny part near the intersection as no markings), reason is because of the proximity to the intersection for turning. In urban areas you also won't see lane markings full applied when it is close to the intersection (often stop at the "stop line").

The road here has markings.

osm.org/way/12005895#map=16/41.18640/-76.31453

Well...you should not resolve any warning (from iD editor) by just applying its suggested fix (which is likely what you did there), because in this case you apparently added a ford and the reality does not agree with it.

However, there is also a chance that the bridge was recently installed, I do not have any prior information but this preserve is indeed having some projects down to the valley.

Do you have any idea of what your team was doing here?

osm.org/changeset/154244957#map=19/40.030709/-75.153877

You added a conditional restriction to a node, this node could be a part of the relation nearby, or could be not, how could others interpret?

Why don't you add that condition to the relation?

Why this bridge has different classification than others nearby?

osm.org/way/1326405935#map=19/41.216040/-76.432432

If there is no marking, even if the road is two way, you should still not map lanes and assume “2”.

We do not map “assumptions”, I understand your logic but tagging the road “no marking” is enough, mapping lanes and specify how many each direction has, is overegg the pudding.

You are right.

So “lanes” should not be added then.

Any valid reason to spam dog/cat/horse whatever animal access on the sidewalk? I think canada geese as well as black bear are also good here.

Is there any legal sign saying "yes" to them?

osm.org/way/1206750316#map=17/41.050978/-76.220473

You should not tag stop sign NOT on the road, this is quite confusing and dangerous.

osm.org/node/11148968986#map=19/41.051516/-76.223625