emersonveenstra's Comments
| Changeset | When | Comment |
|---|---|---|
| 152566640 | over 1 year ago | Hi there, You created two ways with no tags: way/1291622133 and way/1291622235. Could you please tag those? Thanks! |
| 151611544 | over 1 year ago | Hi there, You created way/1285082864 with no tags, could you please go back and tag it? Thanks! |
| 152435588 | over 1 year ago | Hi there, You created way/1290544706 with no tags, could you please go back and tag it? Thanks! |
| 152134798 | over 1 year ago | Hi there, You created way/1288766071 with no tags, could you please go back and tag it? Thanks! |
| 152249185 | over 1 year ago | Hi there, You created way/1289387852 and way/1289387851 with no tags, could you please go back and tag them? Thanks! |
| 152580956 | over 1 year ago | Hi there, Just to double check, adding highway=construction means that the road is physically unusable for all forms of transport (highway=construction). Since there's driveways and houses attached to some of these sections (like way/943843950 connects to way/1291714425), I wanted to make sure that it is truly unusable, and not something like "Road Closed to Through Traffic" |
| 152596469 | over 1 year ago | Hi there, I'm curious why you're adding empty nodes to roads? It's not technically wrong, but I don't see the reason behind it |
| 152553804 | over 1 year ago | It does mean that OSMAnd won't know about it, but presumably there's a posted/signed detour that people can follow and OSMAnd will re-route them. You could also do conditional restrictions (osm.wiki/Conditional_restrictions), so for example adding "access:conditional=no @ (2024 Jun 13 - 2024 Aug 30)" would tell OSMAnd not to route through that intersection for those dates |
| 152553804 | over 1 year ago | Hi there, Please never disconnect roads like this. If something is closed long term for construction, you need to use construction tagging: highway=construction But note that it's not recommended to tag construction that will take less than 6 months. |
| 152472969 | over 1 year ago | Hi there, Looks like you mistakenly added the name of the path as the surface tag here: way/578679619 Could you please fix this? Thanks! |
| 152188479 | over 1 year ago | Also, for waterways like way/1289064499, you need to use layer, not level (see tunnel=culvert?uselang=en#How_to_map). Would you mind fixing these? Thanks! |
| 152188479 | over 1 year ago | Hi there, I removed natural=ridge+ridge=esker from way/17813323/history since it seemed accidental, let me know if it was on purpose |
| 151908649 | over 1 year ago | Ah, I see, so probably best to add that rec ground area back and put the address on that instead of the slipway |
| 152252116 | over 1 year ago | Hi there, Looks like you accidentally tagged the boundary as paved instead of the road. To avoid this, you can go to Map Data -> Map Features and uncheck Boundaries |
| 151908649 | over 1 year ago | I did, I assumed the landuse=recreation_ground was tagging for the renderer and a duplicate of the slipway since i didn't see any features listed in landuse=recreation%20ground?uselang=en, it seemed to be just covering the boat launch and parking. If I'm wrong, then I'll add it back |
| 151868733 | over 1 year ago | Hi there, Are you sure you meant for way/1286901707 to be a pedestrian highway? |
| 151735388 | over 1 year ago | Hi there, Is the entire section of the street actually closed (i.e. impassable)? |
| 151694512 | over 1 year ago | sorry, parking spaces, not parking lots |
| 151694512 | over 1 year ago | Hi there, Looks like you typoed the capacity value on several of the parking lots like way/1285756393 Could you please go back and fix these? Thanks! |
| 151653794 | over 1 year ago | Hi there, In OSM, it's generally incorrect to map a building on top of another building. If the condos are actually separate buildings, could you please delete the building ways that span the entire outside, like way/893851126? Thanks! |