> 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/pt/espaco-de-trabalho-e-gestao-de-dados/creating-objects/sample-data.md).

# Dados de amostra

Dados de amostra - registo de amostras físicas recolhidas de objeto com intervalos de Profundidade e Detalhes identificativos.

**Dados de amostra** regista as amostras físicas retiradas de um objeto (Furo OU Localização), incluindo o Intervalo da profundidade de cada amostra, o identificador, o Típo e a associação com testes de Laboratório subsequentes.

Os Dados de amostra são inseridos através do **Gestão de dados** Método, No **Dados de amostra** separador. Cada amostra é ancorada a um Intervalo da profundidade e pode ser ligada aos Resultados dos testes de Laboratório através de Pontos de medição (e.g. AGS `(AGS) Amostras [AGS]`).

Para o fluxo de trabalho abrangente de operações de objeto - criar, editar, validar, importar, exportar e elaborar relatórios sobre os dados do objeto - consulte [**Referência de Operações de objeto**](/geodin-desktop/pt/tipos-de-objeto/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/pt/espaco-de-trabalho-e-gestao-de-dados/creating-objects/sample-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.