OpenStreetMap logo OpenStreetMap

Changeset When Comment
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,
On hole #5, it's probably best just to join the fairway and the green together and share nodes between them since there isn't a clear break between the two. See leisure=golf_course#Common_mapping_pitfalls for examples of how to map them. Thanks.

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.
For example: way/1368431473

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.

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
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 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!

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
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 an instructions
on how to better map golf courses: leisure=golf_course#Common_mapping_pitfalls

125253035

Whoa! Cool! Thanks archpdx for doing the work on this.

https://ultra.trailsta.sh/#map&m=17.26/44.0406/-123.0713&q=LQhQGcBcE8BsFMBcoAELYENrwE7mWmsCjAA5IrjQC2ARgPayqFoCWAxvQHbD0BuuTKUQoMsAO5ZwzFh27BW1DAHMkMlimKcx8cO3jqWxYopUGNG4yk5d2GSIYuaUAcnjV6AK1aIAZpmVgF0cLKwATenFbDHBzJ1CUAG0UVUgAGmt6AFcuSBxoFABdEOcTJVUSohR3Lx8ARyzdSFZuUBBgUETaBgAPRABvfu76HoBfUcKAblAucRxEpS4AfSUw+ABefxVSRnhCxM4cvOgp0GzIa3hc3EmgA

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.