-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
Unexpected shapes from z0 layer included in z13 tile #870
Comments
What version of tegola are you using? Can you start it with --log-level DEBUG to see if something pops up? |
I'm fairly certain I'm on v0.15.1. I didn't see any additional logs pop up when I ran the Tegola server with |
@dwoznicki Pretty sure I found the issue. Tegola does not filter by zoom level properly if min/max zoom is 0. You can validate that for me real quick. Set it to 1 for the layer in question and see if it still queries it. If so, I can fix it maybe tomorrow afternoon/evening. |
Nice! I've confirmed that changing |
Awesome @dwoznicki, when @ARolek is back we'll discuss how we fix this for good :) |
@dwoznicki thanks for the report! And @iwpnd thanks for the debugging help. Did you figure out a fix for this? |
Never mind this comment. I see you sent in a PR! |
as per go-spatial#870, setting max_zoom to 0 currently causes the layer to bleed through over the entire zoom range. Either we fix filtering as per go-spatial#871 or make sure max_zoom is never 0 as I do in this PR.
as per go-spatial#870, setting max_zoom to 0 currently causes the layer to bleed through over the entire zoom range. Either we fix filtering as per go-spatial#871 or make sure max_zoom is never 0 as I do in this PR.
With my custom layer setup, I've noticed that some tiles at higher zoom levels contain shapes from my base zoom level 0 table. This leads to some unexpected results, like the one below where I'd expect the entire 13/1314/3169 to be water.
It looks to me like this is happening for any tile that does not contain other layer data in it (you can see an extra land polygon in tile 13/1315/3170 which also should be pure water).
Here's my tegola.toml file.
I can't quite set
TEGOLA_SQL_DEBUG
to print SQL statements right now, but here's the query for tile 13/1314/3169 in my PostgreSQL log. I've split the query at||
to make it a bit more readable.It looks like Tegola makes a query to my
ntk_land_areas_z0
at the start, which is probably bringing in the extra polygon. Is there something I can do to fix this?The text was updated successfully, but these errors were encountered: