> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-7.5/voyage-management-system/step-by-step-guides/vessels/vessel-speed-and-consumption-data/manage-air-emissions.md).

# Manage Air Emissions

{% hint style="warning" %}
The data added in this table is currently not used for any calculations in the system related to emissions, and is only meant to be used for external processing.
{% endhint %}

The Air Emissions table shows you an overview over vessel air emissions, specifying bunker- and emission-type, emission factor and from which date the emission is valid from.

<div><figure><img src="https://content.gitbook.com/content/gCulNWvhbyXwomHtQeEl/blobs/gKIEQZYjHfs0Pfdbs9H8/Skjermbilde%202023-12-06%20kl.%2010.04.58.png" alt=""><figcaption><p>The list shows all air emissions linked to the vessel.</p></figcaption></figure> <figure><img src="https://content.gitbook.com/content/gCulNWvhbyXwomHtQeEl/blobs/drbyW3U7mGaNE6pOs88e/Skjermbilde%202023-12-06%20kl.%2010.11.27.png" alt=""><figcaption><p>The Edit Air Emission modal allows you to edit or delete the emission.</p></figcaption></figure></div>

To add a new air emission, click the ![](https://content.gitbook.com/content/gCulNWvhbyXwomHtQeEl/blobs/NcmqUa0AvZ7T77jnBrRo/image.png) icon, fill in the required fields, and click Create. Editing an existing air emission is done by clicking on it in the list to bring up the edit modal. To delete an air emission, click on it in the list and then click Delete.


---

# 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.dataloy.com/release-7.5/voyage-management-system/step-by-step-guides/vessels/vessel-speed-and-consumption-data/manage-air-emissions.md?ask=<question>&goal=<user_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.