OpenStreetMap logo OpenStreetMap

Changeset When Comment
117945162 almost 4 years ago

Hello.
Based on the available satellite imagery it doesn't appear like there's a crosswalk or intersection here. IF there's actually an intersection or a crosswalk, it must be mapped as such, and not just as footpath.
Can you please elaborate on this edit?
---

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

117918613 almost 4 years ago

Hello.
Is smashburger going to occupy the whole building and not just the first floor?
---

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

117897614 almost 4 years ago

Hello.
When adding phone numbers, please try to have them formatted as documented in phone=*#Usage
The way you added is not outright wrong, but it's better if everything is consistent. 👍
---

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

117882496 almost 4 years ago

Hello.
Please note that OSM map must not be used "for testing". This is a live map used by a large number of people and organizations.

117896222 almost 4 years ago

Hello.
There are a couple of mistakes in your edit.
You tagged intersection as "Marked Crosswalk". While in plain English that's what we call it, in OSM it has a slightly different and specific meaning.
"crossing=marked" is specifically for crosswalks WITHOUT traffic lights(ie intersections with a stop sign).
For crosswalks with traffic lights, it's tagged as "crossing=traffic_signals"
You can read more about it at crossing=* 👍

117861524 almost 4 years ago

People too often ignore or forget to tag that. :( But without that tag data consumers can misinterpret that there are twice as many sidewalks or give confusing or sub-optimal directions.

117861524 almost 4 years ago

Hello.
When mapping sidewalks as separate paths, please don't forget to tag related road segments with "sidewalk:left/right/both=separate".
---

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

117849751 almost 4 years ago

You'd map it either by putting all the relevant into in tags on the building polygon itself OR on POI nodes and keep building with just minimal unique info.
In this case name and operator tags has duplicate info on both building and POI.
Also generally it's good to position nodes close to where the main entrance is. That way navigation and routing and search software would be able to direct people to where they should go

117849751 almost 4 years ago

Hello.
Please note that the way you map fire houses goes against "One feature, one osm element" guideline as documented here: osm.wiki/One_feature,_one_OSM_element
Ignoring this guideline can make data less useful to consumers, such as duplicate search results or only 1 feature gets update with a more current information.
---

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

117825226 almost 4 years ago

destination:lanes and turn:lanes with "none" in them is a standard and documented way to tag lanes as can be observed in turn=* and destination=*
If such tags cause problems in your routing software, you'd need to fix your routing software rather than start deleting tags all over the world.
I'm going to revert this edit.

117825226 almost 4 years ago

As the linked article states: "The phrase usually refers to renderers, but it also applies for routing and geocoding and other uses of the data."

117825226 almost 4 years ago

We?
If these tags are not outright wrong and accurately represent relevant data, isn't this an issue with whatever software you use to build those trips?
It seems like you are doing this osm.wiki/Tagging_for_the_renderer
---

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

117825226 almost 4 years ago

Hello.
Could you please elaborate why did you remove these tags?
---

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

117773510 almost 4 years ago

Is there a name of this pizza place? You filled in all that info beside the name..
---

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

117725209 almost 4 years ago

Yet again NYMM, if you are going to be conducting business on OSM, at least learn how to properly add tags! The way you entered it now is INCORRECT and going to be reverted.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/117725209

117660808 almost 4 years ago

Hello.
I do not see this pond on any of the available satellite imagery. As such it will be deleted.

Please note that intentionally mapping non-existing features on the map is considered vandalism.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/117660808

117660318 almost 4 years ago

Hello.
It seems like you move an address node in the middle of a golf course. That is most definitely incorrect. As such this edit will be reverted.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/117660318

117659927 almost 4 years ago

Hello.
It is inappropriate to use "name" field to describe an object. Please see this article for a more detailed explanation: osm.wiki/Names#Names_are_not_for_descriptions
---

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

117659784 almost 4 years ago

Hello.
Could you please elaborate why did you draw building outline that match any of the available satellite imagery?
Additionally, since you mapped this as a Chase bank, iD editor has a preset for it with a lot of necessary tags automatically filled in.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/117659784

117575677 almost 4 years ago

Hello.
When mapping sidewalks they should be tagged as "footway=sidewalk
highway=footway". rather than just footway. iD editor has a specific preset for sidewalks, so you could easily use that.

Additionally, when tagging intersections, "marked" crossing type specifically refers to crosswalks without traffic lights. The ones with traffic lights should be tagged as "crossing=traffic_signals" rather than "marked". 👍
---

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