OpenStreetMap logo OpenStreetMap

Changeset When Comment
161289219 10 months ago

Why do you believe this road is paved?

way/818618350/history#map=17/41.180741/-76.365463

162029253 10 months ago

I do not copy data from Google in any massive way, but I also refer to them because of the sign not being human readable while I'm on the phone.

162029253 10 months ago

Oh? If you feel like the name accepted by Google is wrong, then feel free to correct it. I have no opinion it, my "job" is to verify that the business is open there, whatever name they should have, you are welcome to make changes if appropriate.

162068308 10 months ago

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.

162068308 10 months ago

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.

162068308 10 months ago

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.

162029253 10 months ago

Don’t remember

161376975 11 months ago

Thank you!

161376975 11 months ago

way/15309013

161376975 11 months ago

The height limit is simply wrong!

161376975 11 months ago

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

way/15309013/history/

130684143 11 months ago

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

way/1125823351#map=19/39.523240/-75.817002

160807827 11 months ago

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

160006580 11 months ago

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.

160807827 11 months ago

For Austin Trl near Eagle Rd: 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").

160723311 11 months ago

The road here has markings.

way/12005895#map=16/41.18640/-76.31453

141745825 11 months ago

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.

154244957 11 months ago

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

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?

158151004 12 months ago

Why this bridge has different classification than others nearby?

way/1326405935#map=19/41.216040/-76.432432

160305303 12 months ago

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.