> 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/workspace-and-data-management/creating-objects/well-design-data.md).

# Well Design Data

Well design data - casing, screens, backfill, and piezometer installation details for monitoring wells.

**Well design data** records the physical construction of a monitoring well: hole diameter, casing diameters and depths, filter and screen positions, backfill materials, and any special features such as piezometer boxes.

Well design data is entered through the **Data Management** method, on the **Well Design Data** tab. The schema depends on the object type - for example, AGS 4 supports a structured well design with HDIA, FLSH, BKFL, PIPE, and FILT groups; EN ISO 22475 uses E2WDCAS, E2WDFILD, E2WDBCKF and related tables.

Filters created in the well design table also generate measurement points of the type **Filter**, which is how groundwater measurement data attaches to the well - see [Working with Measurement Data](https://docs.geodin.com/workspace-and-data-management/working-with-measurement-data.md).

## Exporting well design data

Well design data leaves GeoDin as part of the object, not as a separate export. Two routes matter in practice:

* **XML export.** The **XML export** method (under **Publish and Export** at object nodes, queries and groups) writes one XML document per object using a configurable template, so the casing, screen and backfill tables are mapped into the target schema. It can be driven interactively or unattended from an export configuration `.INI` file - see [Object Operations Reference > XML export](https://docs.geodin.com/object-types/object-operations-reference.md#xml-export) for the method and the full `[PARAMS]` parameter reference.
* **Template definition.** Which well design tables and fields appear in the XML output, and under which element names, is decided in the XML export template - see [GeoDinML and XML export templates](https://docs.geodin.com/exporting-data/geodinml-export.md).

For the comprehensive object operations workflow - creating, editing, validating, importing, exporting, and reporting object data - see [**Object Operations Reference**](https://docs.geodin.com/object-types/object-operations-reference.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 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/workspace-and-data-management/creating-objects/well-design-data.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.
