> For the complete documentation index, see [llms.txt](https://carare.gitbook.io/share-3d-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carare.gitbook.io/share-3d-guidelines/3d-process/creating-complementary-2d-media.md). # Complementary Media A range of complementary digital media is often produced as a result of 3D projects. Such media includes: ### Static Images * 2D images of the heritage asset * 3D renderings of visually enriched models from several perspectives * Elevations, plans and sections of the point cloud data * Images highlighting specific features of the cultural object ### Animation * Turn table videos * Flythrough animations and video tours * Structural animations showing the workings of different components of an artefact or a monument, e.g. animation showing a working water mill * Temporal animations highlighting changes in a structure through time, e.g. animation showing a monument in its present day ruined state back to reconstructions of the monument at different points in time. ### Interactive Images * Panoramas * VR Objects ![Complementary 2D media derived from the 3D model. Abbey of Saint-Michel de Cuxa (CNRS-MAP).](/files/-LjMC3v1XIuNPaq3_qnW) --- # 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://carare.gitbook.io/share-3d-guidelines/3d-process/creating-complementary-2d-media.md?ask=&goal= ``` `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.