phidauex's Comments
| Changeset | When | Comment |
|---|---|---|
| 78328309 | about 6 years ago | Hi, thanks for the additions, but you may want to hold off on bringing more RapID buildings into the Denver area - they aren't particularly high quality traces, and we are currently in progress on the DRCOG Planimetrics Import which is bringing in much higher quality buildings with address data (which you would be welcome to participate in!). You can read more here: osm.wiki/Denver_Planimetrics_Import
|
| 78230250 | about 6 years ago | Hi, thanks for contributing! One tip is that in OSM, we fully expand all abbreviations (it is easier for computers to abbreviate than to un-abbreviate) so Pl is best expanded to "Place". I corrected this one for you, but thought I'd let you know for the future. Your area of town is changing a lot so there are a lot of improvements happening to the maps right now.
|
| 77962872 | about 6 years ago | Hi, this is the second guest house point you've added to this area. Is this a building that is available for rent? IE, are you sure it is a guest_house that should be displayed on the map?
|
| 77841310 | about 6 years ago | No problem, this is how we all learned! If the tunnel is just under Bear Creek Rd, then split the way again (right click on the node where you want to split, and select "Split"), then delete the layer and bridge tags from the portion going up to Fireweed Dr. If you want to get fancy, you can even split again to isolate the section that are stairs, and change the highway tag to "highway=steps".
|
| 77841310 | about 6 years ago | Getting closer! Take a look at the change I just made - I split the way again and made it so the section that is a bridge is the only part tagged as a bridge. I also disconnected the way from the parking lot - it is usually bad practice to join the nodes from paths and roads to other features. Also, where does that tunnel come out? Looking at the streetside imagery I can't tell where it goes - is it really as long as it looks, and open to the public?
|
| 77841310 | about 6 years ago | Hi, thanks for mapping! Is this whole trail a tunnel? It seems unlikely. If there is an underpass, the path should be split, and only the section that crosses under the road should be shown as a tunnel.
|
| 76834116 | about 6 years ago | P.S. When editing in Ohio, don't forget to use the Layers tab to change from "Bing" imagery to "OHIP 6in" imagery - it is much more clear and easier to edit with! |
| 76834116 | about 6 years ago | Hi, I also took a look, and did a few cleanups for you. Take a look at what I did, which will help you out next time. A few things I cleaned up - in some areas there were roads overlapping each other - this looks "right" in the editor, but confuses software using the map. I also changed the border roads around parking lots to be service roads, and the aisles down the middle to to be "parking_aisle", which also makes it more clear to routers which roads are used to exit the lot, and which are used to find a parking space. I also removed the one-way tags from the parking aisles - unless there is a clear one-way sign, they don't usually need to be marked that way. If some are one-way, then some need to be one-way the opposite direction so you can get back out! Hope this helps. |
| 75691918 | about 6 years ago | Hi MilkmanHere, a number of us have been trying to reach you on the issues with the very large relations you've been creating. I think the problem is that you are adding all of the properties in a neighborhood to a neighborhood boundary relation, which isn't how those relations are meant to work - the relation is just for an actual boundary line, not the members. Can you please delete the Summerlake relation, and other similar neighborhood relations you've created? They are breaking the rendering and map in the area due to their high member count. |
| 75917236 | about 6 years ago | Apologies, this comment was intended for the original creator of these relations, I see you are trying to fix them! Sorry for the false alarm. |
| 75513853 | about 6 years ago | Hi, some of your recent edits are very malformed, and are breaking the map. In particular, joining whole areas into a boundary relation is not how relations are meant to be used, and it is slowing down the map and causing a lot of problems. Please remove the relations you've created, or they will have to be reverted. If you aren't sure how to do so, let me know and I can help. |
| 75917236 | about 6 years ago | Hi, please stop what you are doing - you are creating some very malformed relations and breaking a lot of things with your edits! You should not be adding all the objects in a location into a "boundary" relation - that relation is for the actual boundary line only. The relations you are creating are extremely malformed and are creating performance problems. Please revert your changes, or delete the relations you've created. If you aren't sure how, let me know and I can help. |
| 75848508 | about 6 years ago | Hi, it is a bit tricky, so I helped you out and corrected the details for your shop. user_5359 is communicating that in a map database, things aren't just described by a name, they are described by "tags" that explain what the thing is. In your case, just having a point with a name is useless, because the map tools don't know if Manzer Equipment is a river, a town, a road, a shop, etc. You can see that I've added tags describing what your shop is. You can add similar tags to the fitness center point if you'd like, now that you see how it is done. |
| 75802932 | about 6 years ago | Thanks for mapping! One tip is that after sketching a building, use the "Q" shortcut in the editor to "square" the building, it will align the corners to 90 degrees, and make for a more professional looking result.
|
| 75532523 | about 6 years ago | Good catch, thanks! I corrected the address labels on the nearby houses as well.
|
| 75399514 | about 6 years ago | @Woodwosewulf - I'm probably the originator of the recommendation, since that is a tagging convention that has been gaining traction, and is now in common use in CO. Do you concur with a tagging strategy like that? |
| 75397123 | about 6 years ago | Hi, nice additions! To make your sidewalks as useful as possible, make sure to connect them to the road network at all crossings, and anywhere else where you could transition from the road to the sidewalk - that will make pedestrian routers work better, since they will have some way to route pedestrians from other roads onto the sidewalk network you've mapped.
|
| 75396708 | about 6 years ago | Is that what ARC really stands for? Yeesh... Sounds a bit out of date now...
|
| 75299654 | about 6 years ago | This is close to my daily bike commute - I'll ride it next week and get a GPX trace.
|
| 75308415 | about 6 years ago | My man, you did add a duplicated residential road (why?) and the sidewalk you added is an uneditable mishmash of sidewalk and unmarked crossing - it would be completely fine to just make that one stretch of sidewalk - splitting it up like that makes it impossible to maintain and adds no value to the map. I fixed the duplicate road, but take a closer look at your edits before uploading, please.
|