mirror of
https://github.com/meshtastic/meshtastic.git
synced 2024-12-24 21:24:44 -08:00
Update position precision levels (#1482)
* Update position precision levels * Update usage.mdx removed precision bits, transformed to 2-column table instead * Create _position-precision-bits.mdx * Create _position-precision.mdx * Update usage.mdx * Insert link to blocks/_position-precision-bits.mdx * Update channels.mdx * Update usage.mdx * Update channels.mdx * Update channels.mdx * Update usage.mdx * Update _position-precision.mdx * Update _position-precision-bits.mdx * Update _position-precision-bits.mdx * Update _position-precision-bits.mdx * Update _position-precision.mdx * Update _position-precision.mdx * Update _position-precision-bits.mdx * Update channels.mdx * Update usage.mdx
This commit is contained in:
parent
59b833f79d
commit
38f59b2e3e
12
docs/blocks/_position-precision-bits.mdx
Normal file
12
docs/blocks/_position-precision-bits.mdx
Normal file
|
@ -0,0 +1,12 @@
|
|||
| Precision bits | Metric | Imperial |
|
||||
| :------------: | :-----: | :--------: |
|
||||
| 10 | 23.3 km | 14.5 miles |
|
||||
| 11 | 11.7 km | 7.3 miles |
|
||||
| 12 | 5.8 km | 3.6 miles |
|
||||
| 13 | 2.9 km | 1.8 miles |
|
||||
| 14 | 1.5 km | 4787 feet |
|
||||
| 15 | 729 m | 2392 feet |
|
||||
| 16 | 364 m | 1194 feet |
|
||||
| 17 | 182 m | 597 feet |
|
||||
| 18 | 91 m | 299 feet |
|
||||
| 19 | 45 m | 148 feet |
|
12
docs/blocks/_position-precision.mdx
Normal file
12
docs/blocks/_position-precision.mdx
Normal file
|
@ -0,0 +1,12 @@
|
|||
| Metric | Imperial |
|
||||
| :-----: | :--------: |
|
||||
| 23.3 km | 14.5 miles |
|
||||
| 11.7 km | 7.3 miles |
|
||||
| 5.8 km | 3.6 miles |
|
||||
| 2.9 km | 1.8 miles |
|
||||
| 1.5 km | 4787 feet |
|
||||
| 729 m | 2392 feet |
|
||||
| 364 m | 1194 feet |
|
||||
| 182 m | 597 feet |
|
||||
| 91 m | 299 feet |
|
||||
| 45 m | 148 feet |
|
|
@ -7,6 +7,7 @@ description: Understand how to configure channels on your Meshtastic device, inc
|
|||
|
||||
import Tabs from "@theme/Tabs";
|
||||
import TabItem from "@theme/TabItem";
|
||||
import PositionPrecisionBits from "@site/docs/blocks/_position-precision-bits.mdx";
|
||||
|
||||
The Channels config options are: Index, Roles, and Settings. Channel config uses an admin message sending a `Channel` protobuf which also consists of a `ChannelSettings` or `ModuleSettings` protobuf.
|
||||
|
||||
|
@ -117,13 +118,9 @@ The `position_precision` value is an integer between 0 and 32:
|
|||
|
||||
- A value of 0 means that location data is never sent over the given channel.
|
||||
- A value of 32 means that location data is sent with full precision.
|
||||
- Values in between indicate the number of bits of precision to be sent.
|
||||
- Values in between indicate the number of bits of precision to be sent, which correspond to a position precision from the table below.
|
||||
|
||||
Some useful values and their approximate precisions:
|
||||
|
||||
- 11: Large region, around ±11 kilometers
|
||||
- 13: City-sized region, around ±3 kilometers
|
||||
- 16: Neighborhood-level precision, around ±350 meters
|
||||
<PositionPrecisionBits />
|
||||
|
||||
The client applications have implemented different levels of precision giving the user a practical range to choose from. Setting across the full range of integers can be done via the Python CLI. See [Setting Position Precision](/docs/configuration/radio/channels/#setting-position-precision) for examples on setting different levels of precision using CLI.
|
||||
|
||||
|
@ -158,13 +155,14 @@ See [Android App Usage](/docs/software/android/usage#setup-a-channel) for more f
|
|||
|
||||
[![Channel Editor](/img/android/android-channel-edit-sm.webp)](/img/android/android-channel-edit.webp)
|
||||
|
||||
Tap the Channel Name (or the pen icon) to access the Channel Menu:
|
||||
Tap "Edit" to access the Channel Menu:
|
||||
|
||||
1. Add, remove, or modify secondary channels
|
||||
2. Create or modify encryption keys
|
||||
3. Enable uplink and downlink for individual channels
|
||||
4. Set the position precision value
|
||||
|
||||
4. Position enabled
|
||||
5. Precise location (if position is enabled)
|
||||
6. Position precision (if precise location is disabled)
|
||||
|
||||
|
||||
</TabItem>
|
||||
|
|
|
@ -4,10 +4,13 @@ title: Android Application Usage
|
|||
sidebar_label: Usage
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
import PositionPrecision from "@site/docs/blocks/_position-precision.mdx";
|
||||
import Link from "@docusaurus/Link"
|
||||
import ThemedImage from '@theme/ThemedImage';
|
||||
import useBaseUrl from '@docusaurus/useBaseUrl';
|
||||
|
||||
|
||||
## Introduction
|
||||
|
||||
The Meshtastic Android app handles the communication and can show the location of everyone in your private group. Each member of your private mesh can see the location and distance of members and text messages sent to your group chat.
|
||||
|
@ -133,14 +136,14 @@ You can test changing channels with the QR code shown below.
|
|||
You can change the following settings by tapping on the name of an existing channel:
|
||||
1. MQTT Uplink
|
||||
2. MQTT Downlink
|
||||
3. Position precision value
|
||||
3. Position enabled
|
||||
4. Precise location (if position is enabled)
|
||||
5. Position precision (if precise location is disabled)
|
||||
|
||||
#### Position Precision
|
||||
The precision levels currently used in the app correspond to the following values:
|
||||
- HIGH_PRECISION (32), full precision
|
||||
- MED_PRECISION (16), around ±350 meters
|
||||
- LOW_PRECISION (11), around ±11 kilometers
|
||||
- DISABLED (0), location data is never sent over the given channel
|
||||
The precision levels currently used in the app correspond the values in the table below. These can be thought of as the radius of a circle around a point (not your current location) which you are within.
|
||||
|
||||
<PositionPrecision />
|
||||
|
||||
### Send a message
|
||||
|
||||
|
|
Loading…
Reference in a new issue