AR_Mapper's Comments
| Changeset | When | Comment |
|---|---|---|
| 153948651 | There is no need to add restrictive access tags when they are incorrect; if a road is narrow the "narrow=yes" tag is appropriate. |
|
| 153976076 | Please give your changesets more descriptive descriptions; "minor" for changes which span across an entire town doesn't help with understanding what your intentions were here. |
|
| 153973309 | Hi, In future please do not make changes just so they "show up". |
|
| 152463050 | Thanks! I'll check them out |
|
| 151528377 | Hi. This source is not publicly accessible to review. Regardless, Ingress is not an acceptable source of information for edits; Only sources with compatible licenses (usually in the public domain) may be used as bases for adding OSM data. |
|
| 151315812 | Hi. Google maps is not an acceptable source of information for edits; Only sources with compatible licenses (usually in the public domain) may be used as bases for adding OSM data. |
|
| 152213773 | Hi, there is no need for any personal attacks here. Edits to remove vandalism from the map are not "rude". As your edits are unverifiable and are consistent with common vandalism from Pokémon Go players the previous changeset was reverted. A beach has different features/requirements which define it, specifically "stretches of sand at the coast formed by wave action from the ocean", compared to a patch of mud/pebbles/sand the bank of a pond/lake or a certain type of surface. I understand you would like some beaches to appear in Wigan, so the next time Niantic update their map you might get access to a specific Pokémon; however, these are not beaches. They are either mistagged or are better defined by either mud or shingle. Please fully educate yourself on the following wiki pages to avoid further reverts on these edits by myself and other mappers who are upholding the integrity of the data in the map. |
|
| 151513856 | Reverted by changeset/151528562 |
|
| 151476614 | Reverted by changeset/151528562 |
|
| 151315812 | Reverted by changeset/151527331 Please review natural=beach |
|
| 151154259 | Reverted changeset/151182443 |
|
| 142974190 | Thanks! I thought I'd fixed them all but it was my first time working with this type of relation. |
|
| 139523908 | Reverted to avoid any potential copyright issue. Will be remapping without use of copyright material. |
|
| 139783630 | Reverted to avoid any potential copyright issue. Will be remapping without use of copyright material. |
|
| 139783671 | Reverted to avoid any potential copyright issue. Will be remapping without use of copyright material. |
|
| 140710776 | Reverted to avoid any potential copyright issue. Will be remapping without use of copyright material. |
|
| 141033531 | Reverted to avoid any potential copyright issue. Will be remapping without use of copyright material. |
|
| 119816211 | Sorry @jennycook but I totally disagree - osm.wiki/Bicycle is an absolute nightmare to decipher. the vast majority of these which have been designated as "cycleways" here are simply sidewalks to a road add no value and just clutter the map. It seems that this is just another "pick and choose your help article of choice to support your view" conversation. |
|
| 119816819 | @tastrax unfortunately someone else reverted other changes I made which subsequently pushed these changes out of sync. This discrepancy / lack of clear guidance about paths alongside roads being mapped is getting ridiculous. and why I rarely do anything on OSM. People seem to pick and choose the help link which supports their view. I'll try and fix this issue now |
|
| 92601276 | Fixed in 106231744; has been replaced with relevant cycleways and footway has been used where the pathing is too small to accommodate both cycles and pedestrians. |