Hi there AsYouAre,

Just wanted to let you know that a change you made to way/918883786 was incorrect. You tagged the outer ring that defines the fairway as "golf=fairway", but it was already part of a multipolygon that correctly defined that. To add that tag when it already existed is saying that everything inside that polygon is fairway, including the green, which isn't correct. I'll fix it. I just wanted to let you know so you could avoid that in the future.

Thanks djjherp for contributing golf courses to the map. In the future, when drawing a fairway that surrounds a green (i.e. way/1360644967), could you combine the fairway and green together (select both and press 'C' on the keyboard) to create a multipolygon? Thanks!

Hey there Brad,

Thanks for your work on golf courses. I'm hoping you can do a favor for me that will save me some future work. When you draw a fairway that surrounds a green (and other things like bunkers), could you select those items and combine/merge them together into a multipolygon? The keyboard shortcut is 'C' in iD. Thanks!

Thanks for listening to my suggestions Steve. It's great to see you creating the multipolygons around the green now. I really appreciate it.

I noticed that you are making golf=fairway polygons around the green that butt up against the rest of the golf=fairway polygon for the hole. They are typically considered to all be the same fairway and should be represented as a single polygon. That's how it's typically mapped from my experience.

Thanks Steve. There's nothing inherently wrong with fairway going around the green. You just have to make sure the lines don't intersect/touch and that you combine them into a multipolygon. For instance, if you look at way/1352433807, you can see it has great imagery and the fairway grass can be seen going all the way around the green. In that case, draw the fairway all the way around, select both (shift click them) and then type 'C' to "Merge" them together into a multipolygon.

There's a problem with some of your golf course mapping. You've made fairways (for example way/1359162412) that intersect other features on the course. In that example, the green. These intersection shouldn't happen. See leisure=golf_course#Common_mapping_pitfalls for examples on how to properly map golf courses. Thanks.

Hey Brad, there's a problem with some of your golf course mapping. You've made fairways (for example way/1359357658) that intersect other features on the course. In that example, the green and and sand trap. This intersection shouldn't happen. See leisure=golf_course#Common_mapping_pitfalls for examples on how to properly map golf courses. Thanks.

Hey Steve, hate to report this on Valentine's Day of all days, but your deletion of way/1034890320 broke the relation that it was a member of. It was happily coupled with the green, but when you deleted the fairway, you left the green single and lonely. I see that you created another green in its place but failed to introduce (merge) it with the existing green.

Please see osm.wiki/Relation:multipolygon to understand the concept and give instructions on how to create them in your editor. You should also check out leisure=golf_course#Common_mapping_pitfalls for some common errors in mapping golf courses.

Thanks.

No problem. It happens to all of us at one time or another. The tools really need to soft-block any attempt to create something like this.

Please be careful that you don't make changes that span massive portions of the map.

Oh, and you might also want to consider learning how to use JOSM if you are going to do a lot of golf courses. It will make life a lot easier than using iD.

Good Morning J,

There's a problem with Hole 8 (and possibly others that you've created). You have the polygon for the fairway and the polygons for the sand traps/bunkers intersecting. They shouldn't be drawn in such a way and the fairway needs to be adjusted to go around (or beside) the bunkers.

It would also help out if you could combine any fairway that completely surrounds a green and/or other features into a multipolygon. See the wiki for examples: leisure=golf_course#Common_mapping_pitfalls

Thanks.

Why are you deleting this golf course?! There needs to be a better explanation than just "The Diplomat" in your changeset comments. If you need to "improve" the course, you need to keep the existing features whenever possible to preserve history. Thanks.

Hi Haggardlyforte,

I've gone ahead and reverted this change in changeset/162441660 and wanted to let you know why.

The existing features that you added "golf=fairway" to are part of something called "multipolygons". They combine things like fairways and greens together to indicate that everything that isn't a green/bunker/etc is part of the fairway. To go back and label the piece that defines the "outer" boundary of the multipolygon incorrectly as it says that *everything* within that border is a fairway. Hope this helps. Please let me know if you have any questions.

"This feature has been labeled as deprecated. The recommended replacement is: railway=station mapped as an area."

That's from the Tag:railway=facility wiki. I'd like to see someone replace the facility with a station area to preserve some of the history instead of adding a singular node.

"A railway station is a node."

Well, that's not entirely correct. A railway station can be either a node or an area. It can be a relation, but only a multipolygon relation.

I think a station node might be warranted here, but I'm not sure what the correct way to handle that and the railway facility without doing more research.

Edits that contain large numbers of objects spreading across the entire country with an unhelpful description of just "." are highly frowned on. Please keep your changes more local and provide a better description of what you're changing. Thanks.

Thanks for adding golf courses to OpenStreetMap. We appreciate your contributions.

Here are some bits of advice to make your golf course mapping even better:
◉ Fairways and greens boundaries should never intersect 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 (don't draw nodes for each that might overlap or leave gaps.)
There are some more bits of advice if you care to read over the golf mapping wiki: leisure=golf_course#Common_mapping_pitfalls

Hi DThos,

When mapping fairways and greens, please don't reuse nodes between the green and the fairway when the green is inside the bounds of the fairway. If there is a visible "fringe" around the green, you should represent that fringe by leaving a gap between fairway and green. The two features should also be merged into a multipolygon by selecting both and selecting Merge after right clicking on them.

See the following for more information on mapping golf course features: leisure=golf_course#Common_mapping_pitfalls

thanks.

Oh, another problem is deleting an object when you want to start from scratch. It's much better to modify the geometry of an object instead of just getting rid of it (and more importantly, it's history). If it is difficult to see, try the "W" keyboard shortcut to turn on "wireframe" mode and get rid of some of the shading from the existing feature that obscures background imagery.