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
Not a huge deal, but having the bounds and center coordinates in the metadata would make it slightly faster for my use case. My tile server indexes the MBTiles files in a given directory then uses the bounds and/or center values to find the required file when it receives a request.
Here's what tilemaker sets as metadata for those values:
If processing single area chart(s), the app will now add bounds and center values to the metadata table in each mbtiles database.
These new metadata fields will be not be present if processing any of the full charts, since those are actually comprised of multiple individual geotiffs which each have individual extent data, making any overall calculation of extents more involved than I have time or inclination to deal with.
Apologies - I was out for part of the weekend. I was specifically referring to the bounds for individual VFR sectionals. What you've added is exactly what I needed. Thank you very much!
Not a huge deal, but having the bounds and center coordinates in the metadata would make it slightly faster for my use case. My tile server indexes the MBTiles files in a given directory then uses the bounds and/or center values to find the required file when it receives a request.
Here's what tilemaker sets as metadata for those values:
The text was updated successfully, but these errors were encountered: