Is there any way to avoid having a separate file for the content of every tile in a 3D Tile tileset? Ideally something where there could be one file and the tile content could be identified as a range in that file. Creating thousands of small files causes issues when using local storage and also when trying to upload it to a cloud data storage. We’re working around it in different hacky ways like zipping up the files before uploading and then unzipping again but it feels like this could be something the file format supported. I was hoping to see something in the latest announced version but I’m not seeing anything.
Thanks for your question. An archive format is on our roadmap, but it is not available yet. You can read about it in the 3D Tiles repository on GitHub.
In the meantime, you can use .3dtiles, which is the fastest way to get data into ion. A tool for generating .3dtiles files is available in the 3D Tiles Validator repository.
Please let us know if you have any follow-up questions.