ZeLonewolf's Comments
Changeset | When | Comment |
---|---|---|
142992723 | over 1 year ago | 'I have reverted this changeset for the following reason:
|
142992611 | over 1 year ago | 'I have reverted this changeset for the following reason:
|
142992544 | over 1 year ago | 'I have reverted this changeset for the following reason:
|
142992471 | over 1 year ago | 'I have reverted this changeset for the following reason:
|
142992166 | over 1 year ago | 'I have reverted this changeset for the following reason:
|
140794401 | almost 2 years ago | In this car case, a huge piece of the loop was missing, so even a trivial check would have caught it. |
140794401 | almost 2 years ago | The algorithm for boundary validity is not hard. I do it in Streetferret. You just gather up all the member ways and make sure each endpoint has a matching endpoint on the same or another way. Then you check that all the inner loops are outside an outer loop. In any case, there is definitely a QA site with boundary validity. |
135174608 | almost 2 years ago | On the satellite view it looked expressway-like to me, but if you have a better local understanding feel free to adjust it. |
140794401 | almost 2 years ago | This boundary is broken (osm.org/relation/119236) This was the last edit to touch it. I'm sure this bot edit wasn't the one that broke the boundary, but now it's hard to tell what the culprit was. It would be ideal if a bot edit working on boundaries might also check to see if the boundary is valid. |
140199138 | almost 2 years ago | This boundary is broken: osm.org/relation/37376 |
142291799 | almost 2 years ago | Should be a primary expressway instead. |
141349127 | almost 2 years ago | landuse=forest and natural=wood means the same thing, trees. While some mappers have tried to use =forest to mean managed forest, many others use it as a synonym. I personally think it's a waste of time to draw a distinction. I think natural=wood where trees are present is a perfectly acceptable way to map wooded areas. |
141234953 | almost 2 years ago | Hi, had to revert this change to highway classifications. The current documentation is at: osm.wiki/Rhode_Island/Highway_classification which is the Rhode Island specific implementation of osm.wiki/United_States/2021_Highway_Classification_Guidance Everything is subject to debate of course, but the Mt Hope Bridge upgrade and the motorway_link change near Sprague Street are not right. Motorways have pretty specific definitions, and _link roads need to connect to roads of their parent types. |
141402069 | almost 2 years ago | I surveyed this area on September 10th. Here's my GPS trace:
|
141402001 | almost 2 years ago | Additional discussion on osm.org/changeset/141402069 |
141402069 | almost 2 years ago | Aside from above, the reason that I marked this area as access=no, is because it is currently scheduled for demolition, and it is surrounded by a tall chain link construction fence. I trust that this explanation is sufficient and that I don't need to run out and gather more photographic evidence as I did on the other changesets on the island that I reverted. I would appreciate in the future, if you would have a discussion when reverting recent edits if you are not personally putting your eyeballs on the thing you are changing. I live in this area and my edits are based on personally visiting these locations on the ground. |
141402069 | almost 2 years ago | Also, Bing Maps Aerial is the wrong imagery layer for this area. You should be using the March 2023 Rhode Island aerial imagery, which is the most up today. |
141402069 | almost 2 years ago | Please explain how you came to determine that this road is accessible. I personally surveyed it. |
141402001 | almost 2 years ago | Please explain this edit and how you came to assess that this street is accessible. |
140563540 | almost 2 years ago | This road has a sign at the end that reads: HARBOR VIEW DRIVE
Therefore I am restoring the private access tagging and mapping the gate and inscription. |