File Preparation

Populating the Design Explorer interface relies on 3 items. A structured CSV file, 2D images, and 3D Spectacles JSON files. The latter two are optional.

CSV File

The Comma Separated Value (CSV) file is what populates the interface with each design iteration within the design space. The top row of the CSV file should be used only for naming and tagging each type of data. The subsequent rows should each represent a single design iteration per row. The formatting of the file should follow these tags:

• Top Row: Tagged titles to specify what data gets displayed where in the interface. Using the following prefixes to distinguish the type of data each column contains.
  • Names: (For naming each design iteration) 'name:'
  • Inputs: 'in:'
  • Outputs: 'out:'
  • 2D Images: (a full url to each image) 'img'
  • 3D Images: (a full url to each Spectacles JSON file) 'threeD'

2D Images

The Design Explorer interface allows you to flip back and forth between 2D and 3D representations of each design iteration. The 2D images are used in the image grid to allow for sorting by input types and ratings.

• Images may be .jpg, .png, or .bmp file types
• The image size should be large enough to fill the canvas
• Images must be hosted somewhere online with an accessible URL.
  • Dropbox

3D Spectacles JSON

The 3D models for each design iteration are created and displayed using Spectacles which has exporters for Revit and Grasshopper for Rhino.