BTW, Great job with this!
I am working on a project for my trucker buddies in Alaska - who deal with pretty extreme weather / road conditions (winter mostly).
I have a database of all the hi-ways / roads in Alaska - along with ALL the Mile Posts (lat / lon) for each.
In a loop, I feed these locations to the map (for each zoom level - 10 to 17) which generates (downloads) each tile and saves them to the tiles.db3.
Right now, my DB is over 1.5 GB in size!
I wrote an app that will MOCK the locations using the new FusedProviderClientGMS.
Question 1.
OSM class uses GPS currently. I would like to use FPC_GMS exclusively. I should be able to work this out, but any tips grateful.
Question 2.
What is the meaning of the structure for the t_tiles table in tiles.db3 (how does the map figure out what records to use each time)?
Question 3.
I guess this is rather obvious, but how can I define a few major roads and load them into a separate DB table, to reduce the size (from 1.5 GB down to a couple of MB)?
One way is to empty the t_tiles, drive the few roads with the MOCK app - then name, save and copy the DB to a different location for distribution.
Any advise gratefully accepted from you geniuses out here in B4X land.
Harris
I am working on a project for my trucker buddies in Alaska - who deal with pretty extreme weather / road conditions (winter mostly).
I have a database of all the hi-ways / roads in Alaska - along with ALL the Mile Posts (lat / lon) for each.
In a loop, I feed these locations to the map (for each zoom level - 10 to 17) which generates (downloads) each tile and saves them to the tiles.db3.
Right now, my DB is over 1.5 GB in size!
I wrote an app that will MOCK the locations using the new FusedProviderClientGMS.
Question 1.
OSM class uses GPS currently. I would like to use FPC_GMS exclusively. I should be able to work this out, but any tips grateful.
Question 2.
What is the meaning of the structure for the t_tiles table in tiles.db3 (how does the map figure out what records to use each time)?
Question 3.
I guess this is rather obvious, but how can I define a few major roads and load them into a separate DB table, to reduce the size (from 1.5 GB down to a couple of MB)?
One way is to empty the t_tiles, drive the few roads with the MOCK app - then name, save and copy the DB to a different location for distribution.
Any advise gratefully accepted from you geniuses out here in B4X land.
Harris