-
Notifications
You must be signed in to change notification settings - Fork 1
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
Water polygons are not merged #35
Comments
I should merge them for tile size, but it's valid to have them unmerged. In fact, if you're dealing with multiple water=* values, they can't be fully merged. |
True, I think jawg just throws all water into one bucket. Shortbread doesn't. |
You probably want an offset polygon approach similar to the standard ways of doing strokes on roads. You should only directly style a line on a polygon if you want two of the same type of polygon to be distinct. |
Not sure what you mean. |
What you're getting will always end up happening when styling the outer line of a polygon. |
But is there another way? |
Yes - a larger fill followed by a smaller inner, the same way we do casings on roads. |
Oh, I have been using "line-gap-width" for the casing. But anyway, when using two fill layers with one of them being slightly offset to be smaller, it sounds like it would result in the same rendering as when using an offset line for the "shore". |
The StreetComplete style draws lines around water bodies as "shore lines". The various docks and canals in Hamburg are mapped in OSM each as individual neighboring polygons.
Current behavior
Neighbouring water polygons are not merged. The area around Ellerholzbrücke looks like this:
See https://streetcomplete.app/map-osm/
Expected behavior
Neighbouring water polygons are merged. The area around Ellerholzbrücke looks like this with the JawgMaps tiles:
See https://streetcomplete.app/map-jawg/
The text was updated successfully, but these errors were encountered: