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: JohnSmith [Submitted to the original trac issue database at 5.39pm, Tuesday, 8th June 2010]
Currently waterway=drain only renders as a way, it would be nice to also render any drain areas tagged as well, as many drains can be quite wide and these can now be mapped in detail from aerial imagery.
As for how they should render, not sure, might need to assume the default surface=grass and then render differently if drains are tagged with surface=concrete.
The text was updated successfully, but these errors were encountered:
Author: Ldp [Added to the original trac issue at 10.15pm, Wednesday, 16th March 2011]
waterway=drain is defined to be linear only.
You can use the combination of a linear waterway=drain + a natural=water around it to convey the true area of the drain. Similar to the way waterway=river (linear) + waterway=riverbank (area) work.
BTW: Did you change the tagging in that example area? The north-south bit of drain shows up wide enough.
Reporter: JohnSmith
[Submitted to the original trac issue database at 5.39pm, Tuesday, 8th June 2010]
Currently waterway=drain only renders as a way, it would be nice to also render any drain areas tagged as well, as many drains can be quite wide and these can now be mapped in detail from aerial imagery.
As for how they should render, not sure, might need to assume the default surface=grass and then render differently if drains are tagged with surface=concrete.
The text was updated successfully, but these errors were encountered: