gpserror's Comments
| Changeset | When | Comment |
|---|---|---|
| 132020418 | almost 3 years ago | This changeset also duplicates a lot of existing roads, please check. May need to revert. |
| 132020411 | almost 3 years ago | hi, it looks like your changeset added a bunch of overlapping ways perfectly on top of existing ways, could you look into this? |
| 132015955 | almost 3 years ago | Hi, it looks like your changeset added a bunch of road violations. Take a look at note/3543755 and review the changes? |
| 132053650 | almost 3 years ago | https://www.greeleytribune.com/2021/07/24/carr-post-office-closes-after-failed-air-quality-test-speculations-about-meth-operations-arise/
|
| 132053650 | almost 3 years ago | Where is the post office now? |
| 131748939 | almost 3 years ago | BTW one such error that showed up is way/440823644 - I'm not sure what this used to be but it's definitely not a road, I think it used to be a boundary of sorts but it was changed and now I don't know what it represents. |
| 131748939 | almost 3 years ago | hi, thank you for your contributions, however I've noticed there were a lot of errors introduced to the map due to your contributions. If you could, could you fix them? perhaps these changes need to be reverted back to a previous state if you're not sure on how to fix some of the problems introduced. |
| 131821702 | almost 3 years ago | ugh we clashed again, this time i saved before yours but no conflicts as I didn't delete any nodes... |
| 131483833 | almost 3 years ago | should it be yes @ (05:00-22:00) ? will add in meantime |
| 123911229 | almost 3 years ago | Hi, just wanted to let you know I fixed a node you accidentally dragged to an improper location, just be careful when scrolling around in the map when editing. No further action needed. New location of the node is node/10303495305 . |
| 128768449 | almost 3 years ago | I was indeed very hesitant to change this road because I was not sure of the actual road name ad tried to contact the initial author of the road (through the other changeset) since he appeared to be local and knew about it. Oh well, I do have an OSM note on the area so someone local or perhaps privileged to the data could fix it for certain,but as of now this might be a mistake. |
| 128768449 | almost 3 years ago | Hi, I made a comment in changeset/127859021 about the previous editor to this road here but now I have some questions about this change. Seems you just deleted the overlapping road, but is this east-west road really called victorville drive or is it prismo lane? |
| 130298153 | almost 3 years ago | Hi, it looks like you accidentally moved node/595490659 and made a mess of the highway... if you could fix it in the next few days that would be great. |
| 130005821 | almost 3 years ago | Hi, just wanted to let you know, these cul-de-sacs at the end of residential roads are not roundabouts and shouldn't be marked as such. This isn't so much of a problem as when the roundabout was marked as such, the default oneway direction is the direction of the way, and it's wrong now for drive-on-right areas... Let me know if know if you this doesn't make sense or if you need me to fix it. Thanks! |
| 128528184 | about 3 years ago | Hi, thanks for your contribution. I unfortunately had to end up deleting a good portion of the footpath you added as it overlapped an existing road - roads are acceptable to walk on by default so you don't need to explicitly mark a footpath on that road. You could also explicitly tag that pedestrians are okay on the road, or you could create a hiking path relation. Let me know if you want more details. |
| 129090956 | about 3 years ago | For my needs I find this to be a serious violation, curious what the policy on fixes/reverts should be on things like this? Would be nice to make sure this doesn't happen again, even if it's pretty easy to do accidentally especially in iD if one has a slow machine. In fact I wish the iD developers speed up scroll performance to help prevent things like this... |
| 129090956 | about 3 years ago | I spotted a mistake in this changeset, and who knows how many more. node/8234272754 was dragged to an improper spot. I was about to fix it but this is a systemic problem. |
| 128293630 | about 3 years ago | No problem, it happens. TheDutchMan13 note/3439389 ended up fixing it! |
| 128508814 | about 3 years ago | I went ahead and fixed these issues. Please be careful next time. |
| 128754116 | about 3 years ago | just wanted to let you know I ended up cleaning up this changeset to clear up the warning. |