pkoby's Comments
| Changeset | When | Comment |
|---|---|---|
| 60418636 | That's my bad! I just checked all my changesets around that area from that time frame, and aside from the road you linked, it looks like I changed this road to a service road without a name: way/605065233 Other than that, I can't find any name deletions. |
|
| 95341723 | Oh wow, very cool! Thanks for the info. |
|
| 95342500 | Fair point! I also don't think that there is any signage on-site to point one way or another. |
|
| 95342500 | Do you have a source for the name? I talked to some people from GHPRD awhile back, and they were impressed that I knew it was Kiwanis Park, so I was curious. |
|
| 95342059 | I noticed that you had changed the name of this road, but the fact that it's private is in the tags (you can see that it's got gray dashes as well, meaning private). |
|
| 95341723 | Hi, welcome to OSM. I noticed you're new to the website, but it looks like you might have some local knowledge that I don't. Do you have a source for these names? I've heard of some of them, but not all. |
|
| 94523806 | It's weird to see you editing in my neck of the woods. :P |
|
| 60695742 | I just came across this changeset when I was mapping around Ashland. As I see it, the section of US 23 between A K Steel Entrance Road and probably around the mall is not any different in road type than the trunk road north of the steel works. The current of section of primary road is IMO "partially grade-separated". Could this be returned to highway=trunk? The current change in classification seems arbitrary. Eager to hear thoughts. |
|
| 39827291 | Hey. I don't know why that would be there, but having done some looking, it seems like the last editor added that tag by mistake when adding other track to the area. I removed the tag from the boundary, because there are no evident roads in the area that aren't already mapped. |
|
| 86744411 | Outdated local knowledge and imagery, I guess. I'll revert shortly. |
|
| 86298181 | No worries! |
|
| 86298181 | I understand that you're mapping this for the game, but that doesn't mean you should mis-tag features in the OSM database. There is no tag 'natural=trees'. The tag that matches what you want is 'natural=wood' (as in woods/forest). That's all there is. The woods exist in real life. If you don't map them in OSM, someone else might. If you were to delete the woods so it looks right in the game, that change would be reverted. The right thing to do is add the woods correctly tagged. Then if the game does not do what you want it to do, then edit the map in the game. That's all you can do. OSM comes first; any product using OSM data has to follow the tagging structure of OSM first. |
|
| 86298181 | Well, tagging an area of trees (which is what you should be doing here) is tagged 'natural=wood'. 'natural=tree' is for an individual point, which you should NOT do for a large area of woods. It's a tag for a notable individual tree. So the woods should be tagged in OSM (as natural=wood) if you want to be complete, but adding the trees in TGC would either be individually by hand or through LIDAR. Not sure why the game would now not import; that's strange... |
|
| 86298181 | I found some forum threads about the TGC game. Apparently tagging an area 'natural=wood' in OSM imports into the game as gravel (not concrete). To get woods in-game, you have to import from LIDAR data which is much more accurate than OSM ever would be. I think then that the trees would layer atop the gravel. Regardless, in OSM, you should tag the woods as 'natural=wood', and it seems like there are no tags to add to it that would bring it into the game. So tag the woods correctly on the map if you want, but it won't import it... |
|
| 86298181 | This seems to be a common issue: http://www.hb-studios.com/forum/index.php?topic=28253.0 (See especially the last post.) So you'd need to import trees from some other source, apparently. |
|
| 86298181 | Can you link to the exact feature you're seeing problems on? Right-click on it and "query features", then click on the link in the left menu for the correct outlined feature. |
|
| 86298181 | I fixed up the tags on the wooded bits you added. I saw that you added 'surface=*' on them, which isn't something you would add to a forest. They should show correctly now (try ctrl+shift+r to refresh your browser cache; sometimes old tiles still show, and it takes some time to render too). Generally, the minimum you need is 'natural=wood'. You could add 'leaf_type=*' and 'leaf_cycle=*', but those aren't required. If you haven't found it yet, check out osm.wiki/wiki. It will have all the tags you will need on any feature. Sometimes the in-browser editor is not clear about what some features are or what some tags would be useful/needed. This course is tagged correctly, so you could compare to that: osm.org/#map=16/40.7870/-77.8806. Either go into the editor, or right-click and query specific features on the map itself. And if you have any other tagging questions, feel free to ask (direct message works too)! OSM is a constant learning experience. |
|
| 86298181 | Very nice work you've done here! It looks like you've been experimenting with how to map the features. I think that you might want to remove `leisure=golf_course` from the holes, fairways, tees, and so on, just leaving the `golf=*` tags. That should remove the numerous golf point symbols from the map, but still be tagged appropriately. |
|
| 80871099 | 1: JOSM user-error. Fixed.
|
|
| 80855411 | Good points, and things I did not consider. I guess it's hard to tell if it's the owner of the business (as the username could suggest either way), or an SEO company. I understand that at large scales, this would get very annoying... |