Closed aussig closed 4 years ago
Work is well underway on a loader for three.js in a fork of the project
We need to build and deploy all models and textures to the website to support this. Most efficient way would be to deploy directly to the AWS S3 bucket rather than the servers and reference via the downloads domain.
I think we should have a separate folder structure for this, with a full copy of the uncompressed repository. Or… We could implement browser-side unzipping as part of our three.js implementation and simply point it at the repository.
Although facades are not implemented yet, closing this as all the infrastructure and deployment is done, and objects, forests, lines and polygons are all working well.
In addition to static screenshots, it would be good to be able to preview the models in 3d.
three.js looks powerful. We would need to either convert the model into a supported format such as glTF or Wavefront OBJ or write a three.js loader for our 3d formats.
ModelConvertorX (Windows only) or i3DConverter (Win / Mac / Linux) might help with the conversion approach.