nmombo12's Comments
| Changeset | When | Comment |
|---|---|---|
| 115168641 | about 4 years ago | Forgot to add second source. Also used aerial imagery Oakland County MiSAIL 2020: BaseMap_EnterpriseOrthoTC2020BasemapMap |
| 84027287 | about 4 years ago | Hello John,
|
| 114452743 | about 4 years ago | Thanks for the updates jpotas.
|
| 114798481 | about 4 years ago | For further clarification, previous discussions on the OSM US slack have had consensus that even a temporary change is considered vandalism. Any temporary change you wish to make for personal download should be done offline and not pushed to the live OSM database. Please let me know if I can assist with offline edits when downloading for TGC-Designer-Tools. |
| 114930208 | about 4 years ago | For further clarification, specifically I am referring to way/688251137 (way/688251137) on the 13th hole. There is a guide on the wiki (osm.wiki/File:Golf.png) describing the proper usage of multipolygons for this type of feature. |
| 114452743 | about 4 years ago | Hello jpotas,
|
| 114798481 | about 4 years ago | Hello jpotas,
|
| 114930208 | about 4 years ago | Hello jpotas, a fairway with a "cutout" in the middle should be modeled as a multipolygon instead of having a single way approach very close to itself.
|
| 114945362 | about 4 years ago | Hello zmdaubs, This is a minor thing, but fairways should have shared nodes leading up to the green according to this wiki page
An acceptable alternative would be to consider the fringe as part of the fairway and make the fairway a multipolygon with the green as the inner part ofthe relation. Noah
|
| 114682637 | about 4 years ago | I assume you are discussing TGC-Designer-Tools to create a golf course in PGA Tour 2K. In this case, it is not accepted to intentionally map features that do not exist in the real world for this purpose. It is just like "mapping for the renderer", in this case the renderer is TGC-Designer-Tools utility. osm.wiki/Tagging_for_the_renderer
|
| 114682108 | about 4 years ago | Hello fattmat58, would you please keep water features tagged water=* in addition to golf=water_hazard? A feature like this can have both tags at the same time.
|
| 114682637 | about 4 years ago | Hello fattmat58, would you please share the reasoning for the cartpath zig-zag of way/1010094190 near the clubhouse? From available aerial imagery I can't identify a winding path.
|
| 113544489 | about 4 years ago | Thanks, makes sense! |
| 113544489 | about 4 years ago | I had seen another user remove features in the golf course due to construction in 2020. What is the estimated date of the aerial imagery used as a source? |
| 113341069 | about 4 years ago | Thanks very much, nice work here. Noah |
| 113125558 | about 4 years ago | Hi tpopchock, welcome and thanks for contributing. I can see you're a new mapper so I'm going to take a look and review some of your changesets. The "name" tag should be used for primary names of features and for the most part should have a sign labeling them. In the case of golf features, to label a tee, fairway, or green as a member of a hole we more commonly uses the "ref" tag, for instance "ref=1".
|
| 112952350 | about 4 years ago | This is actually SW of 13 Mile and John R |
| 112808368 | about 4 years ago | Action taken by DWG osm.org/user_blocks/5398
|
| 112307790 | about 4 years ago | Hello, it looks like the wrong way was selected along Fairgrove Ave for the change to footway. I have reverted that part of the changeset. way/8694877/history
|
| 112426803 | about 4 years ago | Hello David, Thanks for contributing! One request, please attempt to limit the size of changesets to a smaller region so that it can be more easily reviewed. Here is a reference link osm.wiki/Changeset#Geographical_size_of_changesets - Noah |