-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EN] Mesh post-processing - Optimization for web delivery via 3D Tiles #27
Comments
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment to re-open. |
Feature request / Suggestion
We are using
meshoptimizer
along with several mesh simplification steps to make meshes smaller for web delivery. Adding support for the 3D Tiles format will be a big step forward. This will require two main things:.obj
or.glTF
file.<model-viewer>
with a viewer that supports those formats.Later, we can also look into integrating with map layers, such as with OpenStreeMap.
Other details
Some resources:
Also look into https://github.com/Geopipe/gltf2glb as a potential workaround for the node bug in
obj2gltf
.Self-check
The text was updated successfully, but these errors were encountered: