What is a geofence?
A geofence is a boundary on a map. It can be a small radius around a dock door, a booth, a warehouse yard, a campus, or a larger polygon around an operating area.
Atlasemoji / DataSynch
Fixed geofence trial help
Use the home-page trial to create a real saved geofence, place it on the map, capture consented participants, and understand how geofence events can start operational workflows.
It is a trigger, not only tracking
When a consented phone, scanner, truck, plane, vessel, asset, or event enters or exits the boundary, Atlas can trigger email, webhook, alert, DataSynch event, exception, dispatch, CRM note, or another workflow.
Last known vs current location
The map can show the last known location immediately. Current location appears after the device/browser/app sends a new update, which can take a moment.
Consent matters
Do not track a friend, driver, visitor, or device unless that participant accepts the invite and agrees to location sharing. Participants must be able to stop sharing or revoke consent.
Operations examples
A loading dock arrival, conference room demo, field team check-in, container yard movement, vessel arrival, plane crossing, or scanner event can all be handled as geofence-triggered workflow.
Why the Android app helps
Browser location is useful for demos. The Android app can provide a better field workflow for consented location pings, scanner behavior, and mobile operational use.
What actually happens when the boundary is crossed?
The fixed geofence itself is only the saved rule. It becomes operational when a consented participant or device sends a location ping. Atlas compares that point to the saved radius. If the prior state was outside and the new point is inside, Atlas records an entry event. If the prior state was inside and the new point is outside, Atlas records an exit event. The event can carry the participant, geofence, radius, distance from center, timestamp, and map context so downstream workflows have evidence instead of a vague notification.
Using a phone as the homebase
A phone can act as the moving reference point for a temporary geofence. For example, a supervisor, demo host, driver, or field lead can share a consented phone location and use that point as the current operating center. Other participants, assets, or scans can then be compared against that live center, or the phone can simply prove presence at a fixed location such as a booth, loading dock, or jobsite gate.
Scaling beyond one test circle
The same pattern works for hundreds or thousands of locations and many mobile users. A customer can load stores, docks, yards, terminals, hospitals, campuses, ports, aircraft gates, vessel areas, or service territories as geofences. DataSynch can then normalize pings from phones, scanners, EDI/API events, truck feeds, air traffic, vessels, or internal systems and produce operational events when those pings cross the saved boundaries.
How to stop sharing
Turn off browser/app location permission, use the revoke link from your invite flow, or contact Atlasemoji support. A saved manifest can remain visible while live location sharing is paused, stale, or revoked.