waterway=lock chevrons have random orientation #2915
Comments
Author: osm[at]petschge.de That tile looks fine and the lock should always point with the pointy and towards upstream of the waterway... |
Author: malcolm.herring[at]btinternet.com Sorry, I seem to have pointed to a good one. Try this: http://b.tah.openstreetmap.org/Tiles/tile/16/32575/21109.png What I see is: Downstream chevron is at right angles to way (points to bank). |
Author: malcolm.herring[at]btinternet.com OK, now this is wierd - that same tile now shows the upstream chevron with the correct orientation. (The downstream one is still at right angles). I will attach the PNG file rather than the link. |
Author: malcolm.herring[at]btinternet.com ... and now it has reverted to the orientation I originally reported. See second attachment. |
Author: osm[at]petschge.de Ok, I see what you mean. I'll look into it. http://www.openstreetmap.org/?lat=53.78238&lon=-1.05883&zoom=17&layers=0B00FTFT |
Author: osm[at]petschge.de Hrm. That might at heart be a duplicate of #1982. |
Author: malcolm.herring[at]btinternet.com That fits with the situation at the downstream gate, but not the upstream gate. The only ways attached to that node are in line with each other. Also, why does it change from render to render? I have edited that downstream gate node so that the way which is at right anlges to the lock way does not have a node at that point. If the problem on that gate goes away, then that would be an example of #1982. However, the upstream gate variable orientation would appear to be a separate problem. |
Author: malcolm.herring[at]btinternet.com ... and that did undo the right-angle orientation, but it still is not correct. (See third file attached) |
Author: petschge (In [21673]) Make sure that lock chevrons only are oriented along k=waterway |
Reporter: malcolm.herring[at]btinternet.com
[Submitted to the original trac issue database at 9.40pm, Sunday, 25th April 2010]
eg. http://b.tah.openstreetmap.org/Tiles/tile/17/64992/42018.png
The text was updated successfully, but these errors were encountered: