> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/layers/create-layers.md).
# Create layers
Create a point, line, or polygon layer with your own attributes, then draw its first feature on the map.
Create an empty point, line, or polygon layer to build and maintain your own dataset, such as assets to inspect or observations from the field. Once the layer exists, people with Contribute access can add features to it on the web or in the Field App.
## Create a layer
1. Click **Edit map** in the toolbar at the top right of the map.
2. Click **Add to map** (the pencil icon) in the toolbar, then click **Create layer**. If the button shows a tool you used earlier, click the arrow next to it to open the menu.
3. Enter a **Name** for the layer, select a **Type** (**Point**, **Line**, or **Polygon**), and click **Next**.
4. For each attribute you want to collect, click **Add attribute** and select a type, such as **Text**, **Number**, or **Image**. Name each attribute in the list on the left.
5. Click **Create layer**. The layer appears in the legend, ready for its first feature.
6. Click the map to place a point, or click to place each vertex of a line or polygon. The feature editor opens.
7. Optional: To add several features in a row, click **Add in bulk** (the stacked squares icon) at the top of the feature editor, or press **Option+A** (Mac) or **Alt+A** (Windows). In **Bulk settings** (the sliders icon next to it), select **Copy values to each new feature** or **Start each feature with blank values**.
8. In the feature editor, fill in the attribute values and click **Done**. In bulk add, click **Next** to save the feature and draw another, and click **Finish** when you're done.
Each layer has one geometry type. You choose it when you create the layer and can't change it later. To collect points and polygons, create a layer for each and put them in a [layer group](/layers/organize-layers.md#layer-groups).
To add more features later, see [Edit features](/layers/edit-features.md). To change the attributes, see [Add, rename, or delete attributes](/layers/edit-features.md#add-rename-or-delete-attributes). For dropdowns, required fields, and other form settings, see [Forms](/layers/forms.md).
## Layers and annotations
A layer holds features with the same attributes, geometry type, and style, and supports filtering, analysis, the table, and field data capture. An annotation is a shape, pin, or note for marking up the map. See [Draw on the map](/annotations/draw-on-the-map.md).
To turn annotations into a layer, select them, right-click, and click **Actions** > **Convert to layer**. To bring in data you already have, upload it instead. See [Upload files](/upload-anything/files.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://help.felt.com/layers/create-layers.md?ask=&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.
