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
Running into a situation where there's a large mbtiles file that is hard to import on a mobile device due to its size. in theory, one could split the file into a few smaller files and import them separately to create the same resulting map. unfortunately, the current implementation does not support this because each time we extract the metadata and convert to a tilejson format, we create a new id, so each import would create a new map instead of updating the same one.
Proposed solution is to update the id generation in mbTilesToTileJSON to support a user adding a custom MAPEO_ID metadata field to the mbtiles metadata table, which could then be used to determine the id i.e.
id: metadata.MAPEO_ID||generateId(),
The text was updated successfully, but these errors were encountered:
Running into a situation where there's a large mbtiles file that is hard to import on a mobile device due to its size. in theory, one could split the file into a few smaller files and import them separately to create the same resulting map. unfortunately, the current implementation does not support this because each time we extract the metadata and convert to a tilejson format, we create a new
id
, so each import would create a new map instead of updating the same one.Proposed solution is to update the id generation in
mbTilesToTileJSON
to support a user adding a customMAPEO_ID
metadata field to the mbtiles metadata table, which could then be used to determine the id i.e.The text was updated successfully, but these errors were encountered: