OpenStreetMap logo OpenStreetMap

Changeset When Comment
150724726 over 1 year ago

I think you are going a bit overboard here with turn restrictions 😅. Who would ever decide to do a u-turn from a driveway onto a street back into the same driveway🤣. And I can't imagine any situation where a navigation router ever give such directions too.
---

Published using OSMCha: https://osmcha.org/changesets/150724726

150724278 over 1 year ago

Hello.
These crosswalks look rather strange and do not appear on any satellite imagery. could you please elaborate what are you trying to map here?
---

Published using OSMCha: https://osmcha.org/changesets/150724278

150719945 over 1 year ago

Hello.
Could you please provide some supporting evidence that this is the name of this feature?
---

Published using OSMCha: https://osmcha.org/changesets/150719945

150716371 over 1 year ago

Hello.
There are a couple of issues with this edit.
For one, please group your changes into smaller geographic regions, such a by neighborhood, city or county at most. There's no reason for a changeset to have changes in Wash DC and Long Island NY.
Additionally, when adding phone numbers, they must always include country dialing code (in US it's +1), and preferable they should be separated by - or space.

Finally, if you are tagging that a POI accepts "credit_cards" and "debit_cards" there's really no need to tag each individual brand like mastercard, visa, amex, etc.
👍
---

Published using OSMCha: https://osmcha.org/changesets/150716371

150688164 over 1 year ago

Shold this be addr:housename= or just name= tag? I could be wrong, but I don't think "The Blue Building" would be part of an address you would write on a letter...
---

Published using OSMCha: https://osmcha.org/changesets/150688164

150685882 over 1 year ago

Hello.
Rather than completely deleting a closed biz, it's much better to use lifecycle prefix tags as documented on osm.wiki/Lifecycle_prefix. Doing that not only allows that address to still be searchable and routable, but it also preserves history of this object which can be referred to in the future, if there's ever a need.
---

Published using OSMCha: https://osmcha.org/changesets/150685882

150685827 over 1 year ago

Hello.
Those opening_hours you entered look wrong...
---

Published using OSMCha: https://osmcha.org/changesets/150685827

150685238 over 1 year ago

Residents? This is not not a public park?
---

Published using OSMCha: https://osmcha.org/changesets/150685238

150677006 over 1 year ago

But in this kind of relation inner define the "inner" boundary of that feature, so anything inside of inner is excluded from the relation. Just like when you map a building with a courtyard in the middle, when you 3d renter it you get a (square) donut - there's no building inside of the inner.

150677006 over 1 year ago

I'm not sure that relation for "Fifty Third and Eighth" building is correct. The fact that you mapped it as outer and inner, implies that there's no 1st floor under the "inner" section. That's highly unlikely...

I think it can be simplifies with just regular building:part=1 way and optionally add building:min_level=2 to way/260947181 section.
---

Published using OSMCha: https://osmcha.org/changesets/150677006

150645162 over 1 year ago

Hello.
Rather than deleting existing node with old info and creating a new one, it's better to update the existing node with he current info. Doing that preserves history of that object if there's ever a need to refer to that in the future.
Additionally, as documented on phone=*#Usage, phone numbers must always include a country dialing code (in US it's +1) and digits should be separated only by - or space, not ( ).👍
---

Published using OSMCha: https://osmcha.org/changesets/150645162

150642682 over 1 year ago

Hello.
Is Dun Huang Lanzhou Noodles located in the same space where Cafe PARIS used to be?
---

Published using OSMCha: https://osmcha.org/changesets/150642682

150642522 over 1 year ago

Hello.
Why did you delete address information from this building?
---

Published using OSMCha: https://osmcha.org/changesets/150642522

150642351 over 1 year ago

Hello.
As documented on phone=*#Usage, when adding phone numbers they must always include country dialing code (in US it's +1). Additionally, the numbers should be separated either by - or space.

When adding website address, it must always include https:// or http:// depending on what the website supports.
---

Published using OSMCha: https://osmcha.org/changesets/150642351

150641912 over 1 year ago

Hello.
Is this lane count accurate? Satellite imagery shows that the street is wide enough to fit 2 cars in both directions(plus parking lanes).
---

Published using OSMCha: https://osmcha.org/changesets/150641912

150638569 over 1 year ago

Hello.
The website you provided here is invalid. It must be corrected.
---

Published using OSMCha: https://osmcha.org/changesets/150638569

150596396 over 1 year ago

Hello.
Areas such as school should be mapped to their actual physical boundaries, not extend into the roads. They should not extend beyond the public right of way such as sidewalks..
---

Published using OSMCha: https://osmcha.org/changesets/150596396

150593852 over 1 year ago

Hello.
Please note that when adding website address, it must include https:// or http://.
---

Published using OSMCha: https://osmcha.org/changesets/150593852

150591452 over 1 year ago

Hello.
If a sidewalk is straight, it should be mapped as such, without extra nodes.
Why did you map one crosswalk as "traffic_signals" while another as "uncontrolled" when you can clearly see traffic light gantries extending from 2 corners of this intersection.
Why did you tag corner of crosswalk and sidewalk as an intersection? That doesn't make any logical sense.
Additionally, why did you a curb of 60th st as "flush", when it's supposed to be lowered?

This problems must be corrected.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/150591452

150584458 over 1 year ago

Hello.
Please note that you CAN NOT under any circumstances map based on the data you get from Google Maps. This is a violation of Terms of Service that you agreed with OSM and with Google.
Furthermore, as documented description=* the description tag MUST NOT be used for advertising and promotional messaging. It MUST be a neutral tone description of a given feature.
Additionally, product= tag MUST NOT be used for SEO keyword stuffing.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/150584458