akadouri's Comments
| Changeset | When | Comment |
|---|---|---|
| 124106428 | over 3 years ago | Thank you for contributing to OSM! If you are actually NYC Parks it's great to see the department join the OSM initiative. If you'd like to reach out to local mappers there is a mailing list - https://lists.openstreetmap.org/listinfo/talk-us-newyork as well as a Slack channel - https://slack.openstreetmap.us/! It looks like you're missing the `building=` tag on the updated feature. way/278325868 `building=civic` may be appropriate here, building=civic There was also already a node for this facility, node/2020487653 You may want to move the relevant tags from that node to the building and delete it. I would also add `swimming_pool=yes` to the new building feature. Happy mapping! |
| 122679584 | over 3 years ago | Here is another feature that you mapped as two curbs but Bing Aerial shows a single curb. way/1072037042#map=19/40.66842/-73.95577 |
| 123401854 | over 3 years ago | Hello, please be aware that not all of the crosswalks in this area have two curb cuts per corner, some have one. See the following example for this way -
way/1077132723#map=18/40.66317/-73.98081 This is why I have been slow to map this area :/ |
| 122689589 | over 3 years ago | It's not an accepted tag, it's not even proposed yet. I'm not sure if it's the best way to document curb extensions but I think it would be ok as a marker to remember where they are for now. I used Chrome's "Translate This Page" feature to read that wikipage. Talking about it a little over here -https://osmus.slack.com/archives/C6E4S4CQG/p1655941475239799 |
| 121769688 | over 3 years ago | Thanks for the response, the sidewalks/pedestrian mapping has been pick up steam the past year or two and will definitely help people out. |
| 121769688 | over 3 years ago | Hello, thanks for mapping so many sidewalks and crosswalks! I saw you added `tactile_paving=partial` to this node node/8132573641 and was wondering if you did so because of the discussion in the OSM-US Slack a couple days ago or if there was a different situation on the ground there. I added a couple `tactile_paving=partial` nodes to represent grooved pavement (vs blister pavement) but am wondering if that is a good idea considering all the nodes in NYS are either tactile_paving=yes or no. |
| 121597508 | over 3 years ago | Hello, I'm not quite sure a tree line is the best way to map the trees in those back yards. There isn't exactly a straight line of trees there. |
| 119440447 | over 3 years ago | Yeah I'd just remove them. |
| 109699833 | over 3 years ago | Please note that "opening_date" refers to when a building will open in the future (usually used with things under construction) while you probably meant to use "start_date" which refers to when a building was built in the past. |
| 119440447 | over 3 years ago | Both of these features have "opening_date" tags that have passed (fall 2021). Do you know if there's a new expected date? |
| 119126827 | over 3 years ago | Hello, please use crosswalks if you are going to map sidewalks. See the area around this point in Flushing for an example without curbs mapped: node/42836761 And this area for an example with more detail/curbs mapped:
|
| 119002167 | over 3 years ago | I'm not sure, I guess it could have been painted since the last re-pavement. It doesn't seem like it's common enough around here to worry about having to tag both cases. I guess I'll slowly re-tag `crossing=marked` as `crossing=traffic_signals` as I come by them since that does seem to be the right tag despite so much of the city being `crossing=marked` |
| 119002167 | over 3 years ago | Here is one in Flushing, way/936536474 It is pretty uncommon, a few of the other one my query flagged were improperly tagged. It looks like there were some proposals like this one to separate the marked/unmarked tags and signal control but it doesn't look like they ever got officially approved. osm.wiki/Proposed_features/crossing:signals |
| 119002167 | over 3 years ago | I have updated the ones I could confirm. osm.org/edit?way=610035984 I have no doubt made this mistake many times in the past, I could have sworn there was a way to notate both the paint status and traffic control status... |
| 119002176 | over 3 years ago | I split this way, so it copied whatever tags were on it. |
| 118804853 | almost 4 years ago | Hello, Is there a reason to change all these tags to have the "contact:" prefix? It does not seem necessary. |
| 118216943 | almost 4 years ago | Getting a head start huh! Should we set `operator:wikidata=Q1058767` on these on the DOT racks? (https://www.wikidata.org/wiki/Q1058767) I'm not sure there's a better way to conflate the various operator tags (DOT, NYC DOT, NYC, etc). |
| 116204048 | almost 4 years ago | This discussion bled into the OSMUS Slack.
I'm inclined to say we keep these features and style of mapping due to the additional information each representation captures. In the case of ways for routing/accessibility and the areas for micromapping detail. |
| 115741447 | almost 4 years ago | Hello, thanks for contributing your first edits to OSM! When a business closes the prefix "disused:" is can be added before the old tags. disused=*: In this case it would be "disused:name=Nino's Pizza" and "disued:amenity=restaurant", and so on for whichever other tags. Opening_hours refers to the time the restaurant is open, in this case they would be the hours for the new opening times. opening_hours=* OSM isn't the best at keeping history, often people just delete the old tags and replace them with the new. |
| 115496220 | almost 4 years ago | Thank you both! |