> 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/geodin-desktop/es/area-de-trabajo-y-gestionar-datos/creating-objects/well-design-data.md).

# Datos del diseño

Datos del diseño - Detalles de entubación, pantallas, Relleno e Instalación de piezómetros para pozos de monitoreo.

**Datos del diseño** Registros de la construcción física de un pozo de monitoreo: Diámetro del agujero, Diámetros y profundidades de la entubación, posiciones de Filtro y Pantalla, materiales de Relleno y Montajes especiales, como cajas piezométricas.

Los Datos del diseño se introducen a través del **Gestionar datos** Método, en el **Datos del diseño** pestaña. El esquema depende del Tipo de objeto - por ejemplo, AGS 4 admite un Proyecto de ampliación estructurado con grupos HDIA, FLSH, BKFL, PIPE y FILT; EN ISO 22475 utiliza E2WDCAS, E2WDFILD, E2WDBCKF y tablas relacionadas.

Para el flujo de trabajo integral de Operaciones de ejecución de Perforación — creación, edición, validación, importación, exportación y generación de informes de Datos del objeto — consulte [**Referencia de Operaciones de ejecución de Perforación**](/geodin-desktop/es/tipos-de-objetos/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/geodin-desktop/es/area-de-trabajo-y-gestionar-datos/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.