# Using the Space Analysis Package The package comes with a number of sample files provided to help you get started with each of the supported workflows. It is highly recommended to start with the samples as they contain detailed notes and instructions on how to use each of the nodes. ## Package Structure The space analysis package is organizes into 5 main categories in the Dynamo library. * **Core** : Core provides the framework for all space analysis workflows. This category contains the common [**SpaceLattice**](#Defining-a-Space-Lattice-with-Core-Nodes) object that is utilized in all space analysis workflows. * **Acoustics** : This category contains nodes that support approximate acoustic analysis workflows. * **Pathfinding** : Support for path finding workflows. This utilizes [Djikstra’s shortest path algorithm](https://en.wikipedia.org/wiki/Dijkstra%27s_algorithm). The pathfinding algorithms in this toolkit work on a grid (space lattice), with the size and resolution defined by the graph creator. * **Visibility** : Support for visibility analysis using a [view cone](/03-hello-gd-for-revit/03-06_space-analysis/03-06-02_using-space-analysis.md), or a [view point](#Single-Point-Analysis). * **Utils** : Miscellaneous utilities for use within the package. *** ## Defining a Space Lattice with Core Nodes The Space lattice object is the base object for space analysis workflows. It is essentially a 2d grid with diagonal connections. ### Inputs: * **boundingBox** - The Dynamo bounding box to generate a space lattice object for. * **barriers** - A list of lines that represent areas where there would be no lattice present * **resolution** - Space between two adjacent points of the lattice. ***(This uses your project units, so be sure to verify what those are prior to running)*** default value = 0.2 #### Simple Space Lattice with Barriers ![](/files/-MSEVY9TTNK2ek5cew1a) Sample File: [spaceAnalysis-CreateSimpleSpaceLattice.dyn](https://github.com/DynamoDS/RefineryPrimer/blob/master/assets/hello/spaceAnalysis-CreateSimpleSpaceLattice.dyn) Be sure to peek at the sample files in the extra folder for use-cases of the space lattice object. *** ## Acoustics Space analysis supports general acoustic analysis which are very useful for Generative Design applications. While these analyses are not *necessarily* validated. They can be very useful to use for constraints. *(These nodes can be used towards a design goal of "buzz factor")*. ### Additional Resources for Acoustics: * [Introducing Acoustics in Space Analysis](https://www.keanw.com/2019/06/say-what-acoustics-in-space-analysis.html) * [Multiple Source Acoustics](https://www.keanw.com/2019/09/build-your-own-soundsystem-space-analysis-now-supports-multi-source-acoustics.html) *** ## Path Finding 2D Path finding algorithms are included in space analysis. These are achieved using and implementation of [Djikstra’s shortest path algorithm](https://en.wikipedia.org/wiki/Dijkstra%27s_algorithm). A difference between space analysis path finding and the Path Finding in Autodesk Revit is, Space Analysis has no dependency on the Revit API - making it a perfect companion to Dynamo sandbox. ### Simple Two Point Path Finding Probably the simplest example of this would be to use a start point and end point with a barrier in-between. In the space analysis samples, this is demonstrated in: `spaceanalysis-pathfinding-01-one-path.dyn` ![](/files/-MSEVY9YZ0L3W9IKHlGT) ### Additional Resources for Pathfinding: * [Using Space Analysis for Pathfinding](https://www.keanw.com/2019/04/using-the-space-analysis-package-for-pathfinding-and-visibility-in-dynamo.html) * [A Nice Introduction to Dynamaps and Space Analysis by ThatBIMGirl](https://www.keanw.com/2019/06/a-nice-introduction-to-dynamaps-and-space-analysis-by-that-bim-girl.html) * [Comparing Space Analysis Path of Travel to Revit 2020's Version](https://www.keanw.com/2019/04/dynamo-space-analysis-and-revit-2020s-path-of-travel.html) *** ## Visibility Space Analysis offers a few different ways of analyzing visibility. While there are a few overlapping pieces between Space Analysis' visibility tools and [Refinery Toolkit's](https://github.com/DynamoDS/RefineryPrimer/blob/master/03-hello-GD-For-Revit/03-05_refinery-toolkit/03-05-02_using-the-refinery-toolkit.md), they can both compliment each other or simply give us other criteria to perform generative workflows on. ### Single Point Analysis Given a [**SpaceLattice**](#Defining-a-Space-Lattice-with-Core-Nodes) object, a view point and boundaries. We are able to define a view field and perform an analysis. ![](/files/-MSEVY9eQV_V-yXJh7-1) *Related Sample File: spaceanalysis-visibility-01-one-point-local-visibility.dyn* More information regarding single point analysis is available in the sample files within the tool kit. ## Multi-Point Analysis Given a [**SpaceLattice**](#Defining-a-Space-Lattice-with-Core-Nodes) object, multiple view points and boundaries. We are able to define a view field and perform an analysis. ![](/files/-MSEVY9lAd4zWPGdGOAn) *Related Sample File: spaceanalysis-visibility-03-two-points-union-vs-intersection.dyn* ## View Cone Analysis View cone analysis works similarly to Refinery Toolkit. With Space Analysis View Cone analysis your results will report "possible view range" within the analysis zone. While Refinery Toolkit will report if a given viewpoint is visible. ![](/files/-MSEVY9nIsZ9QdGm-jLg) *Related Sample File: spaceanalysis-visibility-04-one-point-view-cone.dyn* All samples for Space Analysis are available in the `extra` folder in the install directory. Typically this is, `C:\Users\USERNAME\AppData\Roaming\Dynamo\Dynamo Core\2.10\packages\SpaceAnalysis\extra` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.generativedesign.org/03-hello-gd-for-revit/03-06_space-analysis/03-06-02_using-space-analysis.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.