revert the 2023-03-19 introduction of "one map per ZL" check - or make that...
Brought to you by:
r_x
Menu
▾
▴
#312 revert the 2023-03-19 introduction of "one map per ZL" check - or make that optional
I've checked with Orux and Locus - two major App that can handle MBtiles. Both - and I assume any other smart Geo App - can handle gaps in zoom level of a map, one way or another.
Hence I consider the "all" ZL requirement of the MBtiles spec purely academic and irrelevant in the practical world.
So my proposal is to revert the 2023-03-19 introduction of "one map per ZL" check. Even Rainer could live perfectly using the 2.3.1 (without that check) with Laurent's hint.
I FULLY DISAGREE with this request !
As I already mentioned here https://sourceforge.net/p/mobac/forum/general/thread/6599836848/?page=1#bc4c
It's not "purely academic" as @mbe57 says. These boundaries are used (at least by Oruxmaps) to correctly fulfill the feature "Switch map here".
If you have a map with a lot of zoom levels, from 6 to 16, for example, with previous algorithm, boundaries were the one of the lowest zoom 6 (since, by definition, they cover a larger area), while with the current algorithm, boundaries are the one of highest zoom 16.
And he difference may be very important. And if you click on "Switch map here" in a place not actually covered by the zoom level you are... you get an empty display, which can be very frustrating.
Moreover, even if it was "purely academic" as he says, specs of MBTiles are done to be respected and fulfilled and not ignored for the pleasure of only one guy !
And finally, this evolution is absolutely not necessary to requester @mbe57 to fulfill his process, as I have already shown him here https://sourceforge.net/p/mobac/forum/general/thread/6599836848/#93a6
So please @r_x REJECT this request.
If @mbe57 absolutely wants this evolution, he has to create his own fork of MOBAC