phidauex's Comments
| Changeset | When | Comment |
|---|---|---|
| 75251695 | about 6 years ago | Hi, welcome to OSM! A few tips for your mapping - use the "q" shortcut in iD to "square" buildings after tracing them - it will give them a more professional appearance. You also need to connect sidewalks to roads in places where there are crossings, so that routers can direct people onto them, right now yours are "floating" and not connected to the rest of the road network. Thanks for tidying up your work and happy mapping!
|
| 75164300 | about 6 years ago | Hi, thanks for mapping! A few tips to help you get started: Use the "Q" shortcut in iD to "square" buildings as you are drawing them, this makes for a much more professional result. Second, you've used the parking_space tag for the parking areas, which is usually for only a single parking space. You want amenity=parking for a whole parking area. Happy mapping!
|
| 75165237 | about 6 years ago | Hi, thanks for mapping! An important tip when mapping buildings is to use the "Q" shortcut in the iD editor to "square" your buildings after tracing - it makes for a much more professional result.
|
| 75168059 | about 6 years ago | Hi, thanks for mapping! I have a few suggestions for your edits. First, the "name" field is usually reserved for a roads actual name, so in this case, "private road" isn't the name of the road, so you would just delete the whole name tag. To indicate that the road is private, it is better to use access tags, so in this case, add a tag called "access" with the value "private" which will tell all OSM data users not to route traffic down the road. And finally, you can delete the tag "tiger:reviewed=no", which is a tag indicating that this road was imported from the US Census, but that no human has looked at it. Since you are a human and have updated the accuracy of the road, you can remove the tag. Thanks, and happy mapping.
|
| 75021701 | about 6 years ago | Hi, welcome to OSM! Thanks for improving the map around Greeley. I have a few tips that will help your mapping - one is to remember to be precise about placing points, draw roads and boundaries as precisely as you can, it will help future mappers. Second, when drawing buildings or things you know are rectangular in real life, you can hit the "Q" key in the editor after drawing, which will square up the corners, and make for a better looking addition. Happy mapping!
|
| 72327490 | about 6 years ago | Hi, this one has a lot of addresses where "Court" wasn't expanded out from "Ct", for instance, "South Wolcott Court" is shown in the import as "South Wolcott Ct". Would you mind correcting? Thanks - Sam |
| 73287313 | about 6 years ago | Hi, this import block also pulled in a lot of "North" street addresses, which can be resolved as mentioned in my other comment. Let me know if you need help. |
| 73226838 | about 6 years ago | Hi, this import block pulled in a lot of addresses with the "North" prefix still attached. Can you go in and fix? A good way to do it is to use JOSM's search functionality to find all buildings with, say, "North Inca Street" as the street, select them all, and change the whole selection to "Inca Street". Thanks - Sam |
| 74735102 | about 6 years ago | Hi Van, I've done you a solid and corrected most of the geometry and tagging errors, doing my best to preserve history, and the best traced building regardless of source. I'd encourage you to go back through the list of issues pointed out above to make sure I got them all, and correct any others. Feel free to message me if you are having a hard time with any fixes, some can be tricky. I've learned a lot about the guts of OSM by working through issues of these types. Going forward, "when in doubt, don't import" is a good rule for any building that is conflicting with something already in the database. In particular, I'd leave all multi-part buildings aside for now. The plan is to address them in a separate import once some better scripts have been developed to make them OSM compliant. Others - Thanks for pointing out the issues, I'm not an import organizer, but I have tried to help out quite a bit. The import is generally good quality (clean traces and good addresses), however, as one of the largest building imports in the country, so there are bound to be some problems. Feel free to visit the import wiki and github issues page to note challenges you are seeing. I spent a few hours last weekend re-writing a lot of the documentation to provide specific guidance for many of these situations to importers. My pull request hasn't been processed yet, but hopefully the new documentation will help new importers learn from some of these situations. |
| 74735102 | about 6 years ago | Ok, I see the problem, those buildings are of type "building=foundation/ruin", probably because they were traced while the development was still in construction, which is why they have a height of zero. They shouldn't have been imported that way. I'll update the documentation for the situation. |
| 74735102 | about 6 years ago | FYI, I just pushed a lot of updates to the workflow documentation for the DRCOG import which should help inform importers of some of these potential issues and how to correct them before importing. The DRCOG data is pretty clean, but no dataset is perfect. These height=0 buildings are a new one for me. |
| 74417547 | over 6 years ago | Hi, welcome to OSM! About the edit to your house, the only suggestion I have is that "height" tags are in meters, so if you meant 18 feet, you probably want something more like "5.5" for the height.
|
| 73814502 | over 6 years ago | Thanks for updating! The tag system is extensive, flexible, and indeed, frustrating. ;) There is a bit of an art to which tag combination is most appropriate for a feature. One thing that can help is to join the OSM US Slack Channel: https://osmus-slack.herokuapp.com/ where you can pop in and ask questions, or get another set of eyes on an issue. Folks there are quite experienced and helpful. The /r/OpenStreetMap reddit can also be a good place to ask for recommendations. Happy Mapping!
|
| 73814133 | over 6 years ago | Hi! One more tip - when drawing buildings, don't forget to use the "q" shortcut to square up the corners of your building after sketching them - it makes for a much cleaner final product.
|
| 73814502 | over 6 years ago | Hi, welcome to OSM! Thanks for your additions to Greeley. For the addition of the wildlife sanctuary, while "zoo=wildlife_park" is close, I think "leisure=nature_reserve" may be a more appropriate tag. Zoo tags, even for wildlife parks, tend to imply a secured and managed environment, usually with a defined entrance and exit, and fees or tickets needed. For a park that is defined for protection of native species, nature_reserve does a bit better job. Thanks!
|
| 73268816 | over 6 years ago | Nice work on the reservoir cleanups! Thanks!
|
| 72879760 | over 6 years ago | It would almost certainly be built along the same line (they aren't likely to change the right-of-way and access easements for PG&E), however, the poles are probably not in the same position - if the originals were destroyed then they will redesign the line with whatever current pole-type and sag calculations are in effect. |
| 72942588 | over 6 years ago | Hi, are you drawing golf courses and then deleting them? If so, we would prefer that you not do that - all changes to the map are retained in the history, and having false additions made and removed makes it hard to review the map. The maps are used by real people for real applications, so false data is not allowed in the database.
|
| 72960550 | over 6 years ago | Hi, is this really a golf course? I don't see any evidence of construction on the imagery - what is the source?
|
| 72701146 | over 6 years ago | Thanks! Happy mapping! |