> For the complete documentation index, see [llms.txt](https://pimkb.gitbook.io/pimkb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pimkb.gitbook.io/pimkb/preserving-360-video/spatial-metadata.md).

# Spatial Metadata

Due to the additional properties of 360-degree video in comparison to fixed-perspective video, there is a need for metadata standards to accommodate this. These are an important component of documentation for 360-degree video files as they support correct identification and decoding by playback tools. Google has released a suite of standards and metadata injection tools on GitHub under the name [Spatial Media](https://github.com/google/spatial-media).

In order to have 360-degree video recognised (e.g. when using a video player, or uploading to YouTube) and played back properly, spatial metadata must be included in the file-level metadata. [Spatial Media Metadata Injector](https://github.com/google/spatial-media/releases/tag/v2.1) is open source software, developed by Google, that can be used to inject spatial metadata into 360-degree video files. This supports MOV, MP4 and MKV/WebM (video only) containers. 

It supports adding metadata describing:

* Projection type
* Stereoscopic mode
* Projection pose (yaw, pitch, roll) - presumably for initiation position? 
* Spatial audio including ambisonic channel order and mapping

You can find full specification information on GitHub for the supported elements describing [video](https://github.com/google/spatial-media/blob/master/docs/spherical-video-v2-rfc.md) and [audio](https://github.com/google/spatial-media/blob/master/docs/spatial-audio-rfc.md). 


---

# 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://pimkb.gitbook.io/pimkb/preserving-360-video/spatial-metadata.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.