Skip to content
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

[Feature request?] Atlas in composer doesn't render all vector features #278

Open
ChameleonScales opened this issue Feb 6, 2020 · 2 comments

Comments

@ChameleonScales
Copy link

ChameleonScales commented Feb 6, 2020

When I try to render an atlas of various places with the QGIS composer, not all vector features get rendered. It seems only those that have been loaded in the canvas do.
Furthermore, the zoom value in the canvas affects what types of features get rendered too, even though the Atlas has a fixed zoom value.
It would make sense that vector layers loaded with this plugin behaved the same way other layers do in that regard.

I assume that's a feature to be added rather than a bug. Either way, does that seem solvable?

@mnboos
Copy link
Collaborator

mnboos commented Feb 6, 2020

The plugin keeps only the visible data in the source, the others are discarded. That is by design.

I am not familiar with the Atlas tool but it is, to my best knowledge, also by design, that vector maps control feature visibility based on zoom values.

It would make sense that vector layers loaded with this plugin behaved the same way other layers do in that regard.

By that you mean that all the data is actually loaded/available?

@ChameleonScales
Copy link
Author

ChameleonScales commented Feb 7, 2020

No, what I mean is that when the atlas generates an image for a specific area and a specific zoom level, it should load the data for that area and that zoom level instead of using the data of the canvas which may be of a completely different area and zoom level.
This is already what it does with WMS, WMTS and XYZ feeds, but not with Vector Tiles Reader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants