> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/object-types/remediation-projects.md).

# Remediation Projects

Reference for the Remediation projects object type collection - five standalone object types for detailed data capture at remediation sites without layer or well-design data.

The **"Remediation projects"** object type collection was developed for the detailed capture of data at remediation sites.

<figure><img src="https://3138966068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOh9veY55xgALNVUW8siX%2Fuploads%2Fgit-blob-f8b3710ab15bc460ae0efa6a10c64704ec50399b%2Fimage.png?alt=media" alt="General data mask for the Wastewater object type, with map preview"><figcaption><p>General data mask for the object type "Wastewater" with map preview.</p></figcaption></figure>

## Checklist

* **Wastewater** - general data (with an additional mask for media files)
* **Container** - general data
* **Storage area** - general data (with an additional mask for media files), supplementary info (substances)
* **Production facility** - general data (with an additional mask for media files), supplementary info (connections, substances)
* **Remediation facility** - general data (with an additional mask for media files), sample data, well design/pipes, supplementary info (filters)

## Features

The "Remediation projects" collection comprises five independent object types: **Wastewater**, **Container**, **Storage area**, **Production facility**, and **Remediation facility**. Each object type has its own general data mask and can be used standalone in GeoDin, independently of the others.

<figure><img src="https://3138966068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOh9veY55xgALNVUW8siX%2Fuploads%2Fgit-blob-8ab35c930acb74ad1e9be949e3171306f8ada864%2Fimage%20(1).png?alt=media" alt="General data mask for the Production facility object type, Protection systems / Soil tab"><figcaption><p>General data mask for the object type "Production facility", tab "Protection systems / Soil".</p></figcaption></figure>

The object types **Wastewater**, **Storage area**, **Production facility**, and **Remediation facility** each have a "Media files" table, used to store file-system paths to related documents.

<figure><img src="https://3138966068-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOh9veY55xgALNVUW8siX%2Fuploads%2Fgit-blob-05626b50bd76df401b321ecefdd15cf8132fb715%2Fimage%20(2).png?alt=media" alt="Media files mask for the Wastewater object type"><figcaption><p>"Media files" mask for the object type "Wastewater".</p></figcaption></figure>

## Application

The object types in "Remediation projects" are used for data capture at remediation sites where no layer or well-design data has been determined or is required.


---

# 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.geodin.com/object-types/remediation-projects.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.