Replies: 2 comments 2 replies
-
I should ask this in discussion, Sorry, for that. I'd be happy if you delete this |
Beta Was this translation helpful? Give feedback.
-
@orttak you may want to try debugging steps to see the actual query being ran. To make logging a bit more "sane", first figure out which tile is causing problems, and try to get just that one tile at different zoom levels. This way you will see what PostgreSQL query is being made. Martin has almost no logic when making these queries - it simply asks PG for all geometries in a given area (computed with ST_TileEnvelope), and lets PG encode those geometries as tiles. |
Beta Was this translation helpful? Give feedback.
-
I noticed that when I zoom in to the same spatial area, the number of polygons generated varies between zoom levels. For example, at zoom level 13, I get 3 polygons, but when I zoom in to level 14, I only see 2 polygons, and the previous 3 polygons are no longer visible.
As a newbie in Martin, I'm unsure if this behavior is expected or if there might be some configuration or setting that I need to adjust. I would appreciate any guidance or insights regarding this issue.
Furthermore, I would like to know if there is a more detailed version of Martin available that provides additional documentation or explanations about its behavior and usage.
Additionally, I would like to inquire if there is an active community around Martin, such as a Gitter or Discord group, where I can seek support, discuss questions, and interact with other users of the tool.
zoom level = x

zoom level = x+1

Beta Was this translation helpful? Give feedback.
All reactions