> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/guides/how-to-set-up-and-use-location-on-non-gps-devices.md).

# How to set up and use location on non-GPS devices

How to use and manually set location data on stationary devices that do not send location data collected via GPS or another tracking system.

## Steps

If your Datacake product (and its devices) does not yet have a field of type "Geolocation", then the first thing you need to do is to create an appropriate field.

* To do this, navigate to the Configuration View of your device and scroll to the list of database fields.
* There you create a new field, select the type "Geolocation" and set the field role "Device Location".
* After creation, the Location field will appear in the list of fields. You can now manually set the location of the device and from now on the location will also be displayed on map widgets or in the map view of the platform.

## Video

The following video will show the required steps.

{% embed url="<https://youtu.be/8sJa_Kwrh1g>" %}


---

# 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.datacake.de/guides/how-to-set-up-and-use-location-on-non-gps-devices.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.
