CurlingMan13's Comments
| Changeset | When | Comment |
|---|---|---|
| 139635106 | over 2 years ago | Please use complete words in your changeset comments. What did you change, and why?
|
| 139665520 | over 2 years ago | Ummmm.... Why did you delete the water?
|
| 139667386 | over 2 years ago | The cartpaths should be added as paths and cartpaths, not highway=service. |
| 139662238 | over 2 years ago | Don't lollipop areas. Multirelations should be used to cut out "holes" of a feature, or they should just be layered. The thin areas to connect it, as you have done on the sand bunkers is incorrect. I have mentioned this multiple times before, but you continue to do it with no regards. As I have done with other changesets, this one and the others with the same issue will either be reverted or cleaned up, but probably the former. |
| 139668693 | over 2 years ago | I have mentioned this multiple times, and you still have not acknowledged, responded or stopped doing it. Do not create "lollipops" with the landuse/landcover areas. Multi-polygon relations should be utilized.
|
| 139682723 | over 2 years ago | Instead of smashing the keyboard, can you please leave a more detailed changeset comment/description? What did you change, and why? Thanks.
|
| 137618522 | over 2 years ago | Best option is to get it added on OpenHistoricalMaps (OHM). I believe the best way to do it is to do it in JOSM. I think there is a wiki page on how to do it. I am not well-versed on OHM and have only moved one rail over on Staten Island, but I did that manually. Start and end dates can also be added, adding even more control because the lifecycle can even be changed from "proposed" to "construction" to "active" to "disused" to "abandoned" then "razed" and finally removed all together. The timeline can then be scrubbed and the status change can be viewed over time whoch is even cooler! |
| 139500523 | over 2 years ago | Don't overlap areas. They should be touching and not overlapping, or the smaller area should be fully contained within the bigger one. I have cleaned it up to resolve the error flags caused by these edits.
|
| 139453237 | over 2 years ago | I took a look at the edits. It looks pretty good. Keep up the good work.
|
| 139461152 | over 2 years ago | Landcover shouldn't overlap, such as the fairway and the green. One should be fully within the other, or they should be snapped to each other. The issue is that the renderer and database has no clue which is "on top" of the other. Example one that has been fixed:
|
| 138149569 | over 2 years ago | Please don't falsely change the map. Even if they did, most services don't get their data that quickly from OSM.
|
| 139396959 | over 2 years ago | Is there a reason you deleted all these golf features?
|
| 139320537 | over 2 years ago | So access tags should be used. It would prevent someone from inadvertently readding it, despite it being "closed"
|
| 138962353 | over 2 years ago | "Virtual=yes" is a non-standard tag with no OSM wiki page for it. Can you elaborate on what this tag means and why it should exist? Thanks. |
| 119306979 | over 2 years ago | I know this was a while ago, but please do not name buildings with descriptive tags, such as "abandoned" or "destroyed" when that is not their official name, just a description which can best be placed in a tag field. |
| 139322567 | over 2 years ago | Please use better changeset comments. What did you change and why? You can read more here:
|
| 139352010 | over 2 years ago | Don't add names to the features. These are descriptive tags. I have removed the names from all areas in this vicinity. |
| 137709817 | over 2 years ago | It was not to revert your work. It was an attempt to cleanup after this changeset by another user:
If there were intersecting polygons before his edits, then that is what it went to. |
| 139269780 | over 2 years ago | Full name should be used. "dr" should be spelled out as "Drive" Intersection roads NEED to be connected to the road. I have resolved this for you. |
| 139270470 | over 2 years ago | Access tags should be used such as "access=no", instead of deleting it since it will likely be readded, despite it being closed and the knowledge of closure won't be shared/saved.
|