Bug 325168 - Different maximumTileLevel entries for layers in DGML files are not respected
Summary: Different maximumTileLevel entries for layers in DGML files are not respected
Status: RESOLVED WORKSFORME
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: 1.6 (KDE 4.11)
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-22 10:39 UTC by Rolf Eike Beer
Modified: 2023-02-01 05:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
OpenFireMap map file (5.99 KB, text/html)
2013-09-22 10:40 UTC, Rolf Eike Beer
Details
Patch to load and store clip setting in DGML files (5.52 KB, patch)
2013-10-20 10:16 UTC, Rolf Eike Beer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Eike Beer 2013-09-22 10:39:28 UTC
I have created a DGML file for OpenFireMap. OpenFireMap is a layer over OSM tiles. OSM tiles are provided up to level 18, OpenFireMap up to level 17. None of the possible combinations satisfy me.

Reproducible: Always

Steps to Reproduce:
Try the DGML file I'll attach shortly.
Actual Results:  
-both maximumTileLevel=18
  => on maximum zoom no OpenFireMap data is visible as no tiles are present
-both maximumTileLevel=17
  => on maximum zoom the OSM tiles look bad as they are scaled from the zoom 17 ones
-OSM maximumTileLevel=18, OpenFireMap maximumTileLevel=17
=> behaves like both on zoom 18

Expected Results:  
On maximum zoom the OSM tiles from zoom18 should be used together with the OpenFireMap ones from zoom 17.
Comment 1 Rolf Eike Beer 2013-09-22 10:40:02 UTC
Created attachment 82454 [details]
OpenFireMap map file
Comment 2 Rolf Eike Beer 2013-10-09 13:33:04 UTC
I was told that this behaviour is intentional to avoid showing e.g. the cloud overlay in higher zoom levels. So I think it needs a new flag to optionally enable zooming the last present tiles to higher zoom factors.
Comment 3 Rolf Eike Beer 2013-10-20 10:16:09 UTC
Created attachment 82961 [details]
Patch to load and store clip setting in DGML files

This only adds support for loading the setting, it doesn't do anything with it for the moment. I have no clue where to add that.
Comment 4 Andrew Crouthamel 2018-11-10 03:19:49 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-20 04:09:32 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2023-01-02 02:04:12 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2023-01-17 05:16:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-02-01 05:05:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!