Open ghost opened 6 years ago
Just created https://github.com/gravitystorm/openstreetmap-carto/issues/3795 - consider "width" when rendering waterways.
I know I'm personally guilty of using waterway=ditch, but it's only because of the big fat river-like rendering of canals. It's horrible.
So how about this very simple solution: render it thinner if it's specifically tagged with usage=irrigation or canal=irrigation. Then the narrower rendering wouldn't affect the big navigable canals.
Should this lose "good first issue", given how it's not clear what should be done here? Although I like @gpsvisualizer's latest suggestion to latch onto canal=irrigation because of its simplicity.
"The good first issue task coming from this would be simply to choose an overall smaller line width for canals. Anything else would not be a good beginner task any more." https://github.com/gravitystorm/openstreetmap-carto/issues/3354#issuecomment-496449087
Rendering canal lines about 1/2 or 2/3rd the width of rivers would be worth trying.
Is this issue still gonna be open in 2030?
Please render
waterway=canal
thinner. The current rendering looks very strange for small irrigation canals and seems to lead people to wrongly tag them aswaterway=ditch
,waterway=drain
(which are both used for carrying superfluous water) orwaterway=stream
.Example of a 1 m wide canal (location) which is rendered ca 5 m wide at zoom 18:
See: key:waterway on the wiki the this email from the tagging mailing list (full discussion).