> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-properties/lct-details-page/location-type.md).

# Location Type

Static or Dynamic Location

The LCT device supports two location types: **Dynamic** and **Static**.

* **Dynamic Location**: Enables tracking the device's position history over a selected timeframe, ideal for mobile applications like containers or vehicles.
* **Static Location**: Displays only the device's last known location, suitable for devices mounted on stationary objects.

The choice between dynamic and static depends on the device's role—dynamic for moving assets and static for fixed installations—ensuring the location settings align with operational needs.

<figure><img src="https://122097802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfEQ6KpTjmszWVWQqgcEa%2Fuploads%2FewcEIqZxnOosj8XBxnvZ%2Fimage.png?alt=media&amp;token=8095ec86-e1e6-4e67-9478-c79595e7b022" alt=""><figcaption><p>Static or Dynamic</p></figcaption></figure>

1. **Navigate to the Device:**
   * Go to the **Device** section and select the LCT device.
2. **Open Properties:**
   * Click on **Properties**.
3. **Access Details:**
   * In the Properties menu, click on **Details**.
4. **Locate Location Type:**
   * Scroll down to find the **Location Typer** field.
5. **Set Type:**
   * Select the Dynamic or Static from the dropdown list.
6. **Save Changes.**

{% hint style="info" %}
When the location is set to **Static**, ensure that the location is accurately marked on the **Map** in the device's **Properties** page.
{% endhint %}


---

# 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.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-properties/lct-details-page/location-type.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.