Importing geometry, three different instructions

I want to upload base geometry to be used in my grasshopper definition. I encountered three separate instructions on how to do this.

1)I was following the instructions for uploading as a giTF. and hosting on AWS. But the import geometry component says that this format is not supported and returns null.

  1. The second method involves uploading as an obj. I tried this but the mesh was invalid. Something about ASCII encoding (I am not at my computer).

  2. I heard you can get around the serving geometry by embedding the object inside the definition?

So which is it? Which technique should I use? It would be nice to avoid serving the geometry.

Solution 1) is optimal if the geometry you upload is a pure static asset that is not processed in the Grasshopper definition. Think of static scene features or modular parts (replacing an option with another one). If this is your case, then I would recommend trying to make the glTF export work. When using external gltTF, you can’t use the import geometry component, you just need to connect the URL to the ShapeDiverDisplayExternalGeometry component directly. You won’t see the asset in Grasshopper but it will be displayed correctly on ShapeDiver.

Now if you need to process the imported geometry in Grasshopper, you need to use either solution 2) or 3). In both cases, the full mesh will have to be imported in Grasshopper. Using solution 2), it can be done externally, even after the definition is uploaded (in case you want to still change the imported geometry in your application, or let your users upload their own). Otherwise, you can just import your object in Rhino and internalize the object in Grasshopper, as described in the last documentation article you are linking to. The gif in the article is pretty self-explanatory:

Does that help?