> 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-properties/location-type.md).

# Location Type

The **Location Type** feature determines how GIoT calculates and reports a device's position. In addition to the standard **Dynamic** mode, devices can be configured to use **Anchor** mode, which keeps the reported location fixed while the asset remains in the same physical place. This reduces location drift caused by Wi-Fi and cellular positioning while minimizing GPS usage and preserving battery life.&#x20;

<figure><img src="/files/I5M0vyyfW6IaN1VlVapg" alt=""><figcaption></figcaption></figure>

The current location type and anchor status can be viewed directly from the **Device Properties** Top-bar. ![](/files/dpRAmGdY36wrQWqMzplv)

### Dynamic Location

**Dynamic** is the default location mode. In this mode, every position update is calculated independently using the best available positioning technology (GPS, Wi-Fi, or cellular). This mode is recommended for assets that move frequently and require continuous location updates.

***

### Anchor Location

**Anchor** mode is designed for devices that remain in the same location for extended periods. Instead of calculating a new position for every transmission, GIoT anchors the device to a single location, preventing small variations caused by Wi-Fi or cellular positioning. GPS is only requested when required, reducing battery consumption while providing a stable location.

#### Status: Awaiting GPS Fix

After **Anchor** mode is enabled, the device enters the **Awaiting GPS Fix** state.

During the next device transmission, GIoT requests a GPS position and temporarily enables a fast reporting interval so the GPS fix can be obtained without waiting for the normal transmission cycle. Until the GPS location is received, the device continues reporting normally.

> ![](/files/5tjQkWLI463XppEKoqUe)

#### Status: Anchored

When a valid GPS position is successfully obtained, the device enters the **Anchored**state.

The GPS coordinates become the anchor location and are reported for subsequent transmissions while the device remains in the same place. GIoT verifies that the device has not moved by comparing Wi-Fi information between transmissions. If at least one Wi-Fi access point matches the previous transmission, the anchor location is maintained.

> ![](/files/NXIFzvmrQ58zIaCQAT7o)

#### Status: Fixed (No GPS)

If a GPS position cannot be obtained—for example, when the device is indoors—but Wi-Fi or cellular positioning is available, the device enters the **Fixed (No GPS)** state.

In this case, GIoT anchors the device using the available Wi-Fi or cellular location instead of GPS, allowing the anchor functionality to continue even when GPS reception is unavailable.

> ![](/files/hbW9f94TFQ1JHymO7GzW)

#### Status: Moving

Indicates that the device is currently in motion. The status is triggered by a **`motion_start`** event and remains active until the device reports a **`motion_stop`** event.

> ![](/files/Btdj1EXbfbcCKiaz6ONb)

***

### Releasing the Anchor

The anchor location remains active until GIoT detects that the device has moved.

Movement is detected when:

* A motion event indicates that the device has started moving.
* No matching Wi-Fi access points are detected and the reported position exceeds the configured movement threshold (currently **1,000 m**).

When either condition occurs, the device returns to the **Awaiting GPS Fix** state and requests a new GPS position to establish a new anchor location.

> ![](/files/ERaCKmDiJq3KHSMvACp9)

#### Why Use Anchor Mode?

Anchor mode is recommended for devices that remain stationary for long periods, such as assets stored in warehouses, production facilities, or customer sites.

**Benefits include:**

* Eliminates location drift caused by Wi-Fi and cellular positioning.
* Provides a stable reported location while the asset remains stationary.
* Reduces GPS usage and extends battery life.
* Automatically creates a new anchor location when the device is moved.

This structure is documentation-oriented and gives you a dedicated place to insert a screenshot for every state and transition.

### Static Location

The **Static** location type is intended for devices installed in a fixed position. Unlike **Dynamic**, where the device location is determined automatically by geolocation algorithms, **Static** uses a location defined manually by the user.

Select **Static** when the device position should remain fixed. The location can be configured from the **Location** tab and will remain unchanged until it is manually updated.<br>

{% hint style="info" %}
After configuring the desired location, click **Update Configuration** to save the changes and apply the new static location to the device.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-properties/location-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
