ZeLonewolf's Comments
Changeset | When | Comment |
---|---|---|
101341126 | over 4 years ago | Imported as a way, needs to be a relation. Currently fixing... |
101523781 | over 4 years ago | Thanks! We're chatting about it in the OSM US Slack (https://slack.openstreetmap.us/) -- feel free to join us at #local-new-mexico |
101523781 | over 4 years ago | If there is a new shapefile available, and you can point me to it, I'd be happy to update the boundary with the corrected geometry. |
101523781 | over 4 years ago | Hi, this change broke the boundary to Los Alamos: osm.org/relation/171160 Are you able to fix it or should I revert the change? |
39067410 | over 4 years ago | Where does the boundary come from? How can it be verified? There must be some source, as I assume you did not invent it :) |
98319639 | over 4 years ago | Hey, I noticed you used the tag riverbank=water which isn't a tag normally used (in fact it was the only one in the database!) -- it should be natural=water + water=river instead. |
101821162 | over 4 years ago | Hey, so this change actually broke the Menomonie / Town of Menomonie boundary polygon. (See missing piece of osm.org/relation/251653) Unfortunately, iD doesn't give any warning to mappers when this happens (see bug report https://github.com/openstreetmap/iD/issues/8286) Also, just wanted to throw out an invitation to the OpenStreetMap US Slack! Link is
|
102255646 | over 4 years ago | Intended changeset comment: tagging quonset huts |
99618961 | over 4 years ago | Are you aware that you added a building in California to a water relation in New York? :) |
37636064 | over 4 years ago | Congratulations on being the first to use the new human tagging scheme! |
74192539 | over 4 years ago | Congratulations on being the first to use the new human tagging scheme! |
101425710 | over 4 years ago | Hello AmazonMapMap27, this edit has created a gap in the Eastport boundary (relation 175742). Are you able to fix this? |
101945534 | over 4 years ago | Hi there! So, I'm actually working through a defined procedure to clean up river tagging nationwide and I'm currently working California. This was the first step which is to look for untagged river areas and give them the missing water=river tag. The link below describes the procedure I'm using, and in California I'm working from north to south. osm.wiki/User:ZeLonewolf/Procedure/River_modernization Feel free to jump on the OpenStreetMap US Slack (https://slack.openstreetmap.us/) channel #local-california if you want to chat more about the project! |
101938517 | over 4 years ago | Missing comment is: "adding lake tagging" (JOSM bug: https://josm.openstreetmap.de/ticket/20690) |
99399382 | over 4 years ago | Hi, just a heads up, this edit broke the Seaford boundary relation (osm.org/relation/175640) |
101916258 | over 4 years ago | JOSM mangled my changeset comment. Should be: change "Brick" to "brick". |
101916282 | over 4 years ago | JOSM mangled my changeset comment. Should be: change "Brick" to "brick". |
101916302 | over 4 years ago | JOSM mangled my changeset comment. Should be: change "Brick" to "brick". |
101894645 | over 4 years ago | Corrected changeset description: Upgrading tagging and fixing geometry errors on Washington's river system, as discussed on the OpenStreetmap US Slack, channel #local-washington-state and as documented at osm.wiki/User:ZeLonewolf/Procedure/River_modernization |
101888396 | over 4 years ago | Merging duplicate nodes |