StackKorora have been discussed with 18 replies of this contributorStackKorora have been discussed with 18 replies of this contributor| Changeset | # | Tmstmp UTC | Contributor | Comment |
|---|---|---|---|---|
| 64097785 by StackKorora @ 2018-11-02 01:30 | 1 | 2024-03-07 15:36 | Mateusz Konieczny ♦7,666 | Hello!You useddirection=forward;0on https://www.openstreetmap.org/node/192409556/historyHave you maybe meantdirection=forward?I am pretty sure that it is a typo, but not sure enough to just replace it (I edited some objects where situation seemed more clear to me).Or have you... |
| 2 | 2024-03-07 23:24 | StackKorora | Greetings,Coming from NW Roanridge Road a driver has no stop sign going either North (Colrain) or East (56th). If you are traveling West bound on NW 56th street, there is a stop sign. This is represented by 'forward'. However, forward will not be represented when traveling South boun... | |
| 3 | 2024-03-08 10:45 | Mateusz Konieczny ♦7,666 | Oh thanks for info! That makes sense.I guess that it is a good thing that I posted only a confused message rather than blindly trying to "fix" it.Though sorry for the message about supposed typo. | |
| 4 | 2024-03-09 00:32 | StackKorora | No worries! Glad you asked too. Happy mapping! | |
| 136391490 by StackKorora @ 2023-05-22 01:41 | 1 | 2023-12-26 04:54 | DUGA ♦549 | Drop the useless source tag. |
| 132209857 by StackKorora @ 2023-02-07 14:46 | 1 | 2023-02-12 23:27 | flyingember ♦9 | FYI- there's upcoming closures. they aren't putting signs up ahead of time |
| 2 | 2023-02-12 23:28 | flyingember ♦9 | SB I-35 is closing in less than a month, for example | |
| 3 | 2023-02-13 13:25 | StackKorora | True. I'm aware of those, but the roads aren't closed now and I'd rather not mess with the routing for those that use those directions until the roads actually close. I also know that some of them are short-term closures and some are going to be long-term. I was trying to be helpful i... | |
| 121488268 by StackKorora @ 2022-05-25 18:30 | 1 | 2023-01-16 14:33 | tekim ♦696 | Thanks for the edits. Regarding Lumpy Ridge Road and associated features, I would be careful about adjusting long existing features to imagery. Locals have generally used a combination of a variety of sources, including imagery, GPX traces, and the Strava Global Heatmap to ensure spatial accuracy.... |
| 105452585 by StackKorora @ 2021-05-27 22:33 | 1 | 2021-07-30 21:20 | tekim ♦696 | I highly doubt that this trail:https://www.openstreetmap.org/way/840670704Has a compacted surface in the OSM sense: "A mixture of larger (e.g., gravel) and smaller (e.g., sand) parts, compacted (e.g., with a roller)" - The park service is not dragging a road compacter/roller into the b... |
| 2 | 2021-07-31 21:05 | StackKorora | I walked those trails. I know what they were like. The trails are a mix of small rock and dirt that has been compacted into a dense firm path that is clearly distinguishable from the ground around it. That's why I chose that option. I don't really care if you relabel them as ground, but th... | |
| 105440342 by StackKorora @ 2021-05-27 17:16 | 1 | 2021-05-28 15:27 | tekim ♦696 | Many of these trails that you have tagged surface=compacted are not. They are informal climbers trails, Nothing has been done to improve them, so they are surface=ground or dirt or unpaved --- Published using OSMCha: https://osmcha.org/changesets/105440342... |
| 2 | 2021-05-29 19:00 | StackKorora | Thanks for the feedback. | |
| 3 | 2021-05-30 14:15 | tekim ♦696 | Thanks for being open to feedback, and thanks for all of your other great contributions to OSM. It is great seeing RMNP getting some mapping attention!There are going to be very few, if any, trails in RMNP where surface=compacted. | |
| 89933642 by StackKorora @ 2020-08-25 20:24 | 1 | 2021-05-28 15:17 | tekim ♦696 | Thanks for your contributions to OpenStreetMap. Regarding: https://www.openstreetmap.org/way/840670701, a "bus_guideway" is for "busway that is side guided "rails like" for the exclusive use of guided buses" - there are no guides here, it is just a regular road that is... |
| 2 | 2021-05-29 19:03 | StackKorora | Good catch. That was a mistag on my part. Thanks! | |
| 105253346 by StackKorora @ 2021-05-24 23:12 | 1 | 2021-05-28 18:39 | tekim ♦696 | The trail from Bear Lake to the junction with the Flat Top Mountain Trail is certainly not surface=compacted - no surface treatment has been done. I have been on this trail many times. --- Published using OSMCha: https://osmcha.org/changesets/105253346 ... |
| 75591828 by StackKorora @ 2019-10-12 04:47 | 1 | 2019-10-21 19:41 | user_5359 ♦19,440 | Hello! Please check the value of maxspeed on https://www.openstreetmap.org/way/90282475. The existing value is slightly higher than the speed previously reached by a car. |
| 2 | 2019-10-22 03:21 | StackKorora | Ha! Thanks for the catch. Sorry about the typo. | |
| 70773708 by StackKorora @ 2019-05-30 14:41 | 1 | 2019-06-06 03:25 | Baloo Uriza ♦2,121 | Is it really full, like the gates go across all four lanes on both sides? Half is far more common in the US. --- Published using OSMCha: https://osmcha.mapbox.com/changesets/70773708 |
| 2 | 2019-06-06 03:44 | StackKorora | Good question. I don't remember honestly and I was just passing through. A friend lives near by. I've asked him to confirm that I didnt hit the wrong button. I will update if/when I hear back. :-) | |
| 3 | 2019-10-11 03:53 | StackKorora | I was finally able to verify first hand. Fixed it in an update a few hours ago. Thanks for the catch. | |
| 61760594 by StackKorora @ 2018-08-18 01:17 | 1 | 2018-08-18 01:18 | StackKorora | Dah! I clicked the review button on accident. Please close this. There is no reason for a review. |
| 60778963 by StackKorora @ 2018-07-17 00:40 | 1 | 2018-07-20 01:12 | Baloo Uriza ♦2,121 | Don't forget OSM uses metric units by default, to specify mph, you must add "mph", ie, maxspeed=70 mph --- #REVIEWED_BAD #OSMCHA Published using OSMCha: https://osmcha.mapbox.com/changesets/60778963 |
| 2 | 2018-07-20 01:36 | StackKorora | Thanks. Overlooked these. Good catch. Fixed. --- #REVIEWED_BAD #OSMCHA Published using OSMCha: https://osmcha.mapbox.com/changesets/60778963 | |
| 60744573 by StackKorora @ 2018-07-16 03:11 | 1 | 2018-07-16 03:12 | StackKorora | Sorry for wasting your time. I checked the box by accident by clicking too fast. This was a super simple edit. |
| 60714785 by StackKorora @ 2018-07-14 15:40 | 1 | 2018-07-14 19:37 | sannkc ♦105 | Good job spotting this. You can use the tag busway=opposite_lane here. More info: https://wiki.openstreetmap.org/wiki/Key:busway https://wiki.openstreetmap.org/wiki/Tag:busway%3Dopposite_lane |
| 2 | 2018-07-14 22:36 | StackKorora | Thanks! Fixed. Also, if you ever want to join us on the slack channel, there is a sub-channel for #kansascityosm that we would be happy to have you in. | |
| 59887323 by StackKorora @ 2018-06-16 02:50 | 1 | 2018-06-17 12:54 | chachafish ♦462 | 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... |
| 2 | 2018-06-17 12:54 | chachafish ♦462 | 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 becaus... | |
| 3 | 2018-06-17 12:55 | chachafish ♦462 | 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... | |
| 4 | 2018-06-17 16:58 | StackKorora | Thanks for the clarifications. I didn't know about the address points. I can fix those. As for the State letters, I had wondered if that was correct but I was just being lazy and selecting what was in the drop down box. I will fix those too. :-)Thanks again for clarifying. | |
| 5 | 2018-06-17 17:04 | StackKorora | A follow up question. When I asked about how to do duplexes in IRC about a year ago, the advice I was given was how I was doing it. They also told me specifically to not break up the building as in the example you cited. I added the duplex name so that others would know why I associated so many addr... | |
| 6 | 2018-06-17 22:40 | chachafish ♦462 | 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 ... | |
| 7 | 2018-06-17 22:42 | chachafish ♦462 | 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 flo... | |
| 8 | 2018-06-17 22:46 | chachafish ♦462 | 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 :) | |
| 9 | 2018-06-17 22:54 | chachafish ♦462 | 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. https://www.openstreetmap.org/edit#map=19/39.73050/-104.96990 | |
| 10 | 2018-06-19 00:27 | StackKorora | Thanks for all the information. I really appreciate it. I've been able to fix a bunch of multiplexes recently with this new info. And that one multi-level building is quite amazing. | |
| 11 | 2018-06-19 01:51 | chachafish ♦462 | No probs. If you have any questions, let me know :) | |
| 54191511 by StackKorora @ 2017-11-29 23:07 | 1 | 2017-12-04 03:11 | UAN51 ♦15 | Your tags that has "source=maxspeed=sign" is unnecessary and unsupported. Same with nodes of "traffic_sign=maxspeed". It only creates a redundancy and inefficient noding. "maxspeed=xx mph" is already enough on the roadway. Renderers and navigation systems will not suppo... |
| 2 | 2017-12-04 13:16 | StackKorora | I did that because the wiki says: "When mapping a speed limit sign for example: always add a maxspeed=* and a source:maxspeed=sign tag to the road itself. "http://wiki.openstreetmap.org/wiki/Key:traffic_signDid I do it wrong or is the wiki wrong? I need to know because I've been... | |
| 3 | 2017-12-04 19:26 | UAN51 ♦15 | Wiki is wrong. Mapbox, osm-carto, Telenav, and others do not support node "traffic_sign=maxspeed" and "source=maxspeed=sign". This "traffic_sign=maxspeed" is only creating node inefficiency. "maxspeed=xx mph" already exists on roads so there is no need to make... | |
| 4 | 2017-12-04 23:12 | StackKorora | Thanks for the information. How do we get the wiki corrected then? | |
| 54110560 by StackKorora @ 2017-11-27 04:16 | 1 | 2017-11-27 05:44 | user_5359 ♦19,440 | Welcome to OSM! A maxspeed sign doesn't have a name! |
| 2 | 2017-11-27 05:47 | user_5359 ♦19,440 | and don't forget the maxspped value on the road (see https://wiki.openstreetmap.org/wiki/Key:traffic_sign) | |
| 3 | 2017-11-28 03:54 | StackKorora | Thanks for the feedback! I captured a bunch of speed limit signs recently. I will make sure to update the road as well. | |
| 44068862 by StackKorora @ 2016-11-30 20:09 | 1 | 2017-10-31 02:26 | VlIvYur ♦149 | https://www.openstreetmap.org/way/456838308Is there really 10300 levels? |
| 2 | 2017-10-31 03:01 | StackKorora | Good Catch. Sorry, wrong field. Should be address. I'll fix. |