chachafish's Comments
| Changeset | When | Comment |
|---|---|---|
| 60270925 | over 7 years ago | Greetings :) I'm looking at a large number of errors that have popped up on OSM Inspector associated with this changeset. For example, 2740 Steele Street is tagged as being on, "North Streeteele Street". Can you go back and correct these errors? Cheers :) https://tools.geofabrik.de/osmi/?view=addresses&lon=-104.96034&lat=39.75461&zoom=15&overlays=buildings,buildings_with_addresses,postal_code,entrances_deprecated,entrances,no_addr_street,street_not_found,place_not_found,misformatted_housenumber_lenient,nodes_with_addresses_defined,nodes_with_addresses_interpolated,interpolation,interpolation_errors,connection_lines,nearest_points,nearest_roads,nearest_areas,addrx_on_nonclosed_way |
| 60264032 | over 7 years ago | Greetings. I'm reviewing some OSM Inspector-tagged errors and quite a few errors popped up here. In the Denver grid, streets south of 1st have a prefix of "South" attached to the street name, but streets north of 1st do not have a prefix of "North". Could you go through this import and correct these addresses? Thanks :) |
| 60410532 | over 7 years ago | Greetings. I'm reviewing some OSM Inspector-tagged errors and something popped up here. The house at 2667 Downing is now tagged as being at 2667 North Downing. In the Denver grid, streets south of 1st have a prefix of "South" attached to the street name, but streets north of 1st do not have a prefix of "North". Thanks :) |
| 59887323 | over 7 years ago | No probs. If you have any questions, let me know :) |
| 59887323 | over 7 years ago | 861 Humbolt is an example of nodes attached to the building. The Belcourt Apartments across the street is an example of using interpolation. Articles on interpolation can be found on OSM Wiki. osm.org/edit#map=19/39.73050/-104.96990 |
| 59887323 | over 7 years ago | Of course, if you do not divide a building, but simply add addresses via nodes and attach them to the building, you're on solid ground :) |
| 59887323 | over 7 years ago | Once you get into multi-level apartment buildings, splits are not at all clear and if you have a 20-storey building it's completely impractical. The best way to handle that is with interior mapping. Go to the link below to see an example. Toggle through the different levels to see different floors. It's quite interesting. https://openstreetmap.cz/edit/#background=Bing&level=0&map=20.00/-104.98485/39.73924 |
| 59887323 | over 7 years ago | Dividing the building, to me, makes sense if there is an obvious break between houses or townhomes, etc. It's simply a reflection of reality. For example, 3345 West 18th Avenue, Denver. If you go to the official website of https://www.denvergov.org/Maps/map/property# you will see each house is split. Many duplexes/triplexes are the same, as the split is clear if you are viewing the houses/apartments/townhomes from the street. osm.org/#map=19/39.74553/-105.03074 |
| 59877790 | over 7 years ago | Howdy :) Welcome to openstreetmap and thank you for your additions to the map. Some of your edits popped up as errors. The road you created, County Road 154, crosses three streams. In this situation you would either create bridges over the streams or create tunnels for the streams under the road. Of course, one other option is to join the road and the stream with a node and create a ford. Also, you created a node and named it, "No Truck Turnaround!!" When we name something in OSM, it's an actual name of something, such as, "Central Park", "Monticello" or "Applebees". I think what you may be trying to do here is to create a turn restriction. You can find the rules for creating a turn restriction here: osm.wiki/Relation:restriction
|
| 59887323 | over 7 years ago | You can see every error that has been flagged by going to this link: https://tools.geofabrik.de/osmi/?view=tagging&lon=-106.09619&lat=39.61836&zoom=17&overlays=nodes_with_empty_k,ways_with_empty_k,nodes_with_empty_v,ways_with_empty_v,node_tags_with_whitespace,way_tags_with_whitespace,node_with_unusual_char,way_with_unusual_char,node_with_short_or_long_key,way_with_short_or_long_key,nonop_confusion_on_nodes,nonop_confusion_on_ways,no_feature_tag_nodes,no_feature_tag_ways,ways_without_tags Another option for creating duplexes and triplexes can be found here: osm.org/edit#map=20/39.74216/-105.02839 Can you go back and correct the flagged errors? Thanks again for your additions. If you have any questions, please don’t hesitate to ask. Cheers! :) |
| 59887323 | over 7 years ago | Additionally, if you are going to use address nodes, the address nodes need to be attached to the building they describe. If you just drag each node to the edge of the building, it will attach itself. That way, OSM knows what the address shoud be linked to. OSM flags these addresses as errors because it doesn’t know what the address is associated with. Is it the address of a building? The address of park? The address of a mailbox?, etcetera. If you attach the address node to the building, then the meaning is clear. Alternatively, you could add a tag of “building” to each address, then the meaning is clear as well. But, of course, then the problem is that you are duplicating a building tag. One on the physical building and one on the address node. Thank you for adding building levels and roof shapes. Most people don’t add so much detail. I think it’s great. One other thing about addresses, the state the address is located in should be in all upper-case letters. For example, “CO” or “KS” is correct. “Co” or “Ks” would be incorrect. |
| 59887323 | over 7 years ago | Howdy :) Thank you for your additions to the map. A number of edits you created popped up as OSM Inspector-tagged errors. In the city of Silverthorne you named addresses as “duplex” or “triplex”. These are actually descriptions, not names. It would be similar to adding a tree and giving it a name of, “tree” or naming a sidewalk, “sidewalk”. A name of a bulding would be more like, “Monticello” or “Empire State Building”. To describe a structure as a duplex, triplex, etcetera is best tagged using the tag “description”. |
| 59604791 | over 7 years ago | Cheers, buddy ;) |
| 59604791 | over 7 years ago | Howdy, Lizard Rock Trail popped up here as an error on OSM Inspector. It seems this is an untagged line and it also appears to overlap with Hankins Trail 630. Could you review this? Cheers :) |
| 51412862 | over 7 years ago | Howdy, It looks like the Fallbrook Farms residential area has been duplicated; one on top of the other. Can you take a look at this? Cheers :) |
| 59613113 | over 7 years ago | Muchas gracias por su invitación. Se lo agradezco mucho, pero por ahora no tengo tiempo para dedicarme a proyectos. A fin de cuentas hago ediciones normalmente en mi ciudad natal, Denver, Colorado. Por casualidad, voy a visitar la Ciudad de Guatemala después de aproximadamente 4-6 meses. Tengo muchas ganas de ver la región. Buena suerte con sus esfuerzos. Ciao ;) |
| 59613113 | over 7 years ago | Que tal. Ud. ha creado numeros "racetracks" cerca de La Reunion Golf Resort & Residences. Realmente son calles, no? Gracias. |
| 59513443 | over 7 years ago | Howdy :) Thank you for your contributions to the map. A node you modified in this changeset popped up as an OSM Inspector-tagged error. Ford Ranch Quarry was tagged with addr:state=CO, ele=*, gnis:county_name=*, gnis:created=*, gnis:feature_id=*, gnis:feature_type=*, and name=*. However, there was no tag explaining what the node actually was. OSM couldn't tell if the node represented a flagpole, a tree or a stop sign. I made the necessary addition of a tag, "man_made=mineshaft". Also, minimum requirements for an address tag are street name and street number. I deleted addr:state=CO for all the mines since this is redundant and incorrect without street name and street number. Cheers! :) |
| 59303363 | over 7 years ago | osm.wiki/OSM_Inspector/Views/Tagging#Name.2Fdescription_without_feature_tags |
| 59303363 | over 7 years ago | Howdy :) Thank you for your contributions to the map. Some nodes you modified in this changeset popped up as OSM Inspector-tagged errors. Edna Mine, Leona Mine, Big Sally Barber Mine, and Leadville Land District Mine were tagged with addr:state=CO, ele=*, gnis:county_name=*, gnis:created=*, gnis:feature_id=*, gnis:feature_type=*, and name=*. However, there was no tag explaining what the node actually was. OSM couldn't tell if the nodes represented a flagpole, a tree or a stop sign. I made the necessary addition of a tag, "man_made=mineshaft". Also, minimum requirements for an address tag are street name and street number. I deleted addr:state=CO for all the mines since this is redundant and incorrect without street name and street number. Cheers! :) |