-
Notifications
You must be signed in to change notification settings - Fork 827
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
natural=mud appearing later than natural=sand/beach (z13 vs z10) #1018
Comments
Note that tidal tag not used by this style (see https://github.com/gravitystorm/openstreetmap-carto/blob/master/openstreetmap-carto.style - it is skipped during importing data into a database). |
Can you give an example of place where it leads to a bad rendering? |
related to #420 |
http://www.openstreetmap.org/#map=13/53.6174/0.0715 Here there is both mud and sand areas adjacent to each other. At z10, 11 & 12 only the sand is rendered, creating an 'island' of sand. In reality this is a single, continuous tidal flat. |
2014-10-07 8:46 GMT+02:00 Malcolm Herring notifications@github.com:
according to the wiki definition of the key "natural", both, sand and mud, |
@dieterdreist Well, both "mud" and "sand" are currently rendered. You may want to open a separate ticket. |
2014-10-07 14:29 GMT+02:00 Mateusz Konieczny notifications@github.com:
done |
"not according to the Wiki" Where? On the main map features page, natural=mud/sand/beach are all documented, with the renderings that do appear. Where does it say that they are "malformed"? |
I consider this as a bug caused by #420 |
#899 is next in this group. |
natural=sand/beach and tidal=yes appear at zoom 10
natural=mud and tidal=yes appear at zoom 13
The text was updated successfully, but these errors were encountered: