b-jazz's Comments
| Changeset | When | Comment |
|---|---|---|
| 172806795 | RE: way/1435170498 When drawing golf course areas (such as greens, fairways, bunkers, tees, etc.), please be aware that the ways used to outline those areas can't cross over each other. Fairway outlines shouldn't cross over greens or bunkers or other fairways for example. If you could go back and clean up where you've made this mistake, that would be helpful. But more importantly, if you could stop from doing this in the future, it would be greatly appreciated. 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 about golf course mapping, feel free to reach out. |
|
| 172675421 | RE: way/1434444359 Hello Doctor, Thanks for the golf course contributions, but there are a bunch of problems with this hole as you've mapped it that cause others to clean up behind you. * you split the green area into two different ways and joined them up with a multipolygon. That is not the correct use of a multipolygon here.
I'm happy to help you golf courses correctly. Please be careful going forward and reach out if you aren't sure how to map something. Also, you might want to visit the golf_course wiki at osm.wiki. |
|
| 172269282 | Thanks for the contributions jwelchjunk. Just to let you know, the tee box (golf=tee) shouldn't have a name. I'll go ahead and clean that up for this course, but wanted to let you know for your future mapping projects. Thanks! |
|
| 171985532 | When there is no clear delineation between what is rough and non-rough, there really is no need to draw in the rough. By this, I mean, I couldn't see any different between the area inside the rough vs. outside the rough. There were no distinct mower lines or other physical boundary, so it's just an arbitrary area that probably shouldn't be mapped. |
|
| 171517597 | Hey NJ, I'm going to revert these changes as they are incorrect. It's not really your fault, as iD (the editor that you used) doesn't make it obvious that these were already fairways. They are part of a "multipolygon" relation where the fairway and green are paired together and everything inside the fairway EXCEPT the green defines the fairway. In the future, if you see what looks like a fairway and iD claims it is a "Line", check first to see if it is part of a relation. I'm going to try to create a wiki page to better describe this. This is what I have so far: osm.wiki/ID_understanding_golf_course_relations |
|
| 171480375 | RE: way/984095380 My opinion on mapping out roughs is that they are often so nebulous that it leads to messy course maps and is better to just leave them out. Most golfers understand that if it isn't within the fairway, it is rough. No need to really draw it out. There are some exceptions that I've seen where the boundaries are very clear and could be easily mapped. But those are few and far between. |
|
| 171373902 | Thanks Thunder! What's appreciated even more than people modifying the map are mappers that are open to learning how to improve their skills. So thank you so much for being open for improvement. I'll reply to you direct message next. |
|
| 171247085 | RE: way/1426109119 Please don't use the "lollipop" style of mapping golf course elements as you've done in the URL above. You need to create proper multipolygon relations in order to map features like roughs/bunkers that are within other features like fairways. Please see leisure=golf_course#Common_mapping_pitfalls and osm.wiki/Relation:multipolygon 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. |
|
| 171206513 | Awesome!! Thanks so much for helping to clean up golf courses. If you're looking for more of this, check out the MapRoulette challenge: http://mpr.lt/c/50926 |
|
| 170941326 | FYI, no need to add a "golf=tee" on the start node of a "golf=hole" when that start is already inside of a "golf=tee" area. It's redundant. |
|
| 170988370 | FYI, I fixed way/1424842363 Golf holes need to start at the tee and end at the green. You had it backwards. Common mistake. Just thought you might want to know. |
|
| 121170673 | My preference depends on whether or not that business is the only one occupying that physical space as marked on OSM. If it is, then I'll put all of the necessary tags on the building. Otherwise, I'll create an address tag and put relative tags on that address. |
|
| 121170673 | Thanks Learning, As you have more information on the physical move than I do, please feel free to move the object in OpenStreetMap as you see fit. |
|
| 171110025 | Wait! What? How did THAT happen!? Harumph. |
|
| 170905979 | The fairway for the first hole shouldn't extend and surround the tee for the second hole. It should stay with the fringe around the first green. Can you take another look please? Thanks. |
|
| 169524343 | Thanks Bamamba, but you're doing it again. See way/1423871476 for another example. |
|
| 170796739 | RE: way/1423958947 When drawing golf course areas (i.e. greens, fairways, bunkers, tees, etc.), please be aware that the ways (lines) used to outline those areas must not cross over each other. Fairway outlines shouldn't cross over greens or bunkers or other fairways for example. Take a look at osm.wiki/File:Golf.png for an example of the "Wrong" way to map a fairway and a green along with the right way. There are some cases where a fringe exists around a green and you should draw the fairway outline completely around a green. Other times, the fairway and green butt up against each other. In that case the fairway and green should share the same nodes at the boundary between the two. When drawing these shared nodes, editors like iD (built into openstreetmap.org) will "snap" to an existing node if you get close enough. If you could go back and clean up where you've made this mistake, that would be great. But more importantly, if you could stop from doing this in the future, it would be greatly appreciated. If you have any questions about golf course mapping, feel free to reach out. Thanks. |
|
| 170753934 | RE: way/13015737063 When drawing golf course areas (i.e. greens, fairways, bunkers, tees, etc.), please be aware that the ways (lines) used to outline those areas must not cross over each other. Fairway outlines shouldn't cross over greens or bunkers or other fairways for example. Take a look at osm.wiki/File:Golf.png for an example of the "Wrong" way to map a fairway and a green along with the right way. There are some cases where a fringe exists around a green and you should draw the fairway outline completely around a green. Other times, the fairway and green butt up against each other. In that case the fairway and green should share the same nodes at the boundary between the two. When drawing these shared nodes, editors like iD (built into openstreetmap.org) will "snap" to an existing node if you get close enough. If you could go back and clean up where you've made this mistake, that would be great. But more importantly, if you could stop from doing this in the future, it would be greatly appreciated. If you have any questions about golf course mapping, feel free to reach out. Thanks. |
|
| 170564945 | Can you post a link to the imagery you are using? Your fairway seems a little bit problematic and wildly crosses bunkers (according to more standard sat imagery). Thanks. |
|
| 170327595 | There is my list of ~8000 fairways left to fix, but then there is a list of changes that have been made in the last 24 hours that gets generated every day. This secondary list ranges from 0 to 50 course elements to review and is reviewed nightly so that I can quickly educate new/problematic mappers on errors that they are making. Even though you aren't the one making the error, you show up having touched a fairway that is still a problem. As each one of these takes several minutes to research and construct a response to, it is some extra effort. Having said that, I wouldn't worry about it. I'm just going to sort my list of 8000 problematic fairways looking for "high density" ways that might qualify for your nearly colinear and work on fixing them first. This should greatly reduce how often you show up in the nightly reports. |