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
We should consider adding a section to the 3D Tiles spec about recommended glTF extensions. This would be like best practices guide for taking the most advantage out of glTF within the 3D Tiles / geospatial domain.
This would be like best practices guide for ... glTF within the 3D Tiles / geospatial domain.
Another good example for inspiration would be the 3D Commerce Real-time Asset Creation Guidelines. Basically, best practices for glTF within the online retail/commerce domain. Many of those same recommendations could apply here, too.
The MIGRATION.adoc covers some of these extensions. I wonder whether this should be made more explicit, and/or whether the list of "recommended extensions" should be featured more prominently somewhere in a GitHub MD/ADOC file...?
EDIT: It can not become part of the (now released) specification itself. The point is whether this issue could be closed, or should kept open as a reminder that such a section indeed should be added.
We should consider adding a section to the 3D Tiles spec about recommended glTF extensions. This would be like best practices guide for taking the most advantage out of glTF within the 3D Tiles / geospatial domain.
Inspired by the Khronos 3D formats guidelines: https://github.com/KhronosGroup/3D-Formats-Guidelines
e.g.
The text was updated successfully, but these errors were encountered: