b-jazz's Comments
| Changeset | When | Comment |
|---|---|---|
| 163508500 | Hello fellow golf course mapper. The lines that define Fairways and Greens should never intersect or partially overlap each other and we noticed that they are overlapping in one or more of the fairway/green pairs in this changeset. If there is no obvious fringe around the green, the fairway should butt up against the green and every node between them should be *shared*. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create them with your map editor). Please read the wiki for visual examples an instructions on how to better map golf courses: leisure=golf_course#Common_mapping_pitfalls. If you have any questions, please reply here and I'll gladly help clarify things. Thanks! |
|
| 163289790 | The lines that define Fairways and Greens should never intersect or partially overlap each other. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create
|
|
| 163469108 | The lines that define Fairways and Greens should never intersect or partially overlap each other. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See
|
|
| 125253035 | Whoa! Cool! Thanks archpdx for doing the work on this. |
|
| 163446770 | ◉ The lines that define Fairways and Greens should never intersect or partially overlap each other. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create them with your map editor). If there is no obvious fringe, the fairway should butt up against the green and every node between them should be shared. Please read the wiki for visual examples and instructions on how to better map golf courses: leisure=golf_course#Common_mapping_pitfalls |
|
| 163424108 | Hey there malifica, I see that you edited one of the fairways incorrectly. If you look at way/1247954535, you added the tag of "golf=fairway" to a multipolygon. It's not uncommon to think that is a correct tag, but the multipolygon already defines what inside that boundary is a fairway and what is a green. So it correctly identifies just the fairway as a fairway, but you have come in and said that *everything* inside that boundary, including the green, is to be considered a fairway. Please be careful in the future when modifying objects that are multipolygons. Thanks. |
|
| 163421269 | The lines that define Fairways and Greens should never intersect or partially overlap each other. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create them with your map editor). If there is no obvious fringe, the fairway should butt up against the green and every node between them should be shared. Please read the wiki for visual examples and instructions on how to better map golf courses: leisure=golf_course#Common_mapping_pitfalls |
|
| 163414238 | Thanks for adding golf information to the map. I wanted to let you know that you have added what is called a "lollipop" to the course and those aren't supposed to exist. See the wiki at leisure=golf_course#Common_mapping_pitfalls for how to correctly map those situations. |
|
| 163384888 | Thanks for the additions. A couple of comments to improve your mapping if you're interested.
You can find more information at the golf_course wiki page: leisure=golf_course#Common_mapping_pitfalls |
|
| 163163098 | That’s sad to hear. They are 100% wrong. Can you point me to where you heard so that I can prevent this misinformation from spreading any further? |
|
| 163259458 | As mentioned in changeset/162300773, you shouldn't be reusing the nodes when the fairways extend all the way around the green. Some sort of fringe should be left or the fairway should come up short and butt up against the green instead of surrounding it. If you need further clarification, please leave a comment here with any questions and I'll be glad to help out. |
|
| 163339578 | The lines that define Fairways and Greens should never intersect or partially overlap each other. If there is a fringe around the green that is similar to the fairway, the fairway should extend around the green and the two objects should be merged together into a multipolygon (See osm.wiki/Relation:multipolygon for how to create them with your map editor). If there is no obvious fringe, the fairway should butt up against the green and every node between them should be shared. Please read the wiki for visual examples and instructions on how to better map golf courses: leisure=golf_course#Common_mapping_pitfalls |
|
| 163226558 | Hey there Nat,
|
|
| 163163098 | Overlapping fairways and greens is bad, but so is "almost touching". What you should be doing is *sharing* the nodes between the green and the fairway. Take a look at the wiki (leisure=golf_course#Common_mapping_pitfalls) for examples. See way/1361164081 if you want to look at an example. |
|
| 163137912 | Overlapping fairways and greens is bad, but so is "almost touching". What you should be doing is *sharing* the nodes between the green and the fairway. Take a look at the wiki (leisure=golf_course#Common_mapping_pitfalls) for examples. I've gone ahead and fixed way/1361164081 if you want to look at that for an example. |
|
| 163227978 | Thanks for helping with my golf course cleanup project! |
|
| 163132655 | Thanks for helping with my golf cleanup project! |
|
| 163098973 | Please don't break existing fairway relations. You need to read the golf_course wiki first before you make any changes that undo the work of others. Thanks. |
|
| 163068703 | Hi Stykman17, thanks for your contributions. In case you weren't aware, fairways that completely enclose objects like fairways and sandtraps should be turned into multipolygons. See leisure=golf_course#Common_mapping_pitfalls Thanks. |
|
| 163053806 | Hi eschack50, thanks for your contributions. In case you weren't aware, fairways that completely enclose objects like fairways and sandtraps should be turned into multipolygons. See leisure=golf_course#Common_mapping_pitfalls Thanks. |