-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Wrong boundingbox values in GetCapabilities for empty layers #15120
Comments
Author Name: Paolo Cavallini (@pcav)
|
Author Name: Bernhard Ströbl (Bernhard Ströbl) I raised this bug in priority because it is annoying Proposed solution: if layer delivers a bbox larger than the bbox set in the OWS server tab the bbox set in OWS server is returned (IMHO it does not make sense to have layers propagating larger bboxes than the project does)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Paul Blottiere (Paul Blottiere)
|
Author Name: Paul Blottiere (Paul Blottiere) Applied in changeset da22f7c.
|
Author Name: zicke - (zicke -)
Original Redmine Issue: 5520
Affected QGIS version: master
Redmine category:qgis_server
Assignee: Paul Blottiere
For layers without any feature the bbox calculation for the GetCapabilities request is wrong. The result is some 'nonsense' bbox value. You can still use the wms layer with a correct bbox but QGIS fails to load groups (or the whole wms 'tree') with empty layers since the group bbox is wrong too.
Related issue(s): #18798 (relates)
Redmine related issue(s): 10379
The text was updated successfully, but these errors were encountered: