Changeset When Comment
186549446

Thanks Mark. Another thing you might want to be aware of is that your polygons shouldn't overlap each other. If you look at node/14057315719, you can see that the fairway and green are overlapping. Instead, you should share each and every node at the boundary of these two polygons. If you don't, the Q/A tools will pick up on that and someone will have to spend time cleaning up the mistakes (which takes away from other mapping work.)

You might want to look at the wiki pages in the golf_course wiki at leisure=golf_course that will try to explain some of these things in more detail.

Again, thanks for your attention and for being responsive to communications. It's much appreciated.

186415487

You have made a common error when you saw a fairway that looked like it didn't have a proper "Feature Type" defined and decided to add the fairway tag. The hole was already properly tagged, but was part of a relation of multiple objects known as a multipolygon. Please read this short wiki page where I've tried to explain what you are looking at and avoid making the mistake in the future. osm.wiki/ID_understanding_golf_course_relations Thanks.

186039419

RE: way/1380488199

You have made a common error when you saw a fairway that looked like it didn't have a proper "Feature Type" defined and decided to add the fairway tag. The hole was already properly tagged, but was part of a relation of multiple objects known as a multipolygon. Please read this short wiki page where I've tried to explain what you are looking at and avoid making the mistake in the future. osm.wiki/ID_understanding_golf_course_relations

Thanks.

186474299

FYI, the direction of the golf=hole centerlines is important. They should point from the tee to the green. I've fixed those I found on this court, but wanted to let you know for future edits you might do.

185787821

Leave 'em, Love 'em. It's up to you. :-D

185787821

100% Correct. Love those as is. Thanks.

181329378

Thanks bbmiller. Looks like others have removed the entire relation but possibly left behind elements that weren't part of the original relation. Those have been cleaned up by others as well.

185787821

Hey there FOFB,

Thanks for cleaning up these bogus hole numbers (refs). Just curious how you found them. It's uncommon for someone with so few changes to be finding a specific error like that across a large area and fixing them up. Glad to have you around lending a hand!

Oh, if you continue doing this and see a name along with it that is just the hole number or something like "Hole 1", could you deleted that tag while you're there? Thx!

185774713

To be clear, this isn't the "current OSM convention" but is a proposed convention that hasn't been voted on.

There is one problem that I've noticed so far and that is that you took a multipolygon that describes a fairway as being made up of an outer polygon and the green as an inner polygon. You tagged that outer ring as "fairway", but that isn't correct as the definition of what is and isn't fairway belongs to the multipolygon relation. See osm.wiki/ID_understanding_golf_course_relations for more information.

186040192

Hey Stephen, there are ton of problems with your edits that you've made to this golf course. I don't even know where to begin fixing it. You've duplicate a bunch of information that already exists. cart paths, fairways, greens, water hazards, etc. You should go back through and clean them up. I'll check back in 48 hours.

You've also named items that shouldn't be named. Please read up the various golf related wiki pages at wiki.openstreetmap.org and look at how other courses are mapped to get an idea of community standards.

I see you are using JOSM, but I don't see that you validated your changes, because around a hundred ways have duplicate nodes in them that should have been caught (and fixed).

185843082

Another example is node/14019884508 that doesn't join the green way.

185851932

Hey Pizza,

Can you be a little more careful when joining fairways to greens like node/14020226043? I've fixed several of these in the past couple of weeks and thought it would be worth reaching out and mentioning it to see if you could correct it at the source.

Thanks,
- b-jazz

185727028

way/1539099360 and it's neighbor partially overlap, but map the same body of water. They should be represented with a single polygon and not two overlapping (or even adjoining) polygons. Can you please fix this? Thx.

185736959

Greetings mayman,

Can you help me understand what you are doing with way/1539164424 and way/1539164423 and why they are mapped the way they are mapped instead of a single polygon for the bunker?

Thanks.

185370133

Hey there HockeyPlayz,

I did some small edits to the tees you mapped in this change. It's not uncommon to find that people want to map something and then give it a name. So somebody will map a building, tell OSM it is a building, and then name it "Building".

So I've unnamed "Tee #1" and put a `ref=1` tag on the two tees so that map consumers will know that it is the first tee. No need for you to go back. Just letting you know in case you do further editing.

Thanks.

P.S. Are you doing Happy Gilmore drives at your local course with a username like that?

185377301

I reverted the changes made that overlap other golf features. Please reach out to me.

185377074

Thanks for understanding. I've gone through and removed most/all of the roughs and single trees that were marked as wood. You might want to look at the golf course mapping wiki at leisure=golf_course. That's a good start with a lot of subsections to explore.

As for mapping out roughs, I'm typically against doing it because they rarely have well defined borders. But that's just me.

185377074

Hello DJH,

I just wanted to give you a heads up that I'm planning on reverting most(all?) of the changes you've done to this course. There are a ton of problems and it would be easier to remove your changes and start from scratch than try to fix them all up.

I understand you put effort into this, so I wanted to work with you and give you advanced warning.

Some of the problems:
* the areas you drew for things like roughs are extremely minimal and blocky and aren't following natural landscape.
* your roughs often cross over other elements like fairways and cart paths.
* you are using natural=wood to define a single tree or two. you should be placing single trees in those cases.
* sometimes your natural=wood extends far beyond the visible area that trees are in.

If you have issues with the reverting of these changes, please let me know in the next 24 hours. Thanks.

185187124

Putting the various fairways together into a multipolygon isn't necessarily wrong, but this isn't done anywhere else in the country. They are already associated with each other by the ref number. I'm going to undo this grouping for now, but am open to discussing the issue if you feel strongly about it.

185104988

I'm always happy to help. Feel free to reach out with golf mapping questions any time.

You might want to peruse the golf wiki at leisure=golf_course for some basics on how to map golf courses. Be sure to click on each of the features and read up on those as well. For instance, I noticed one of your golf=hole centerlines today was pointed in the wrong direction. It should always go from the tee to the green. Direction matters for this type of way. (I already fixed it, but figured I'd point it out for any future mapping you might plan.)