-
Notifications
You must be signed in to change notification settings - Fork 34
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
Lake intersecting viewport is rendered wrong #143
Comments
Some observations in relation to the lake rendering
At first I thougth it's because of the 'layering' of the lake with a swimming area also mapped there, but I now think it might have something to do with a wetland polygon in the vicinity. |
Hello, @habi! Thank you for the issue. I'm afraid, this is really a hard one. Map Machine downloads only ways that at least partly present inside boundary box, so it doesn't have enough information about lake shape. I may provide two ways to fix that:
I think, I want to start with the first one and then will continue with the second one. |
There's no option for 'discarding' a feature (the lake) in map-machine? |
Sure, you just need to either edit default scheme file or use a custom scheme file. E.g. use map-machine render --coordinates=46.805,6.715 --zoom=16 --output=out/bad0.svg --scheme no_water.yml
- tags: {natural: water}
exception: {intermittent: "yes"}
style:
- fill: water_color
- # stroke: water_border_color
- # stroke-width: 1.0
+ # fill: water_color
+ stroke: water_border_color
+ stroke-width: 1.0
priority: 21.0 |
This is a duplicate of #120. |
I'd like to produce a high-resolution render of a campsite and can do this by issuing
map-machine render --boundary-box=6.712,46.802,6.723,46.807 --zoom=16 --output=out/vd8.svg
.This does render the lake bordering the campsite weirdly, e.g. glitches out with the intersection of the campsite.
I know that rendering of lakes or larger water bodies is complicated, but how could I generate a nice map of this campsite?
The text was updated successfully, but these errors were encountered: