OpenStreetMap
CurlingMan13's Comments
| Changeset | When | Comment |
|---|---|---|
| 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:
|
|
| 148879092 | Why are you continuing to change service roads incorrectly to cartpaths? Do not change things to what they are not just for your silly golf game. Do not map for the renderer...
|
|
| 148879018 | 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:
|
|
| 148857768 | I am not sure. Thanks for the info. I was wondering who the actual heck tries to build a lavish and water demanding golf course community in the middle of the desert. Hahaha. The roads have started construction, so I think construction tag is more appropraite than proposed since the ground has actually been broken. Thoughts? Now, I recognize there are a few segments where the road hasn't been built/paved like the road *into* the community. I was assuming those segments were completed since imagery was taken. I'll adjust it a bit more tonight based on imagery to construction and lower road status from tetriary to minor/service as appropriate. |
|
| 148862072 | Why did you delete all these features?
|
|
| 148860709 | 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. |
|
| 148861621 | 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. |
|
| 148852355 | Do not "lollipop areas to simulate a hole. Multipolygon relations should be used instead. |
|
| 148845065 | Do not partially overlap landcovers (fairway and putting green) for example.
|
|
| 148837948 | Couple things:
I have resolved this for you for this changeset.
|