You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the user wants to use multiple mbtiles databases (like a mosaic). These multiple mbtiles cover a specific area of interest. Suppose that I want to cover the area of Italy and France and for that I want to use italy.mbtiles and france.mbtiles databases.
the user wants (from the client application) to make a call without specify the database of interest (because he does not know)
a new API /{z}/{x}/{y} should manage both databases and return the correct tile.
I am supposing to work in this way:
add a watcher for changes in the folder containing mbtiles (in case a new database is added/removed/updated). In case update in memory metadata info of each database (mainly the BBOX)
inside the new route /{z}/{x}/{y} do the following steps:
from the z, x, y parameters determine the bbox of the request
check wich databases cover the request and return an array sorted by the max probability to find the correct one at the first shoot (maybe the minimum distance between the baricenter of the tile and baricenters of the BBOX covered by the databases)
execute the query to the current database (in a loop). If the query returns data BREAK and return the tile to the requester, otherwise move to the other database in the loop (if exists).
Do you think it could be interesting for this project?
Otherwise I will do it only on my forked project.
The text was updated successfully, but these errors were encountered:
This is the use case of interest.
I am supposing to work in this way:
Do you think it could be interesting for this project?
Otherwise I will do it only on my forked project.
The text was updated successfully, but these errors were encountered: