> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/holoplot-plan/importing-3d-assets-from-sketchup/defining-zone-types-in-sketchup.md). # Defining zone types in SketchUp ## Defining zone types in SketchUp This video show is an overview of the workflow for creating and defining zone types in SketchUp, and provides details on the following workflows: * Drawing and duplicating geometry in SketchUp * Making a face into a component * Applying the AudienceZone\_Material and BoundaryZone\_Material to separate components * Exporting the components as a .gltf file * Importing the .gltf file into Plan * Viewing audience zone, boundary zone and venue geometry types * Changing zone types in the Zones Panel * Creating a 1x1 Matrix Array with a Parametric Beam to view simulations * Viewing Audience Zone and Boundary Zone simulation results * Viewing the Boundary Zone casting shadows onto the Audience Zone when Acoustic Shadowing is enabled {% embed url="" %} Defining Zone Types in SketchUp {% endembed %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.holoplot.com/holoplot-plan/importing-3d-assets-from-sketchup/defining-zone-types-in-sketchup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.