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 tileset would be packed into a single-file archive format similar to COG or Zip where tile byte ranges are stored in its header, which could be partially or wholly downloaded to the client, and then used to make HTTP range requests into the binary body when fetching tiles.
This should work for both tileset.json and implicit tiling (#92), but the tile range mapping in the header might look different.
This should be a design consideration for the archive format #89 as well as an optimization for downloading multiple children in a single request #9 since HTTP range requests allow you to request multiple non-contiguous chunks.
The text was updated successfully, but these errors were encountered:
Conceptually this would be similar to a Cloud Optimized GeoTIFF but for 3D tiles.
The tileset would be packed into a single-file archive format similar to COG or Zip where tile byte ranges are stored in its header, which could be partially or wholly downloaded to the client, and then used to make HTTP range requests into the binary body when fetching tiles.
This should work for both tileset.json and implicit tiling (#92), but the tile range mapping in the header might look different.
This should be a design consideration for the archive format #89 as well as an optimization for downloading multiple children in a single request #9 since HTTP range requests allow you to request multiple non-contiguous chunks.
The text was updated successfully, but these errors were encountered: