b-jazz's Comments
| Changeset | When | Comment |
|---|---|---|
| 163930234 | When drawing the fairway and green, if you can't leave room for a fringe all the way around the green, you shouldn't draw the line for the fairway around the green, but instead butt up against it on the inside and re-use each and ever node of the green. See leisure=golf_course#Common_mapping_pitfalls for some examples. |
|
| 163916411 | >people use the same software and overlap fairway and greens all the time. Yes. And that's really bad. OpenStreetMap is a community sourced repository of all sorts of map data and there are tens of thousands of contributors and millions of users of the data. We need to all be careful to behave as a community and not stomp on other contributor's hard work. Using OSM as a scratch pad by doing some work and then deleting the data is hugely problematic and could lead to you getting banned. It's better to all work together, follow OSM best practices, and come up with a solution and stop bad videos and other instructions from recommending these bad habits. Your instinct to not delete someone else's work to do your own way is right. I'm putting in hundreds of hours to work cleaning up this mess and to have someone come behind me and wreck it again is incredibly frustrating. I did take a look at Chad's Tool and saw that there is work to get multipolygons/relations working correctly. There is a pull request (https://github.com/chadrockey/TGC-Designer-Tools/pull/143) that is just a week old that might solve your problems. If you could help by giving voice to the issue and applying pressure to getting this code implemented, that would be appreciated. |
|
| 163916411 | I understand that might be a problem, but we need to conform to the standards and norms of OpenStreeMap and do things the proper way there and not try to work around it due to a bug or shortcoming of 3rd party software. Can you let me know what software is causing this problem for you? I've heard of some software not handling multipolygons correctly, but they eventually updated their software to fix that problem. Have you tried updating to the latest version?
|
|
| 163916411 | Re: way/1370057429 Hello 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 instructions and examples of 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! |
|
| 163885201 | Hello 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 instructions and examples of 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! |
|
| 163921585 | Hey Zach, please go back to the notes I left on a previous change from you last week (changeset/163446770). You are crossing greens and fairways and shouldn't be. Please examine the wiki pages and make sure you aren't creating greens and fairways that intersect like in way/834709162. Please leave a comment here so I know that you got this message. Thanks. |
|
| 163881705 | Please don't create lollipops like on hole 5 (way/1369777434). Use multipolygons to properly create enclosing features instead. See my previous comments and wiki reference on how to create those. Again, feel free to reach out for help if you don't understand. Thanks. |
|
| 163879948 | Hi there JHornberry, as I pointed out in a previous changeset comment (changeset/162903940), you are breaking multipolygon relations when you delete and recreate fairways that are part of a relation. Please see the wiki at osm.wiki/Relation:multipolygon#iD for help in understanding how to deal with multipolygons. Feel free to reach out here if you don't understand something. Please respond here so I know that you've seen this message. Thanks! |
|
| 163866233 | Re: way/1369677169 ... Hello 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 and 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! |
|
| 163811983 | Thanks for joining the fairways and greens. Much appreciated. |
|
| 163754940 | Hey there Thockey,
|
|
| 163783038 | 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 and 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! |
|
| 163740212 | Hi Zach, why are you creating a multipolygon out of two lines (typically most of the fairway on one line and then a short chunk of line that completes the fairway for the other?) Is there something I'm missing? I don't see any use for a multipolygon in that situation.
|
|
| 163714996 | Hello fellow golf course mapper. If you can't see any fringe around a green, you shouldn't reuse the nodes around the entire green, but instead cut the green out of the fairway polygon and reuse them on the boundary between the green and fairway instead. Please read the wiki for visual examples and 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! |
|
| 163662516 | You shouldn't be using the "lollipop" style of mapping as seen in way/1367951144. You need to create proper multipolygon relations in order to map features like roughs/bunkers that are within other features. Please see osm.wiki/Relation:multipolygon and leisure=golf_course#Common_mapping_pitfalls for help in understanding how to map this situation. If those aren't clear, please let me know and I'll help explain them further. Thanks. |
|
| 163633938 | 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! |
|
| 163653489 | Hey there Matthew, Thanks for your golf contributions. We appreciate your help. I wanted to point out a small error in what you are doing. An example is the multipolygon relation relation/18829142. I believe you were the one to turn the fairway and green into a multipolygon. That's awesome and much appreciated. But you left the fairway tag on the outer polygon which duplicates the tag on the relation itself and also means that everything inside that outer (including the green) is a fairway, which isn't right. Whenever you make a relation, you need to make sure the outer polygon isn't tagged as well. Let me know if this doesn't make sense. Thanks! |
|
| 163633261 | You shouldn't be using adjoining polygons to define a single feature like a fairway in hole #3. You should just use a single feature for the fairway, a single feature for the green, and then select them both and right click and select merge to make it a single object called a multipolygon. If you need help, please check out the wiki at leisure=golf_course If you need help after that, please drop a comment here or reach out to me for help. |
|
| 163609736 | Thanks for helping out with this MapRoulette challenge! |
|
| 163629479 | What exactly are you trying to troubleshoot? Maybe I can help. |