Beta.Speckle is an online parametric model viewer. It enables sharing with your clients/stakeholders/community flexible designs, not just static artefacts.
When exporting model metadata form grasshopper - the metadata is saved alongside the mesh data into the same JSON documents. This makes it hard to reuse metadata outside of SPK itself. Would be much better to export data in this structure:
Assuming mesh and meta files will have the same names to link it through param values it will be more modular and reusable structure.
Right now I've solved this problem by replicating this structure by hand and copying all mesh files to meta folder. This means I have to pull all mesh data alongside meta and then discard it, which is not ideal, but better than having no way to access meta directly at all.
When exporting model metadata form grasshopper - the metadata is saved alongside the mesh data into the same JSON documents. This makes it hard to reuse metadata outside of SPK itself. Would be much better to export data in this structure:
Assuming mesh and meta files will have the same names to link it through param values it will be more modular and reusable structure.
Right now I've solved this problem by replicating this structure by hand and copying all mesh files to meta folder. This means I have to pull all mesh data alongside meta and then discard it, which is not ideal, but better than having no way to access meta directly at all.