Skip to content
This repository has been archived by the owner. It is now read-only.

[amenity-symbols] Adding rendering for (major) waterfalls #2954

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 6 comments
Closed

[amenity-symbols] Adding rendering for (major) waterfalls #2954

openstreetmap-trac opened this issue Jul 23, 2021 · 6 comments

Comments

@openstreetmap-trac
Copy link

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Reporter: SK53
[Submitted to the original trac issue database at 8.55am, Wednesday, 12th May 2010]

In various parts of the world major waterfalls are conspicuous landscape features and tourist attractions. Mapnik fails to render these at all with the result that certain waterfalls have been 'tagged for the renderer': e.g., Iguazu and Rheinfalle.

It is suggested that waterfalls pretty much fall in the same class as cliffs and barriers and can be treated using the same rules. Furthermore the type of line symbolizer required for waterfalls is similar to that of cliffs (a line, with some ornamentation on the lower (downstream) side).

Light experimentation suggests that the following changes are required:

  1. Create 2 new line symbols "wfall.png" and "wfall2.png". Example of latter attached.

  2. Create a new style, along these lines (basically 'cliffs')

    <Style name="waterfalls"> ([waterway]='waterfall') 25000 100000 ([waterway]='waterfall') 25000 </Style>
  3. Alter the layer 'line features' along the following lines

    cliffs waterfalls barriers mapnik true localhost mapnik 5432 (select way,barrier,"natural",man_made, waterway from planet_osm_line where barrier is not null or "natural" in ('hedge','cliff') or man_made='embankment' or (waterway='waterfall')) as roads postgis mapnik
@openstreetmap-trac
Copy link
Author

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Author: steve8[at]mdx.ac.uk
[Added to the original trac issue at 7.13pm, Saturday, 5th June 2010]

Can I have a couple of URL examples please?

@openstreetmap-trac
Copy link
Author

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Author: SK53
[Added to the original trac issue at 11.45am, Sunday, 20th June 2010]

Sorry should have added these ages ago:

  1. Niagara Falls: [http://www.openstreetmap.org/?lat=43.08098&lon=-79.06946&zoom=15&layers=B000FTF]

  2. Iguazu: [http://www.openstreetmap.org/?lat=-25.68829&lon=-54.44562&zoom=15&layers=B000FTF]

  3. Victoria Falls: [http://www.openstreetmap.org/?lat=-17.91738&lon=25.85565&zoom=15&layers=B000FTF]

  4. Rhine Falls: [http://www.openstreetmap.org/?lat=47.6779&lon=8.615&zoom=17&layers=B000FTF]

@openstreetmap-trac
Copy link
Author

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Author: Federico Explorador
[Added to the original trac issue at 5.48pm, Tuesday, 1st March 2011]

I support the request for rendering waterfalls.
However, I would prefer a polygon for tagging, because many waterfalls are not vertical, but inclined and may descent on a longer way. So also rapids could included.

@openstreetmap-trac
Copy link
Author

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Author: RicoZ
[Added to the original trac issue at 11.22pm, Saturday, 9th November 2013]

Did everyone completely forget this ticket? Waterfalls are still not rendered at all. Even shoving a simple stupid icon would be a progress.

@openstreetmap-trac
Copy link
Author

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Author: RicoZ
[Added to the original trac issue at 7.02pm, Sunday, 1st December 2013]

Created http://wiki.openstreetmap.org/wiki/Waterfalls

@openstreetmap-trac
Copy link
Author

@openstreetmap-trac openstreetmap-trac commented Jul 23, 2021

Author: math1985
[Added to the original trac issue at 5.44pm, Monday, 14th April 2014]

This issue is now discussed on Github:
gravitystorm/openstreetmap-carto#336

Therefore, I will close the issue here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant