Glassman's Comments
Changeset | When | Comment |
---|---|---|
165967229 | 3 months ago | Thank you for your edit. I reviewed your work and it looks good.
|
165968539 | 3 months ago | Thank you for your edit. I reviewed your work and it looks good.
|
165967445 | 3 months ago | Thank you for your edit. I reviewed your work and it looks good.
|
165967283 | 3 months ago | Thank you for your edit. I reviewed your work and it looks good.
|
165914558 | 3 months ago | Thank you for your edit. I reviewed your work and it looks good.
|
165912913 | 3 months ago | Thank you for your edit. I reviewed your work and it looks good.
|
165912507 | 3 months ago | Thank you for your edit. I reviewed your work and it looks good.
|
165089410 | 3 months ago | Can you explain why you deleted valid foreign names at Thessaloniki railway station, despite the name “Thessaloniki” being widely translated? Thanks DWG
|
165817442 | 3 months ago | Check out the wiki page on removing roads on private property. osm.wiki/Why_we_won%27t_delete_roads_on_private_property. While the wiki page talks about roads, the same argument can me made for sidewalks and paths. Please add the ways back. |
165769441 | 3 months ago | I have reverted this changeset. The road exists on the counties iMap server. See https://gismaps.kingcounty.gov/iMap/ As I said in a previous changeset of yours, just because the feature is on private property it can be added to OSM. In this case, it is a public road. If you disagree, please leave a comment
|
165817442 | 3 months ago | The path exists on imagery. Why was it removed? Note - even though the property is privately owned, we can document features that exist there. You can add the tag ownership=private as well as access=private if the footway has no trespassing signage.
|
165817313 | 3 months ago | Question - your changeset comment said this is a private residence yet the edit removed a path. Why did you remove the path? Does it not exist?
|
165777176 | 3 months ago | This app requires that I review everything as good or bad. There is no in between. When I mark it as bad, it may only be that it doesn't fit the OSM tagging scheme. I'll leave a changeset comment with what I found. It looks like you dragged to nodes. I have fixed them. Also, when individual trees are tagged, they should not be part of a tree row. I removed the tree rows you added.
|
165492965 | 4 months ago | After reviewing what you posted, I have to agree with you that what you did was correct. I do think that the the tag crossing:markings=* should be added as suggested by the wiki page you referenced. I'm going to update the crossings as I have time. Feel free to jump in. And in the future, please including the crossing:markings tag as well. Thanks |
165651593 | 4 months ago | The two nodes in Seattle almost look the same. You could just add both shop and gallery to one tag. It would also help your SEO score to add your website.
|
165478859 | 4 months ago | Why did you remove the cuisine=coffee_shop from Cherry Street Coffee House?
|
165492965 | 4 months ago | Check out the wiki at osm.wiki/Tag:crossing%3Dtraffic_signals.
|
165385675 | 4 months ago | node/12783765563 has both a blue box and an ALRP device. From the shadow, it does appear that there is something up a ways. If both exist, then there should likely be two different nodes, probably close together.
|
165492965 | 4 months ago | Help me understand why you replaced crossing=marked with crossing=traffic_signals? It is wrong. Unless you can convenience me that your change is correct, my only real alternative is to revert all of your changeset that made this change. I do see come good additions, but changing the crossing tag is just wrong.
|
165497197 | 4 months ago | Reverted. OSM is a live database. We do have a dev server. Let me know if you need more info on it.
|