Indoor and outdoor

Omaya can follow something in two ways. Indoors, BLE gateways on the ceiling hear a tag and Omaya works out which room it is in. Outdoors, a tracker with its own GPS reports where it is, and Omaya turns those positions into places, trips and stops. Both write to the same trail, so a person's day reads as one story: the office, the car park, a drive across town, a stop at a client, and back to the lobby.

Indoors and outdoors write the same trail. While a BLE gateway is hearing the tracker, indoor positioning owns it and names a room. Outside, a GPS fix inside a geofence names that place; anywhere else the time is a trip while it moves and a stop once it stays put. The short dashed window is the handover: for a couple of minutes after the gateways last heard it, GPS fixes are kept on the map but not put on the trail, so a fix taken by a window does not pull someone outside.

This page explains how the two fit together, how to name outdoor places with geofences, and what each outdoor setting does. For the indoor half in depth — floor plans, gateways, the calibration walk — see Floor plans and positioning.

Two ways of knowing where something is

	Indoors	Outdoors
What does the work	Gateways hear the tag and report how loud it was	The tracker works out its own position by GPS and reports it
What you need	A floor plan with its scale, zones drawn, gateways placed	A tracker that reports latitude and longitude; geofences for the places you want named
What it names	A room (a zone on the floor plan)	A geofence, a trip or a stop
How exact	The room, when the floor is set up well	About 5–20 m under open sky; worse between tall buildings, nothing under a roof
How often	Every sweep, about every 30 seconds	Every time the tracker reports — usually every few minutes
Where it is tuned	System → Configuration → Indoor Positioning	System → Configuration → Outdoor & GPS

A tag with no GPS simply goes quiet when it leaves the building, as it always has. A tracker with both — one that broadcasts BLE and has GPS — gets both: a room while the gateways can hear it, and places, trips and stops outside.

Which trackers work outdoors

Any tracker whose reports reach Omaya with a latitude and longitude:

• LoRaWAN trackers, through your LoRaWAN network server, the same way as a LoRaWAN sensor. See Milesight LoRaWAN gateways and MQTT gateways.

• Trackers that publish over MQTT: a gateway following the MQTT gateway contract with latitude and longitude (and, if given, accuracy in metres) in a device's entry, or a cellular tracker that reports itself, such as MOKO's PS101-M.

• Positions from another platform: a fleet or telematics system that already knows where its trackers are can send plain positions (tracker ID, latitude, longitude, time) over MQTT or an HTTP connector. See GPS positions from another platform.

• Phones running Omaya Scout, for a Bluetooth tag that has no GPS of its own. See Phones as trackers: Omaya Scout below.

The tracker is registered like any other device, by its MAC, its LoRaWAN EUI, or for a cellular tracker its tracker ID (the IMEI or serial number). Coordinates written with their unit, as some manufacturers' decoders do (3.1390123°), are read correctly. A report of 0, 0 is what trackers send when they have no fix yet, and is ignored.

Trackers that scan

Some trackers locate themselves indoors by scanning nearby beacons or Wi-Fi access points and sending the list of what they heard, rather than a position — MOKO's PS101-M set to a Bluetooth or Wi-Fi fix, for example. Omaya places such a tracker in a room from the beacons and access points you have registered as anchors, and the room then takes over from GPS exactly as a gateway sighting does. See Beacon and Wi-Fi anchors. Without anchors the list is kept on the device's latest reading but places it nowhere.

Phones as trackers: Omaya Scout

An ordinary Bluetooth tag goes quiet the moment it leaves gateway coverage. Omaya Scout is a phone app that fills that gap: a phone running it listens for your tags wherever it is, and when it hears one it sends the phone's own GPS position with it. Omaya then knows the tag was close to that phone, at that place and time. Its main use is people: each person who carries a tag installs Scout on their own phone, and their tag keeps working outdoors, between sites and on the road, with no gateway nearby. It works for things too, when someone's phone travels with them: a tool kit in a van, a trolley taken across a campus. The app itself is described in Omaya Scout.

What a Scout report does:

• It counts as a GPS position for the tag. It goes on the map, the trail, Outdoor Activity and GPS Replay, and names your geofences, exactly as a tracker's own GPS would. Indoors still wins: while a gateway hears the tag, the gateway's room is the answer.
• One position per moment, however many phones. When several phones hear the same tag, Omaya keeps the most accurate report and counts the phones.
• Its accuracy is the phone's, plus the distance to the tag. The tag can be anywhere from about 1 to 60 m from the phone, judged from its signal, so a Scout position is a little looser than a tracker's own fix.
• It refreshes the tag's battery and readings, and its last-seen time, but never places it in a room and never changes which gateway is said to hear it.
• What it relays does not set off rules. Phones are not gateways you installed, so a reading or a button press relayed by a phone is recorded but fires no rule, button-press alert or panic page. The position itself crosses geofences like any GPS position, so geofence rules see it.
• It follows your data retention, like every other GPS position.

Which tags phones look for. Your organisation's registered tags, beacons and trackers, once Scout has been switched on for your organisation by whoever operates your platform. Tags people carry — bound to a Person on the Entity page — are included too where your operator has turned that on, which is what lets each person's own phone keep their tag working outdoors, with no gateway nearby. Install Omaya Scout on the phone of everyone who carries a tag.

How a phone knows which tag it heard. A phone passes on every Minew, MOKO, Eddystone and iBeacon advertisement it hears, the way a gateway does, and Omaya decides which are your tags; the rest are dropped unread. An Android phone sees each tag's Bluetooth address. An iPhone does not, so Omaya recognises the tag by what it broadcasts instead — its iBeacon or Eddystone ID, or a MOKO tag's device ID — which it learns from your gateways. So:

• On iPhones, a tag is found once a gateway has heard it. A tag that has only ever been outside is found by Android phones until it comes past a gateway once.
• Give each tag its own ID. Two tags left on the same factory ID (a common default on MOKO buttons) cannot be told apart, and an iPhone reports neither. Set a distinct ID in the maker's app, or on the tag's Configure page where its model offers the setting.

See who is covered outdoors

1. Open Monitor → Scout (phones).

2. Read the figures across the top: Covered outdoors (of the holders listed), Outside now, No phone yet and Phones gone quiet.

3. Tag holders lists each person or asset whose tag a Scout phone heard in the last 30 days. Holders no phone has heard are one count beside the title, so a large organisation stays a short list. Each holder is one of:

   Status	What it means
   Outside now	Their own phone placed their tag away from your sites in the last 15 minutes.
   Covered	Their own phone has placed their tag away from your sites, and is still reporting.
   Phone gone quiet	Their phone has not reported for a day, or has Scout or Bluetooth switched off.
   Seen at a site only	Only other people's phones heard the tag, at a site. They have no phone of their own carrying it yet: ask them to install Omaya Scout.

4. Their phone says which phone carries the tag, and what share of the holder's outdoor fixes it sent. It is worked out over the last 30 days as the phone that places the tag away from your sites; at a site every phone hears every tag nearby, so a phone heard only there carries nobody. A site is a geofence, or anywhere within 300 m of a location's pin.

5. The chips (All, Covered, No phone yet, Gone quiet) narrow the list.

6. The map shows where each covered holder was last outside. Click a holder for their trail; 24 h, 7 d or 30 d at the top right sets its range.

7. Phones, at the bottom, lists each phone that placed your tags in the last 30 days: its model, whose tag it carries, its app version, how many of your tags it heard, its last report and whether it is still Reporting.

Check it worked. Give someone with a tag Omaya Scout on their phone and ask them to walk outside your geofence for a few minutes. They move to Outside now, their phone appears under Their phone, and Covered outdoors goes up by one. If an Android phone finds the tag and an iPhone does not, the tag has not been heard by a gateway yet, or shares its ID with another tag.

The page needs View Monitor (overall), like the rest of the Monitor menu.

Outdoors: visits, trips and stops

A tracker outside reports a stream of positions. Omaya does not put each one on the trail — a day would be hundreds of rows. It keeps every position as a point on the map, and writes one trail row per stretch of time:

• Inside a geofence: one row for the whole visit, named after the geofence — "Car park", "Yard B", "Client site — Mutiara". If geofences overlap, the smallest wins, so a loading bay drawn inside a warehouse site names the bay.
• Outside every geofence, moving: a trip, shown with its distance — "Travelling · 2.4 km".
• Outside every geofence, staying put: a stop, once the tracker has stayed within the stop radius for the stop time. It is named by the nearest known place — "Stop · 350 m from Head Office" — or just "Stop" if nothing you have named is close enough.

The stop radius and the stop time are the two numbers that decide this, both on System → Configuration → Outdoor & GPS. GPS wanders 5–20 m on its own, so a radius smaller than that turns a parked van into a string of tiny trips. A tracker that goes silent and wakes up in the same place carries on the same stop; one that wakes up somewhere else after a long silence starts a new trip, because the route in between is unknown.

Two details that explain most surprises:

• A long silence in the same place is still the same stop. Many trackers stop reporting while they are still, to save battery. When one wakes up where it was, the stop simply carries on — a van parked overnight is one stop, not two.
• A long silence followed by a different place starts a new trip. The route in between is unknown, so Omaya does not pretend to know it.

A position the tracker itself rates as poor (worse than Ignore fixes worse than) is kept on the map but does not move the trail.

The handover between indoors and outdoors

Indoors wins. While a BLE gateway has heard the tracker recently — within Indoor wins for, two minutes unless you change it — indoor positioning owns the trail and any GPS position is only kept on the map. That stops a fix taken through a window, or the last fix before someone walks in, from pulling a person outside.

Walking out, the room's row ends when the gateways stop hearing the tracker, and the first outdoor row begins with the first GPS report after the handover window. Expect a gap of a minute or two between them: it is the time it took the tracker to send that report. Coming back in, the first gateway to hear the tag puts it in a room again, and the next time it goes outside starts a fresh row.

How Omaya knows someone is at home

Nobody enters a home address, and the person does not mark it. Omaya works it out from where their tracker spends the night:

1. It takes the outdoor positions of every tracker bound to the person, from the last 30 days, and keeps only those between 00:00 and 05:00 in your organisation's time zone.
2. Positions within 200 m of each other count as one place.
3. The place that appears on the most different nights is their home, as long as it appears on 3 nights or more. With fewer nights there is no home yet, and nothing below applies.
4. From then on, while they are within 200 m of that place, they are At home.

Omaya works the home out again at least every six hours, so a move shows up once the new place has three nights more than the old one in the last 30 days.

Only people have a home. For an asset or a vehicle bound to a tracker, a depot it parks at overnight is drawn like any other stop.

What "At home" changes

With Homes on maps and replays left at Hidden (the default, under Outdoor settings):

Where	What it shows for a person at home
Monitor → Entity Tracker	At home with the times, no marker and no route near the home
Monitor → Outside	At home, no position, listed after the people on the move, stopped or at a geofence
Reports → GPS Replay and the movement replay	The time at home as one At home stay, with no position and no route drawn within 200 m
Reports → Outdoor Activity	Time at home counted apart from time outside, and never where
Search and nearest-people answers	At home, with no position or distance
Rules on time outside	Time at home never counts towards Stopped outside a geofence (GPS) or the lone-worker check Not heard while outside (GPS)

Set it to Shown and a person's home is drawn like any other stop. Show homes only where your people have agreed to it.

When it gets it wrong

The home is a habit, not a fact anyone confirmed:

• Night shifts. Someone who works through the night at the same site gets that site as their home. Draw a geofence around it; inside a geofence they show at the geofence instead.
• New people and new trackers. There is no home until three nights of positions exist, so a new starter shows where they are on their first nights.
• No positions at night. A tracker that is switched off, or a phone without Omaya Scout running, at night gives Omaya nothing to work from; such a person never gets a home and is always shown where they are.

Geofences: naming the places that matter

A geofence is an outline on the map of a place you want called by its name: the car park, the yard, each client site, a restricted area. Everything outside them is trips and stops.

Space → Location → Map tab.

• Add one. Press Add geofence on the map, click the corners of the area, press Finish, give it a name and a type, and Save. Undo removes the last corner; Cancel throws the drawing away.
• Find one. The Geofences list beside the map has every geofence, searchable by name or type. Show zooms the map to it.
• Change one. Edit renames it or changes its type. Reshape lets you drag its corners. The switch on each row turns it off and on: a switched-off geofence stays on the map, greyed, and stops naming GPS positions.
• Delete one from the list or from its outline on the map.
• Name the places your tags keep going to. Under the list, Frequent stops, no geofence yet shows places tags have stopped at 3 times or more in the last 30 days outside every geofence: how many stops, by how many tags, how long in all and when last. A place whose stops are mostly overnight is marked as likely someone's home. Show circles the place on the map; Make geofence draws an outline around it and opens the form, so naming it is a name and Save. Reports → Outdoor Activity lists the same places under Places they keep stopping at, with a Make geofence button that opens this map ready to name it.

Draw them generously. GPS wanders by 5–20 m, so a geofence drawn tight to a building's walls misses half the positions taken in the car park outside it.

A new geofence also names its past: GPS positions of the last 90 days that fall inside it are matched to it, so stops already recorded there read as visits to the new place. Reshaping or switching a geofence off affects new positions only.

Switch off rather than delete

A geofence that is deleted leaves its old rows labelled just "Geofence", because the name has gone with it. If you want the history to keep saying "Old depot", switch it off instead.

Outdoor settings

System → Configuration → Outdoor & GPS. Every setting is your organisation's own; a sentence at the top of the panel says in plain words what the current numbers mean, and Use defaults puts the defaults back (press Save to keep them). Changes apply from the next GPS report; rows already written keep their shape.

Setting	Default	What it does	Change it when
Stop after	5 min	Standing still this long, outside any geofence, starts a stop.	Couriers making two-minute drops: lower it. Field staff whose short pauses should stay part of the trip: raise it.
Stop radius	50 m	Positions this close together count as standing still.	A parked tracker shows as a string of tiny trips: raise it. Below about 20 m, ordinary GPS wander breaks stops up.
New trip after silence	30 min	No report for this long, and it moved meanwhile: a new trip starts.	Trackers that report rarely: raise it, or every report is a new trip.
Indoor wins for	120 s	After a gateway last heard the tracker, GPS stays off the trail this long.	Someone working by a window keeps appearing outside: raise it. Outdoor rows start late after leaving: lower it.
Ignore fixes worse than	150 m	A position the tracker rates poorer than this is kept on the map but does not move the trail.	Trackers in dense city streets: raise it if trips go missing; lower it if positions jump across town.
Keep a still fix every	60 s	A tracker standing still keeps one point per this long on the map.	Fine-grained replays: lower it. Storage matters more than detail: raise it.
Or after moving	15 m	A position this far from the last kept point is always kept.	As above, for movement rather than time.
Name stops by places within	5 km	A stop is named by the nearest location or geofence this close.	Rural sites far apart: raise it. A dense city where "2 km from Head Office" says nothing: lower it, and draw geofences instead.
Street names	Off	Under Naming places. On: Outdoor Activity and GPS Replay show the street of a stop outside your places, looked up on OpenStreetMap (it receives the stop's coordinates; cached 30 days). Off: named from your own sites and geofences only, and nothing is sent anywhere.	Turn on when stops are far from any site and "25 km north-east of Head Office" is not enough. Leave off if tracker positions must not leave Omaya.
Likely homes in frequent stops	Hidden	Under Privacy. A place where most stays run through the night is probably someone's home. Hidden: it is left out of the frequent-stops lists on Location › Map and Outdoor Activity, which say how many were left out, and its position is never shown. Shown: it is listed with its position and flagged as a likely home.	Show them only if your trackers are vehicles or equipment parked overnight at depots you want to make geofences for.
Homes on maps and replays	Hidden	Under Privacy. Where a person spends the night, found from three or more nights of fixes there. Hidden: the Entity Tracker panel, its movement replay and GPS Replay say At home with the times, and draw no marker, route or position within 200 m of it. Shown: a person's home is drawn like any other stop. Assets and vehicles are always shown. See How Omaya knows someone is at home.	Show homes only where your people have agreed to it, for example lone workers whose safety plan covers time at home.
Trip speed	Hidden	Under Speed. Shown: trips on the Sensor Trail, Outdoor Activity and GPS Replay show their average speed (distance over time) and their top speed (the fastest 2 minutes of the trip). Speed is worked out from the GPS positions — about one a minute from a phone — so short bursts are smoothed out. Trips under 300 m or 2 minutes show none.	Turn on for vehicles and field staff, to tell driving from walking. Not suited to speeding checks.

The places a stop can be named after are your locations that have coordinates (set on the location itself) and your geofences.

Seeing it

• Reports → Sensor Trail. For a tag that reported GPS, an Outside tile (time outside, km, trips, stops), outside and distance columns in Per day, and an Outside tab beside Indoors: the route on a street map, where the time outside went, and the Journey — each stretch in order, Travelling with its distance, Stopped, or In a geofence, with its GPS fixes and a map link. Click a day to see only that day. A tag with no GPS in the range shows the indoor trail only.

• Reports → Outdoor Activity adds the stretches up: per tracker and day, the time outside, the distance, the trips, the stops and the geofence visits — and per geofence, how many visits, by how many trackers, and how long they stayed. Every stretch is listed under its tracker, with a map link for each stop. Narrow it with Date range, Label (the trackers of the people or assets carrying a label, such as Drivers or Vans) and Tracker, then Apply. Distance is the straight line between kept positions, so a winding road reads a little short. See Where they went below for the map.

• Reports → GPS Replay plays a person's or tracker's journey back on a street map. See Replay a journey outside below.

• Ask the AI. OAIA and AI Reporting know about outdoors: "where is Ali?" answers with the geofence, trip or stop and a map link rather than a room; "where has the van been today?" lists the outdoor stretches among the rooms; "how far did the vans go this week?" and "who went to the depot?" come from the same numbers as Outdoor Activity. See AI in Omaya.

• Roll Call. A person outside on GPS is Off-site — accounted for, with where and a map link — and a geofence can be the outdoor gathering point of a muster, where a GPS fix inside it counts as present. See Roll Call.

• From your own systems. The API has the same answers — where a tracker or person is now, every kept position, the outdoor activity and the geofences — under /api/v1/gps/…; see Reading data out.

• Movement Replay for a device draws the route on a street map: every kept position, joined up, with your geofences outlined. Open it from the map link in the Sensor Trail, from the Sensor Trail's replay button with a device chosen, or from Monitor → Live Monitor → Sensors → the device → Movement → Replay. Hover a position for its time and the geofence it was in.

• Monitor → Outside puts everyone outside right now on one street map: who is on the move, stopped, at a geofence, or not heard from for 15 minutes or more, with how long they have been out, today's distance and the age of the last position. Click someone for their route today. A person stopped where they spend the night reads At home, with no position. People who came back in within the hour are listed underneath. The page shows in the menu once your organisation has GPS positions from the last 30 days, and Monitor → Right Now & Live Alerts then gets an Outside now tile that opens it.

• Monitor → Entity Tracker. When the tracker is bound to an entity, someone outside gets their own Outside group, above the offline ones. The card says where — "Stop · 350 m from Head Office", "Travelling · 2.4 km", or the geofence — with Outdoor under it, how long, and the GPS chip. A tracker that reports every few minutes counts as online while it keeps reporting.

• The entity's panel shows the last day outside, stop by stop, whenever the entity's tag has a GPS position in the last 24 hours. The section is titled Outside · last 24 h, or Outside now and the place while it is outside, when it also takes the place of the floor plan. A street map shows the route with your geofences and each stop numbered; under it, a line sums up the stops, the distance, the fixes (and how many came from Scout phones) and the time of the last one. Then the stops and the trips between them, newest first: when each began, how long it lasted and, for a stop placed by phones, how many phones heard the tag and how close it was to them. Click a row to zoom the map to it. Replay on the map opens the same journey in GPS Replay.

• The entity's Movement Replay names each outdoor stay the same way, and while the scrubber is on one the floor plan gives way to a street map with the day's route and the person moving along it. The stays list, the timeline and Time by zone all include the time outside.

• Monitor → Live Monitor. In the Sensors list a tracker outside shows Outdoor and where — the geofence, trip or stop — in green. Its device window says the same, and Tracking → Presence shows Outside now with a street map, the last GPS fix and a link to its Movement Replay.

• Monitor → Scout (phones) shows where phones running Omaya Scout last placed each tag. See Phones as trackers: Omaya Scout above.

The moment a gateway hears the tag again, all of these go back to the room. The floor-plan views (Live Monitor's Floor Plan tab, and the zone counts on Monitor → Right Now & Live Alerts) stay indoor-only; Right Now's Outside now tile is the one count of people outside.

Elsewhere on the platform:

• Dashboard. Live Devices lists what is in your buildings; the Outside Now widget (add it with Edit Layout) lists who is outside, with the same tiles as Monitor → Outside and a small street map when the widget is wide enough. The Entities tile adds how many are outside.
• TV boards can show an Outside now widget: counts only, never names or positions, whatever the board's name setting.
• Search (Ctrl+K) says where a person or device is now — the room, Outside and the place, or At home — and finds geofences by name, opening the map on them.
• Live Monitor shows a tag placed by GPS as last seen at its latest fix, and a person stopped at home as At home, with no position.
• Entity Tracker. Time outside shows its real length on the day strip and the Timeline. Today counts arrival and time on site indoors, with time outside beside it. GPS fixes taken while a gateway placed the person indoors are not counted as an outdoor stop, here or in GPS Replay. The floor-plan pin clears as soon as someone goes outside.
• Security Watch (Assign) and Facility (Nearest available) list people on site first, then staff outside nearest first ("Outside · 1.2 km away"), with people at home last and without a position.
• Visitor. A badge seen outside reads Outside, the host and reception are told once when a visitor leaves the site with the badge (its own switch under Notifications), and the automatic check-out counts only your own gateways' sightings.
• Warehouse shows an asset outside as Outside, with a link to Monitor → Outside.
• OAIA's briefing points out long stops away from your sites compared with that person's usual stops, tags that went quiet outside, low batteries on tags used in the field, and assets moving outside site hours. Home locations are never shown.
• Data subject requests (System → DSAR) include outdoor positions in the export and delete them on erasure.
• Entity access by role applies to GPS Replay, Outdoor Activity, Monitor → Scout, Device Replay and OAIA's outdoor answers.

Where they went, on Outdoor Activity

Outdoor Activity's Where they went card answers "where were they when they were not at one of our places?"

1. Open Reports → Outdoor Activity, set the Date range and press Apply.
2. Read the map. Every stop outside your geofences is an orange spot, bigger for longer; every geofence visit is a green one. Your sites and geofences are drawn too, and a dashed line joins each tracker's stretches in order.
3. Read the list beside the map, longest first. Stops within 150 m of each other are one spot. Each spot shows its name, how many visits, who, the total time and the last visit.
4. Click a spot in the list to zoom the map to it.
5. Replay last visit opens GPS Replay on whoever was there last, on that day. Google Maps opens the spot there.

A spot inside a geofence is named after it. Any other spot is named by its distance and direction from your nearest site or geofence, such as 25 km north-east of Head Office. That name is worked out inside Omaya from your own places, so no position is sent anywhere to be named. To see the street as well, turn on Street names (see Outdoor settings); the street then comes first, with the distance from your nearest site under it.

The report also links into GPS Replay from each tracker: Replay on a tracker's row plays its days outside in the range (up to the last 7), and Replay on a day in the tracker's detail plays that day. A tracker bound to a person or asset opens as that person or asset, with all their tags. The Replay button on the card plays the one tracker on screen, or opens the replay on your dates for you to pick someone.

Check it worked. Click Replay last visit on a spot: GPS Replay opens with that person or tracker already picked and the day of the visit loaded.

Replay a journey outside (GPS Replay)

/admin/report/gps-replay: Reports → GPS Replay

GPS Replay plays back a day outside: where someone or something stopped, for how long, and the way between. It reads every GPS position, from a tracker's own GPS or from Omaya Scout phones, so a long stop with a silence in the middle shows the silence rather than hiding it.

1. Open Reports → GPS Replay, or follow a Replay link from Outdoor Activity, the Sensor Trail's GPS Replay button, or Replay on the map in an entity's panel. Those links open with the person and the days already chosen.
2. Set the Date range. Up to 7 days load at once.
3. Pick the Entity or sensor. Before you pick, the page lists Outside in this range: everyone with a GPS position in the dates, newest first. An entity follows all the tags it carries.
4. Press Load replay.
5. Press Play. Choose a speed: 1 min/s, 5 min/s (the default), 15 min/s or 1 h/s. Previous stop and Next stop jump between stops. Drag the bar under the map, or use ← and → (with Shift, 10 minutes at a time), to move to a moment. Follow keeps the tag in view.

Check it worked. The line over the map names who and which day, and the journey beside the map lists at least one stop or trip.

What the page shows:

• The line over the map sums up the replay: who, the day, the first and last position, the distance, the stops and the time still, the time moving, and where the positions came from.
• The bar under the map is coloured by what was happening: Stop, In a geofence, Travelling, and hatched for Not heard, when no position came for longer than New trip after silence and the way it went is not known.
• The card beside the map follows the playhead: the time, whether it was stopped or moving, the place and since when. Fix details under it opens the position behind that moment: which tracker or phone sent it, how many phones heard the tag, and how accurate it was.
• Journey: the stops, numbered, and the trips between them in order, such as Travelled 1.1 km in 8 min. The one under the playhead is highlighted. Click any of them to jump there.
• Signal details, folded at the bottom: per stop and trip, the time, how long, where, and the fixes, phones, distance between tag and phone, and accuracy behind it.

Stops are named the same way as on Outdoor Activity: the geofence, otherwise the street when Street names is on, otherwise the distance and direction from your nearest site. The Outdoor Activity button at the top opens that report for the same tracker and dates.

GPS Replay and Outdoor Activity need the View Sensor Status Report permission, the same as the Sensor Trail.

Rules and webhooks on geofences

A tracker going into or out of a geofence can raise an alert, page someone or call your systems, like any other rule.

A rule on a place. In the rule builder, click the Watches box, choose Geofence (GPS) and pick the geofence, then add the condition Geofence entered / left (GPS) equal to entered or left. The rule wakes for any tracker that crosses that geofence — "tell the supervisor when a van leaves the depot":

Scope	Geofence (GPS) → Depot
Condition	Geofence entered / left (GPS) = left
Action	an alert, email, Telegram… with {{device.name}} and {{geofence.name}} in the message; an alert, email, WhatsApp or SMS can add {{map_link}}, where it crossed

Each tracker keeps its own Repeat at most every clock, so the second van leaving a minute after the first is not silenced by it.

Only some trackers. Only for, under the geofence you picked, keeps the place rule but narrows who fires it: these devices, these people or assets, anyone with these labels, or people only or assets only. "Tell me when Aisha leaves the office campus" is a geofence rule on the campus, Only for → These people / assets → Aisha.

Omaya Scout tags count too. A tag a phone running Omaya Scout hears is placed by the phone's GPS, and its crossings fire geofence rules like a tracker's own fix. Leaving needs a fix inside the geofence first: while an indoor gateway hears the tag, the phone's fixes do not move it, so a tag that never leaves gateway range has no fix inside the campus to leave from.

A rule on a tracker, a person or a group. Watch the Device, the Person / asset it is bound to, or a Label instead, and use the same condition: it fires when that tracker (or any tracker under the label) enters or leaves any geofence, and {{geofence_name}} says which. Watching the person keeps the rule working when their tracker is swapped. See Your first rule for what each choice covers.

A crossing is the GPS fix that lands on the other side of the line, so it is as quick as the tracker reports — every few minutes for most. Going into a building inside the geofence and coming back out is not a new crossing. The geofence_event condition and its values are in Rule metrics.

Every crossing is also written to System › Activity Log under System events — "Sam entered Head office", "Sam left Head office" — and shows in the History of the person and the device.

Rules on time outside

Four conditions watch people and assets while they are outside. They are in the condition list under Outside (GPS), for a rule that watches a device, a label or a person / asset:

Condition	Fires when
Time outside (GPS)	they have been outside longer than the minutes you set
Stopped outside a geofence (GPS)	they have stopped in one spot that is not in any geofence for that long
Not heard while outside (GPS)	nothing has been heard from them for that long, and the last thing heard put them outside — a lone-worker check
Speed (GPS)	the speed at their latest fix is above the km/h you set

A person is all their tags together. They are checked every minute, and each fires once per stretch outside (once per stop, once per silence), not again and again while the person stays out. A person stopped, or gone quiet, at home is never counted. Speed is the tracker's own figure when it sends one, otherwise worked out from its previous fix.

Panic and man-down. A panic or man-down press says where the person is: the room, when a gateway hears the button; outside, the geofence, trip or stop with the GPS position and a map link; otherwise the last GPS position, marked as such. It is in the page text ("Where:" and "Map:") and in the emergency.activated webhook as location.

Webhooks. Subscribe an outbound webhook to geofence.entered and geofence.exited to have every crossing sent to your system, with the geofence, the tracker, the person it is bound to and the position — see Webhook events.

When something looks wrong

What you see	Why	What to do
No outdoor rows at all	Nothing is arriving with a position, or the tracker is heard indoors the whole time	Check the device's latest reading has a latitude and longitude. A tracker that has not got a fix yet sends 0, 0, which is ignored.
A walk is chopped into many short trips	The stop radius is smaller than the GPS wander, or reports are further apart than New trip after silence	Raise Stop radius, or New trip after silence for trackers that report rarely.
A lunch break does not show as a stop	Fewer than two reports in the same place, at least Stop after apart	Trackers that only report while moving show the stop when they next report. Lower Stop after if stops are short.
Someone at their desk shows outside now and then	A GPS fix arrived while no gateway had heard the tag for a while	Raise Indoor wins for, and check gateway coverage at that desk with A tag shows in the wrong room.
A stop is just "Stop"	No location or geofence within Name stops by places within	Draw a geofence for the place, give the location coordinates, or raise the distance.
Old rows say "Geofence" instead of a name	That geofence was deleted	Nothing to repair; switch geofences off rather than deleting them in future.
Times bunch up when a tracker comes back into coverage	Positions stored while it had no signal arrived late	When a report arrives more than a few minutes after it was taken, Omaya places it at the time it arrived.