> For the complete documentation index, see [llms.txt](https://docs.dryad.app/dryad-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dryad.app/dryad-documentation/site-planning/coverage-estimation/sensor-changes.md).
# Add or move Sensors
Add, delete or change locations of Wildfire Sensors.
After a path or area has been drawn, a sensor may have been placed in a location free of trees or perhaps in a location where a sensor cannot be deployed, such as on a building.
## Add Sensors
Wildfire Sensors can be added to areas or paths.
{% hint style="danger" %}
Any customization of an area or path overwrites the default placement of sensors.
{% endhint %}
Add Sensor
1. Select an Area or a Path.
2. From the **Edit Path** panel, select the **Manually Planning** tab.
3. Select **Add Sensor**.
4. Drag the Sensor to the required location, then click to place the Sensor icon.
{% hint style="warning" %}
A red icon indicates the sensor is outside the zone of the selected path or area.
{% endhint %}
5. Save the project.
## Move Sensors
The name and location of a Sensor can be changed.
Edit Sensor
### Change Sensor name
1. In an area or path, select a Wildfire Sensor.
2. In the **Edit Sensor** dialog, enter a descriptive name in the **Name** field.
3. Save the project.
### Move Sensor location
1. In an area or path, select a Wildfire Sensor.
2. Using the mouse, move a Sensor to update the latitude and longitude settings of the sensor. This may be required if a Sensor is placed outside a Connectivity zone.
3. Save the project.
## Delete Sensors
1. In an area or path, select a Wildfire Sensor.
2. In the **Edit Sensor** dialog, select **Delete Sensor**. This cannot be undone.
3. Save the project.
---
# 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.dryad.app/dryad-documentation/site-planning/coverage-estimation/sensor-changes.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.
