OpenStreetMap
chath_tsu's Comments
| Changeset | When | Comment |
|---|---|---|
| 168457528 | @Spaghetti_Monster🍝 and related - I made a challenge on MR to verify living street designations mpr.lt/c/54158 |
|
| 168457528 | yes thank you for the comment, I agree! I have since looked more closely at the definition of living streets and now working on a project to address living streets that are not in fact living streets |
|
| 177451785 | tho the bikeway on the south side of fourth plain is twoway and separated from the roadway by flexposts and amadillos so maybe it should be mapped as a separate way? |
|
| 176693741 | Thank you I appreciate it! I think (?) I fixed most thing but you are of course more than welcome to double check :) |
|
| 176693741 | Hi! I've noticed you recently added some bike lanes that you mapped as bike paths. Please note that, for bike ways to be mapped as separate ways and tagged as cycle paths, they have to be not inherently part of the roadway and physically separated from vehicle travel lanes. For a roadside bike path, there has to be physical barriers separating it from traffic (eg. curbs, jersey barriers, guardrails, planter strips). Otherwise, on-road bike lanes, including those with painted buffer but no physical barrier, are represented as cycleway= tags on the main roadway ways. You can find more information here: highway=cycleway and cycleway=*. Thanks for your effort and happy mapping! |
|
| 176786957 | I think your change is fine we dont need to revert it.
|
|
| 176786957 | Do we know if the roads on the south side are actually private access only, or are the access tags too restrictive (esp for foot?) |
|
| 176786957 | I don't think it's an issue with the footpath itself, rather it is because that the roads on the south side, Holly Pl and 33rd Pl, have private access tags, so the routing engine wouldn't route on them. If you route to the south end of the footpath it does route fine: https://maps.openrouteservice.org/#/directions/33rd%20Place%20South,Seattle,WA,USA/3312%20South%20Holly%20Place,Seattle,WA,USA/data/55,130,32,198,15,97,4,224,38,9,96,59,2,24,5,192,166,6,113,0,184,64,90,1,24,2,102,32,58,98,4,224,1,154,128,88,233,32,14,39,43,169,226,1,163,160,118,50,5,99,172,80,143,38,0,216,152,240,96,25,151,128,110,34,164,42,179,19,218,152,186,52,154,21,93,207,160,226,236,54,84,47,199,165,126,132,66,113,1,0,3,170,120,17,19,97,202,0,23,148,0,182,185,10,81,183,109,1,0,6,111,0,3,110,139,130,12,21,10,143,128,14,236,134,16,13,100,128,14,109,98,8,30,140,30,141,14,136,134,9,23,143,153,5,229,224,91,14,139,2,0,11,235,84,0,0
|
|
| 176759088 | Hi, welcome to OSM! You did a very good job with your first edit. The only minor issue I could see is that phone numbers should have the international dialing code in front - so +1 for the US. I've gone ahead and added that. Thank you and happy mapping!
|
|
| 176714717 | Hi! In this case the best course of action is to split the existing sidewalk ways (by selecting a node and press X on a keyboard, or right click and select split from the menu) into the portions you want to add the bike path, and change the tags of the sidwalks to reflect the bike addition. The "cycle and foot path" preset in the editor works well for this situation. Alternatively you could map the bike paths as separate ways; they would be mapped with their own alignments that's not overlapping with the sidewalk, but with the current lack of good aerial imagery that's not as feasible. Thank you and happy mapping!
|
|
| 176714717 | Hi! In this case the best course of action is to split the existing sidewalk ways (by selecting a node and press X on a keyboard, or right click and select split from the menu) into the portions you want to add the bike path, and change the tags of the sidwalks to reflect the bike addition. The "cycle and foot path" preset in the editor works well for this situation. Alternatively you could map the bike paths as separate ways; they would be mapped with their own alignments that's not overlapping with the sidewalk, but with the current lack of good aerial imagery that's not as feasible. Thank you and happy mapping!
|
|
| 176714980 | Hi! Just a heads up, on OSM in the US all road names are fully spelled out, including directions (Southeast instead of SE) and suffixes (Drive instead of Dr). Road numbers are represented using the ref=* tag, and the name field used if there is a name other than the road number. Thank you and happy mapping!
|
|
| 176721459 | Hi! Thanks for adding the buildings. Just a little editing trick for you - when in the editor, you can right click on a feature and select square, or press Q on a keyboard, to square the corners of a feature. That way the buildings will have right angle corners and look neater. Happy mapping!
|
|
| 176727694 | Hi! Thanks for adding the stop signs. They are largely well mapped, but they have traffic_signals=signal tags, in addition to the standard stop sign tags, that shouldn't be there. I have gone ahead and fixed the tags. Thank you and happy mapping!
|
|
| 176734106 | Hi! Thanks for contributing to the pedestrian infrastructure mapping in Portland. I wanted to note that in Oregon every intersection is legally a crosswalk, whether marked or not, unless signed otherwise. In this changeset you deleted an unmarked crossing feature. In this case, since the sidewalks are mapped as separate elements, the unmarked crossing ways serve as routable elements in routing calculations, otherwise there won't be a routable way to cross Sandy at this intersection. Please do not delete unmarked crossings like this unless there are "crosswalk closed" signs, especially in locations like this where there are curb ramps for the unmarked crossings. Thank you and happy mapping!
|
|
| 176716654 | Hi, thanks for splitting the ways! For signalized intersections involving split roadways, the best practice is to add traffic signal nodes on the incoming ways at the locations that traffic wait for the lights (stop lines if painted, edge of intersection if there are no stop lines), and add direction tags for the signals if on a 2-way road. You can find more information here highway=traffic_signals#Tag_all_incoming_ways. I have fixed the signal taggings. Thank you and happy mapping!
|
|
| 176462050 | Hi! I wanted to let you know that I am reverting this changeset of yours. I have noticed that, in this and some others of your recent edits, you have mapped turn lanes as separate link roads. Link roads are only to be mapped as separate ways if they are separated with physical barriers with the main roadways (eg bollards, curbs, grass or concrete medians but not paint-only ones), otherwise they are turn lanes and should be represented using tags on the main roadways. You can find more information here osm.wiki/Highway_link. Thank you and happy mapping! |
|
| 176617218 | Hi! Just so you know that the Seattle Processing & Distribution Center is already mapped: way/53622367
|
|
| 176617218 | Hi! Just so you know that the Seattle Processing & Distribution Center is already mapped: way/53622367
|
|
| 176594889 | Thank you for your understanding! |