CurlingMan13's Comments
| Changeset | When | Comment |
|---|---|---|
| 149071435 | The paths that go over water should be mapped with bridge tags, as appropriate. |
|
| 149072766 | Do not delete just to readd the features...
|
|
| 104152296 | Is "Public Fishing Access - Easement of Private Property" the actual name? It appears descriptive and unlikely to be signed as such. |
|
| 148994419 | Do not partially overlap areas, such as the green and fiarway.
|
|
| 148994419 | Do not partially overlap areas, such as the green and fiarway.
|
|
| 148955837 | Multipolygon relations should be used instead of this abstract art of areas to try and create "holes" in an area.
|
|
| 148938913 | Please do not delete features just to remap them, especially when they were mapped better before you tried to redraw them.
|
|
| 145801673 | They are continuing to delete and readd. https://osmcha.org/changesets/146032152
|
|
| 146032903 | Please use "Q" to square the buildings.
|
|
| 148938994 | You can use multiple segments of lines to create a network of cartpaths, rather than one long snake folidng back upon itself. You can also add tunnels for the segments that are tunnels beneath the road. I have corrected this for you.
|
|
| 148939970 | do not map each individual tree as natural=wood. nodes should be used instead if individual trees are desired to be mapped.
|
|
| 148904058 | As mentioned before, do not fold landcover areas back upon themseleves, as you did for the sand trap to create "holes". Multipolygon relations should be used instead.
|
|
| 138198502 | Why did you change a lake to a water hazard? This is not correct. Do not make edits purely for your golf game. This damages data. |
|
| 145136788 | Why did you change a lake to a water hazard? This is not correct. Do not make edits purely for your golf game. This damages data. |
|
| 148888757 | Do not partially overlap landcovers (fairways and greens). This has been mentioned multiple times. Please acknowledge receipt and understanding of this comment. You have not acknowledged previous comments or responded, yet are continuing to map with the same mistakes. I have not received a DM or other form of communication explaining why you are continuing to map in this manner. Doing so may result in referral to DWG for further action.
|
|
| 148892462 | As mentioned previously, do not partially overlap areas...
|
|
| 148887257 | Access=private was already tagged to the ways. This is in accordance with OSM guidelines. Do not delete ways/features just because they are private. This is not the solution. You can read why here:
|
|
| 148890250 | Do not partially overlap areas.
|
|
| 148874275 | Do not partially overlap areas...
|
|
| 148879092 | Do not "lollipop" areas to create simulated holes in an area. You should use multipolygon relations instead. This changeset has been reverted in part or full to remove "fake holes" in the area. I highly suggest you review the "Common Mapping Pitfalls" section of the wiki prior to making further edits:
|