Thanks! Just an early mistake. Popped in a fix.

For your reference, here is _current_ Airbus / Maxar / Vexcel imagery from 2025 via Google Maps: https://maps.app.goo.gl/a27X43MiWYpeUXtw7

You've deleted the temporary Pro Shop at Lake Chabot Golf Course. Why? ➔ way/1441514060

OK I _think_ I might have corrected the fairway / putting green relationship on hole 1 here. Would you let me know if I've got it right? I'm mapping another local course and ready to get those relationships right.

Paging @b-jazz ... I tried relationships on these four holes on a new course mapping mission here. I'm going to stop now until I hear if I've got the details right or not.

Well, confirming while there today for kids' golf coaching lessons. This is hole 1 - it's tightly cropped rough but the fairway does finish well in front of the green and the green is ringed by a defined fringe. Second shot is from the tee ¯\_(ツ)_/¯ https://imgur.com/a/BD5BAGD

Actually the more I look at the mapping of this course the weirder it becomes. The fairways seem too small. I am not sure how to update it for the best here, would be interested in your thoughts overall.

I'm not quite sure what you mean on this one. The prior fairway on hole 1 is still in place, I defined the rough, and I deleted the name=blahblah from the putting green (I saw this debate on another golf course, such features shouldn't all be named as it's similarly redundant as pins). I can help fix things I've broken but the relationship problem is a bit unclear to me in this case. There's probably more... I've been adding rough and deleting green name="xyzzy" properties on this course today.

And now all that said. Fresh aerial imagery (again, ESRI but I'm not 100% on that yet) shows that they likely reconfigured the south course significantly. Well shit, more work to do when something else can confirm that.

OK! Turned out my conference ended a bit earlier than I thought so while resting up in a Barcelona hotel room, I figured out utilsplugin2, it's Split Object tool, and JOSM's own Improve Way Accuracy mode. This was much quicker to correct some ways and paths crossing over that I'd done. And you're right, it is faster. Just... learning curves are a thing.

If you have a list of QA issues where I've left some early overlaps just send me the list and I'll get them knocked out and fixed.

Thanks, these are all helpful guidance. I did find JOSM and have tried it for a few changes and uploads. My experience so far is that it's deeply unintuitive so the learning curve is definitely steep. I'll spend more time learning it when I'm back from current business travel in Europe. It's also clear that having some patience to tune and get the features right, put enough points in the polygons to avoid overlaps and have decent curve following, is all valuable. Rushing to the finish line clearly generates QA issues... sorry 'bout that. I'm learning :) Meantime I'm just making small edits and corrections where I can as I can in ID.

If you wouldn’t mind, that’d be great. I _think_ I inspected and found most, have just sent in several changesets for fixes now, but a double check from you would be most helpful.

Thanks, appreciate the guidance. I’m new to this and I think I’m getting better. Do you know if there’s a way I can quickly and easily identify instances where I’ve done this in past changesets?

I suspect these features have issues with the water_hazard tags, they are now showing up on the map as much larger areas than in reality.