> For the complete documentation index, see [llms.txt](https://docs.geosamples.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geosamples.org/metadata-schema/field-requirements.md).

# Field requirements

Fields SESAR requires to register a sample.

To **register** (publish) a sample, SESAR requires three things: **object type**, **sample name**, and **latitude and longitude**. Everything else is optional.

You can **save a draft** with only object type and name. Latitude and longitude are required when you publish a new sample. UTM or other coordinates do not replace them.

| Field                          | When it is required                   | Notes                                                                                                                                                         |
| ------------------------------ | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Object type**                | Always — drafts and published samples | Controlled list. The web form shows the full path; API writes use the leaf label.                                                                             |
| **Sample name**                | Always — drafts and published samples | The collector's name for the sample. In a batch spreadsheet, each name must be unique in that file.                                                           |
| **Latitude** and **longitude** | When you publish a new sample         | WGS84 decimal degrees. Provide both, or neither on a draft. Latitude must be between −90 and 90; longitude between −180 and 180. South and west are negative. |

End latitude and end longitude are optional. Use them together when the sampling location is a line (for example a dredge track). They are not a substitute for the required start coordinates.


---

# 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.geosamples.org/metadata-schema/field-requirements.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.