> For the complete documentation index, see [llms.txt](https://docs.pollination.solutions/user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pollination.solutions/user-manual/rhino-plugin/interoperability/rhino-import.md).

# Import

Pollination Rhino allows for the import/export of geometry and properties in the gbXML, OSM, IDF, hbjson file format.

There are two modes to open the file formats above.

* Open: Creates a new Pollination Rhino Model using the generic template
* Import: It add the model to the current Pollination Rhino model

## Import:

* [Import Honeybee JSON (HBJSON)](/user-manual/rhino-plugin/interoperability/rhino-import/hbjson.md)
* [Import Green Building XML (gbXML)](/user-manual/rhino-plugin/interoperability/rhino-import/gbxml.md)
* [Import OpenStudio Model (OSM)](/user-manual/rhino-plugin/interoperability/rhino-import/osm.md)
* [Import Input Data File (IDF)](/user-manual/rhino-plugin/interoperability/rhino-import/idf.md)

There is no loss of information when importing HBJSON but only certain model elements\
can be imported from OSM, gbXML and IDF. These are summarized below.

| Model Element                  | HBJSON | OSM            | gbXML            | IDF              |
| ------------------------------ | ------ | -------------- | ---------------- | ---------------- |
| Geometry                       | ☑      | ☑ <sup>1</sup> | ☑ <sup>1</sup>   | ☑ <sup>1 2</sup> |
| Spaces / Zoning                | ☑      | ☑              | ☑                | ☑                |
| Boundary Conditions            | ☑      | ☑              | ☑                | ☑                |
| Face Types (eg. AirBoundary)   | ☑      | ☑              | ☑                | ☑                |
| Opaque Constructions           | ☑      | ☑              | ☑                | ☑                |
| Window Constructions           | ☑      | ☑ <sup>3</sup> | ☑ <sup>3</sup>   | ☑ <sup>3</sup>   |
| Schedules                      | ☑      | ☑              | :x: <sup>5</sup> | ☑                |
| Loads                          | ☑      | ☑              | :x: <sup>5</sup> | ☑                |
| Thermostats + Outdoor Air Req. | ☑      | ☑ <sup>4</sup> | :x: <sup>5</sup> | ☑                |
| Program Types                  | ☑      | ☑              | :x:              | :x:              |
| HVAC Systems                   | ☑      | :x:            | :x:              | :x:              |
| SHW Systems                    | ☑      | :x:            | :x:              | :x:              |
| Natural Ventilation            | ☑      | :x:            | :x:              | :x:              |
| Everything Else                | ☑      | :x:            | :x:              | :x:              |

<sup>1</sup> Formats do not natively support geometries with holes (they are collapsed to a single list of inward-turning vertices on export).\ <sup>2</sup> IDF only supports Apertures/Doors with 3-4 vertices (more complex window geometries are usually triangulated).\ <sup>3</sup> No dynamic behavior of window constructions is imported.\ <sup>4</sup> These always become divorced from ProgramTypes since they are not a part of OpenStudio SpaceTypes.\ <sup>5</sup> These may eventually be supported depending upon [this issue](https://github.com/NREL/OpenStudio/issues/4320).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pollination.solutions/user-manual/rhino-plugin/interoperability/rhino-import.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.