You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: Jonathan Bennett [Submitted to the original trac issue database at 3.43pm, Sunday, 15th November 2009]
Ways which have oneway=yes tagged have arrows shown to indicate their direction, which is nice. However, there are some classes of way (and I'm thinking of waterway=river and waterway=stream here) where the directionality is implicit, rather than explicitly tagged. These should have arrows, too.
Now, what should really happen is that PL is able to look up the definition of each tag using an API of some sort and get back data saying the tag implies directionality. However, until that's available, how's about a nasty, horrible hack to achieve the same thing?
The text was updated successfully, but these errors were encountered:
Author: Richard [Added to the original trac issue at 7.50am, Monday, 16th November 2009]
Not sure about the API or indeed anything that implies trusting wiki-fiddlers'� tag definitions. ;)
Good idea though I think it'd work better as an option rather than a default: drawing the arrows is quite slow, so it would significantly slow down redraw speed in areas where lots of rivers have been traced.
Author: Richard [Added to the original trac issue at 11.05pm, Sunday, 7th March 2010]
On balance I think "nasty horrible hacks" are best achieved by custom stylesheets in Potlatch 2, and my time is better spent finishing the latter rather than creating the former. :)
Reporter: Jonathan Bennett
[Submitted to the original trac issue database at 3.43pm, Sunday, 15th November 2009]
Ways which have oneway=yes tagged have arrows shown to indicate their direction, which is nice. However, there are some classes of way (and I'm thinking of waterway=river and waterway=stream here) where the directionality is implicit, rather than explicitly tagged. These should have arrows, too.
Now, what should really happen is that PL is able to look up the definition of each tag using an API of some sort and get back data saying the tag implies directionality. However, until that's available, how's about a nasty, horrible hack to achieve the same thing?
The text was updated successfully, but these errors were encountered: