Hi all, ioners!
we are facing some compatibility issues with a viewer based on THREE.js that uses 3DTilesRenderer by NASA AMMOS.
Problem is some features of 1.1 specification are not (yet) supported (e.g. implicit tiling) even if active development is ongoing.
I know this is a completely natural evolution and the 1.1 specification is really great - but, is there a specific reason why the switch 1.0/1.1 was removed from ion interface?
Would it be possibile to use the previous tiler somehow (even via REST API) while these THREE.js open-source projects fully catch up with 1.1 specification?
The short answer is we wanted our users to have the best performance and quality. The new format allows us to provide a number of performance improvements that are not possible with 1.0.
There was a transition period where users could select between the 1.0 and 1.1 versions in the UI. During this period we found that the majority of users were choosing to tile their data with the newer 1.1 tiler.
If you do need the 1.0 format, you can still use the old 1.0 tiler via the API. If you are looking for the option in POST asset, you will need to select the 3D_CAPTURE option under sourceType to see the version option exposed.
