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

Spurious WMS Requests when adding a new layer #28856

Closed
qgib opened this issue Jan 20, 2019 · 3 comments
Closed

Spurious WMS Requests when adding a new layer #28856

qgib opened this issue Jan 20, 2019 · 3 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@qgib
Copy link
Contributor

qgib commented Jan 20, 2019

Author Name: Jonathan Moules (Jonathan Moules)
Original Redmine Issue: 21037
Affected QGIS version: 3.4.3
Redmine category:web_services_clients/wms


If I add a WMS layer, QGIS requests it and renders it.
If I add a second WMS layer, QGIS requests the new layer, but also requests the OLD layer too (as a separate GetMap request).
If I add a third layer (from a completely different service), QGIS sends requests off separate GetMap requests for all THREE layers.

There's no panning/zooming/resizing etc. going on here.

Surely QGIS should be using the cached versions of the earlier layers when a new layer is added? I can see this wasting a lot of bandwidth at both ends.

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers labels May 25, 2019
@gioman
Copy link
Contributor

gioman commented Mar 9, 2022

Is this relevant in recent QGIS releases?

@gioman gioman added the Feedback Waiting on the submitter for answers label Mar 9, 2022
@github-actions
Copy link

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Mar 24, 2022
@github-actions
Copy link

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Data Provider Related to specific vector, raster or mesh data providers Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

No branches or pull requests

2 participants