location.position
The newest fix any watch brought; null until the first. A signal: fixes
come about once a second, not once a frame, so nothing needs to follow
them on the UI thread.
Usage
Request a current position
import { Text, location, permissions } from 'kuito';
const { status } = await permissions.request('location');
if (status === 'granted') {
const here = await location.current({ accuracy: 'high' });
const [place] = await location.reverseGeocode(here.coords);
}
function Here() {
// Locates while Here is mounted; the fixes land in location.position.
location.watch({ distanceInterval: 20 });
return <Text>{`${location.position.value?.coords.latitude ?? '…'}`}</Text>;
}Properties and methods 1
| Name | Type | Required | Description |
|---|---|---|---|
valuereadonly | LocationObject | Yes | — |
value — nested fields
value fields
| Name | Type | Required | Description |
|---|---|---|---|
coords | LocationCoords | Yes | — |
timestamp | number | Yes | Milliseconds since the epoch, when the fix was taken. |
mocked | boolean | Yes | The fix came from the iOS simulator or an Android mock-location app. |
coords — nested fields
coords fields
| Name | Type | Required | Description |
|---|---|---|---|
latitude | number | Yes | — |
longitude | number | Yes | — |
altitude | number | Yes | Above sea level (iOS), or the WGS 84 ellipsoid (Android). |
accuracy | number | Yes | The radius of 68% confidence around the position. |
altitudeAccuracy | number | Yes | — |
heading | number | Yes | Degrees clockwise from true north that the device is moving. |
speed | number | Yes | Meters per second. |
Generated from the public TypeScript declarations: signatures, props and defaults come from the checked source, descriptions from its JSDoc. No defaults are invented.