b-jazz's Comments
Changeset | When | Comment |
---|---|---|
88469984 | about 5 years ago | Hi there skinnyhunt05. I removed the golf cart paths that duplicated the existing residential roads on Barleywood, Collinwood, and Glenwood Drives, and Village Parkhouse Gatehouse Road and added a "golf_cart=yes" tag to the existing roads to indicate that golf carts are allowed there. As I understand it, a duplicate path shouldn't be used, but instead have appropriate tags added to existing roads. If you know otherwise, please let me know. Thanks. |
80198102 | about 5 years ago | I've removed the new Cinemark that you created since there is already one defined. If I'm misunderstanding the purpose for the duplicate, please let me know. Thanks. |
87998803 | about 5 years ago | Hi there. Thanks for making a bunch of contributions to the map. I just wanted to point out a couple small problems so that you can avoid them in your future mapping sessions. First, sidewalks shouldn't have a "name=Sidewalk" tag. Instead, there is a "footway=sidewalk" tag that should be used. Second, ways shouldn't cross over themselves or double back on themselves. So in this change, where you come to a corner, and then double back away from the corner, a new path should be started.
|
87944557 | about 5 years ago | Hi Twissler. First off, thanks for the work you're putting into updating the map. Unfortunately this particular change has a lot of problems so I've reverted it back to before you did you changes. When you shifted that bike path, the ends of the path where it connected with other ways got all messed up and created a big problem to clean up.
|
87931272 | about 5 years ago | A-ha. I see it now. I'm not used to Bing having the most up-to-date satellite imagery, so I didn't even bother to check. My bad. I went ahead and applied my changes again (with the correct path this time). The loop was drawn such that it reused nodes on the way back to the main path. This is considered a no-no and should have started with a new path. Thanks for the quick reply. |
87931272 | about 5 years ago | Hey Joe, can you tell me why you reverted my changes? Was there a specific problem with them, or did my changes get caught up in some larger issues? I'd like to understand before I reapply them because there are certain problems with 825077740 that need to be addressed and don't want my changes reverted again without good cause. Thanks. |
87664977 | about 5 years ago | Hi MojaveNC, a small portion of West State Street was deleted in this change. Was that intentional? |
87584699 | about 5 years ago | Hi AduptUniform, thanks for the additions to OSM. Are you using satellite imagery (or local knowledge) that is relatively new? The area I'm looking at has this going through a parking lot and I'm wondering why a living street exists in a parking lot. Has there been some construction there I'm not aware of? Thanks. |
85516740 | about 5 years ago | Thanks! |
85516740 | about 5 years ago | Is there any chance I can convince you to delete the way until you are ready to finish? I'm trying to keep the country free of the "self-intersection" errors and this one keeps showing up on the list. Thanks. |
87535438 | about 5 years ago | Hello KneeKnocker. Can you fix up the relation for this golf course? The course shouldn't use things like sandtraps and cartpaths as "inner" relations. It's like you are saying everything there is the golf course EXCEPT sand traps, those aren't part of the golf course. If you need some help with understanding inner relations better, let me know. |
87308406 | about 5 years ago | Hey Alan, can you take another look at osm.org/way/29795501? Several nodes got deleted and now the polygon is a figure eight, which I'm guessing isn't what what intended. |
85516740 | about 5 years ago | There are some problems with this way. The first is that is intersects and overlaps itself in many places. The second is that it is untagged, so I have no idea what it is. Can you fix it up please? Thx. |
82771454 | about 5 years ago | Hi there. Can you take another look at osm.org/way/780861268. It claims to be a room, but since it crosses over itself, it is impossible to tell if the inner box is a room, or if the outer box (minus the inner donut hole) is the room. It would be good if you could break that way up so that it doesn't do this (technically, ways aren't supposed to intersect with themselves). Thanks. |
87104630 | about 5 years ago | Hi Daniel. I'm not sure how or why this change was done, but I have reverted it to move the water way back to its original place. If you need some help with a change, let me know what you were trying to do and I'll see if I can help you get it done. |
86680127 | about 5 years ago | Hi there, can you clarify the tagging and geometry of osm.org/way/815603054 ? It is listed as a gate, but I'm guessing it should be a fence or wall or something. Also, the geometry is drawn in such a way that it doubles back on itself, which isn't allowed. Can you fix that as well? Thanks. |
85694417 | about 5 years ago | Hi pwhite. You might want to take a look at osm.org/node/1787821171#map=14/39.6212/-79.8103
|
85697020 | about 5 years ago | Are you familiar with the sidewalks in this area? One in particular is drawn in such a way that it doubles back on itself (nodes A-B-C-B-A) and also includes an "incline" tag. I tried to fix the fact that it shouldn't double back on itself, but then the question arose of which way the incline actually points (A-B-C or is it C-B-A) if that makes sense. Is this something you can fix because you might have local knowledge? Thanks (and thanks for the contributions). |
81198330 | over 5 years ago | Thanks for the additions, but you might want to know that you shouldn't but anything under the name tag that isn't the actual name of the feature. For instance, osm.org/way/773920089 shouldn't have a name at all. |
84019589 | over 5 years ago | Looks like osm.org/way/562085214 got messed up during your change. Can you take a look at correct it? I'm not sure what the intent was here. Thanks. |