Rules, geofences, and spatial events
Turn geometry, time, state, and observations into conditions a workflow can evaluate.
Why this matters
A map becomes operational when software can evaluate what a location means instead of only drawing it. Rules make that reasoning explicit and testable.
Learn it
A geofence is a geographic boundary used in a rule. Point-in-polygon can evaluate whether a position is inside an area. Other conditions can use distance, direction, time, attributes, freshness, or state. A transition such as outside → inside can become an event. Good rules state their inputs, condition, and expected result clearly enough to test.
Work through an example
A vehicle position enters Survey Area A while a temperature observation exceeds a project threshold. Those can be separate conditions or combined into a rule depending on the workflow.
input data + spatial context + condition → event/resultPractice
- 1Write one rule in plain language using geometry plus one other condition.
- 2List the exact data fields the rule needs.
- 3Create one test case that should match and one that should not.
Try it
Follow data through a workflow
Select each stage. The goal is to keep the source, connection, protocol, data, spatial context, rule, and use understandable instead of collapsing everything into one box.
The real-world fact, device, file, application, person, or system that starts the workflow. If it is an observation, preserve where, when, what, source, value, units, and provenance.
What to watch for
Do not confuse a geofence with the event it may produce. The geometry is the boundary; the rule evaluates data; the event records a meaningful occurrence.
Where this takes you
Use spatial rules for arrivals, departures, research areas, service zones, field assignments, exceptions, and automated workflows.