How to store tiles about grout HOT 9 OPEN

Why not just store in sqlite blobs?

from grout.

Sidecar sqlite files? That way you avoid requiring another tool.

from grout.

@bradh

Sorry, I realized I hadn't pushed an update that sought to clarify this. If you look at the table structure for the tile_level table now you should see you can store as blobs in the database.

My question was: should we have a way to store them outside the database too?

from grout.

Outside the database could be outside of the main database. In other words have a single master database with child databases. This is pretty much the same as putting them in a zip file except you don't need to switch between sqlite and zip mode in your code.

from grout.

@pepijnve

Yes, sqlite sidecar files would be a good alternative.

from grout.

I'm good with all SQLite and master/child tables

from grout.

From Tom MacWright

table structure would look like tilesets -> tile_level -> tile_table{0..23}? Seems like the number of tables could rapidly increase if you had (tilesets)x(zoomlevels + 2) tables in a database.

Is there a good way to support master/child SQLite databases, but limit the table growth?

from grout.

If I understand it correctly the intention is to partition on tile level right? I don't think that's the best partitioning scheme though since the upper levels are very small and the lower levels are very big. Partitioning on spatial extent seems like a better idea. In other words, move branches of the quad tree to separate files rather than entire levels.

from grout.

@pepijnve

I really like this idea. Would you be able to help me define how this would work?

from grout.