# Location

**Category:** Field

**Version:** 1.0

**Last Updated:** April 15, 2026

**Author:** Any2Info

***

### Description

The **Location field** is a form field used to capture and store a geographical location.

In addition to storing the current location, the field also supports displaying a **target location**, enabling comparison or guidance scenarios within a form.

This field is specifically designed for use within forms and works with data of type **Location**.

### Configuration Options

| Setting | Required | Description                                                                                                            |
| ------- | -------- | ---------------------------------------------------------------------------------------------------------------------- |
| Target  | No       | Maps to a header of type **Location**. Defines a target location that can be displayed alongside the current location. |

***

### Data Format

The Location field uses the following format: latitude;longitude;precision;altitude;altitudePrecision

* **latitude** (required) → Latitude coordinate
* **longitude** (required) → Longitude coordinate
* **precision** (optional) → Accuracy of the location
* **altitude** (optional) → Height above sea level
* **altitudePrecision** (optional) → Accuracy of the altitude

At minimum, **latitude and longitude must be provided**. Additional values are optional.

This format must match the standard used across dataclips. :contentReference\[oaicite:0]{index=0}

***

### Usage

Use the **Location field** in forms where geographical input or reference is required.

Typical use cases include:

* Capturing a user's current location
* Comparing a current location to a predefined target
* Supporting navigation or location-based workflows

***

### Events

| Event            | Description                                               |
| ---------------- | --------------------------------------------------------- |
| On Value Changed | Triggered whenever the current location value is updated. |

***

### Mappings

| Mapping | Description                                                                 |
| ------- | --------------------------------------------------------------------------- |
| Target  | Links the field to a **Location-type header** to display a target location. |

***

### Tips & Best Practices

* Always ensure the mapped **Target** header is of type **Location**.
* Provide at least latitude and longitude to avoid invalid data.
* Use the target mapping when guiding users toward a specific location.

***

### Changelog

| Version | Date           | Change                               |
| ------- | -------------- | ------------------------------------ |
| 1.0     | April 15, 2026 | Initial documentation version added. |


---

# Agent Instructions: 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:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/forms/fields-toolbox/basics/location.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.