This object is in archive!
Using Orux SQLites as overlays
Answered
Hi Menion,
for whatever reason, the Orux DB in many cases is much smaller than any other SQLite format for the exact same tiles and display quality. Hence it would be nice to allow that SQLite for overlays, too.
Why is that denied ?
TXs and cheers
Michael
The same question
Just guessing... but maybe your oruxmaps sqlites have jpeg tiles instead of the more commonly used png? That would be a reason for smaller sizes... not for being incompatible with Locus. Locus handles jpeg tiles nicely as far as I know.
JPEG is the preferred tile format on Android anyway. There is more hardware acceleration going on behind the scenes afaik. Mobac can e.g. be told to recompress to jpeg when downloading. Would be great if the Locus built-in map downloader and also the online map tile cache could optionally to that as well. It's only a minor addition but potentially saves 50% of SD memory without any visible artefacts. Might even be a little faster and use less battery afterwards.
Just guessing... but maybe your oruxmaps sqlites have jpeg tiles instead of the more commonly used png? That would be a reason for smaller sizes... not for being incompatible with Locus. Locus handles jpeg tiles nicely as far as I know.
JPEG is the preferred tile format on Android anyway. There is more hardware acceleration going on behind the scenes afaik. Mobac can e.g. be told to recompress to jpeg when downloading. Would be great if the Locus built-in map downloader and also the online map tile cache could optionally to that as well. It's only a minor addition but potentially saves 50% of SD memory without any visible artefacts. Might even be a little faster and use less battery afterwards.
Good day Michael,
format, that is used by Orux allows to define more map projections, not just basic projection aka "Google style". Locus currently do not do any tile re-projection on the fly, so I've disabled this type of map for overlays at all.
Thanks for understanding.
Good day Michael,
format, that is used by Orux allows to define more map projections, not just basic projection aka "Google style". Locus currently do not do any tile re-projection on the fly, so I've disabled this type of map for overlays at all.
Thanks for understanding.
I see. TXs for the background, Menion.
With joeloc's hint (to use jpg) also the other SQLite DBs shrink in size, so I can achieve my objective.
I see. TXs for the background, Menion.
With joeloc's hint (to use jpg) also the other SQLite DBs shrink in size, so I can achieve my objective.
well,
@Michal
That brings me back to http://docs.locusmap.eu/doku.php?id=manual:user_guide:maps_tools:overlays#select_your_background_map
and
http://forum.locusmap.eu/index.php?topic=5014.msg42485#msg42485
There is no described restriction in manual about sqlite maps.
well,
@Michal
That brings me back to http://docs.locusmap.eu/doku.php?id=manual:user_guide:maps_tools:overlays#select_your_background_map
and
http://forum.locusmap.eu/index.php?topic=5014.msg42485#msg42485
There is no described restriction in manual about sqlite maps.
Replies have been locked on this page!