Support for rmap 1024x1024 tiles
Gathering feedback
Hi, I create my own charts in Global Mapper and export to a sqlitedb file in rmap format with tile size of 1024x1024 - and I think Locus is trying to display them as 256x256 tiles.
This means that to stop the app crashing I need to set the map zoom level to x4
I know the simple solution would be to export my tiles at 256x256 but it already takes over 24 hours to export my chart and dropping the tile size would increase the export time by a couple of days.
Are you able to add support for larger tiles? - I can provide a small test file if it would help.
regards,
Brian.
I like this idea 
Hello Brian,
Locus currently do not support other then 256x256 tiles. Create me a small file and I'll check what I may do.
Hello Brian,
Locus currently do not support other then 256x256 tiles. Create me a small file and I'll check what I may do.
Many thanks - I will post a file tonight when I get home.
Many thanks - I will post a file tonight when I get home.
Hi Menion,
attached are two samples - one at tile size of 1024x1024 and the other at tile size 256x256
regards,
Brian.
Hi Menion,
attached are two samples - one at tile size of 1024x1024 and the other at tile size 256x256
regards,
Brian.
Hello Brian,
I'm worried this won't work in a way you expect.
SQLite databases use predefined size of map for every zoom level. It means at level 0, it is 256x256px, at level 1 it is double, so 512x512 etc. As I look on your map, you simply increased size of map tiles to 1024x1024, but all other parameters remains same.
If I think correctly, what you need to make this work, is at least change of indexes of every map tiles. So they should be divided by four to correctly match it's position.
Check this http://www.maptiler.org/google-maps-coordinates-tile-bounds-projection/
For example zoom 2 - 4x4 tiles you see? So it means 1024x1024 pixels. But in your case, it should be only one tile! Etc.
Hope it is clear.
I'm not saying that Locus will then work correctly. It won't. But I'll be at least able to test this map and make this work.
Hello Brian,
I'm worried this won't work in a way you expect.
SQLite databases use predefined size of map for every zoom level. It means at level 0, it is 256x256px, at level 1 it is double, so 512x512 etc. As I look on your map, you simply increased size of map tiles to 1024x1024, but all other parameters remains same.
If I think correctly, what you need to make this work, is at least change of indexes of every map tiles. So they should be divided by four to correctly match it's position.
Check this http://www.maptiler.org/google-maps-coordinates-tile-bounds-projection/
For example zoom 2 - 4x4 tiles you see? So it means 1024x1024 pixels. But in your case, it should be only one tile! Etc.
Hope it is clear.
I'm not saying that Locus will then work correctly. It won't. But I'll be at least able to test this map and make this work.
Hi Menion,
Thanks for your reply.
Unfortunately I did not design Global Mapper :-) and I do not have any options on export except to choose the zoom levels to include and the tile size.
There are three tile size options:
256x256
512x512
1025x1024
As stated before I use the 1024px tiles because it processes the sqlitedb file in around 24 hours rather than several days to produce the file with 256px tiles.
I will give this information to Global Mapper as they may have designed the export routines incorrectly.
Hi Menion,
Thanks for your reply.
Unfortunately I did not design Global Mapper :-) and I do not have any options on export except to choose the zoom levels to include and the tile size.
There are three tile size options:
256x256
512x512
1025x1024
As stated before I use the 1024px tiles because it processes the sqlitedb file in around 24 hours rather than several days to produce the file with 256px tiles.
I will give this information to Global Mapper as they may have designed the export routines incorrectly.
If I wrote at http://help.locusmap.eu/topic/htc-one-android-ver4-4-2
I'm sure there are some issue inside this sqlite - build with an 3rd party tool.
I played little bit with map on different viewer and tools (mobac, MAPC2MAPC,...) to rebuild - with no succes.
Why Locus should load this "corrupt" file? Think you waste your time...
If I wrote at http://help.locusmap.eu/topic/htc-one-android-ver4-4-2
I'm sure there are some issue inside this sqlite - build with an 3rd party tool.
I played little bit with map on different viewer and tools (mobac, MAPC2MAPC,...) to rebuild - with no succes.
Why Locus should load this "corrupt" file? Think you waste your time...
Replies have been locked on this page!