Setting geofence boundaries in Drone Programming - Step-by-Step Execution

Concept Flow - Setting geofence boundaries

Start

↓

Define geofence coordinates

↓

Set geofence boundaries in drone system

↓

Drone checks position

↓

Is drone inside geofence?

No→Trigger alert or action

Yes↓

Continue normal flight

↓

End

The drone system defines geofence boundaries, then continuously checks if the drone is inside. If outside, it triggers an alert or action.

Execution Sample

Drone Programming

geofence = [(lat1, lon1), (lat2, lon2), (lat3, lon3), (lat4, lon4)]

for position in drone_positions:
    if not inside_geofence(position, geofence):
        alert('Outside geofence!')
    else:
        continue_flight()

This code sets a geofence polygon and checks drone positions to alert if outside.

Execution Table

Step	Current Position	Check inside geofence?	Result	Action Taken
1	(34.0, -118.0)	Yes	True	Continue flight
2	(34.1, -118.1)	Yes	True	Continue flight
3	(34.5, -118.5)	No	False	Alert: Outside geofence!
4	(33.9, -117.9)	Yes	True	Continue flight
5	(35.0, -119.0)	No	False	Alert: Outside geofence!

💡 All positions checked; alerts triggered when outside geofence.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5
position	None	(34.0, -118.0)	(34.1, -118.1)	(34.5, -118.5)	(33.9, -117.9)	(35.0, -119.0)
inside_geofence	N/A	True	True	False	True	False
action	None	Continue flight	Continue flight	Alert	Continue flight	Alert

Key Moments - 3 Insights

Why does the drone trigger an alert at step 3 even though it was flying normally before?

At step 3, the position (34.5, -118.5) is outside the geofence polygon, so inside_geofence is False, triggering the alert as shown in the execution_table row 3.

What happens if the drone position is exactly on the geofence boundary?

Typically, the inside_geofence function treats boundary points as inside, so the drone continues flight without alert, similar to steps where inside_geofence is True.

Why do we keep checking positions even after an alert is triggered?

The drone continuously monitors its position to respond immediately if it leaves or re-enters the geofence, as shown by multiple checks in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the action taken at step 5?

A Continue flight

B Alert: Outside geofence!

C No action

D Return to base

💡 Hint

Check the 'Action Taken' column for step 5 in the execution_table.

At which step does the drone first go outside the geofence?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Check inside geofence?' and 'Result' columns to find the first False.

If the drone position at step 4 changed to (36.0, -120.0), what would be the new action?

A Alert: Outside geofence!

B Continue flight

C No action

D Hover in place

💡 Hint

Refer to variable_tracker for how 'inside_geofence' affects 'action' when position is outside.

Concept Snapshot

Setting geofence boundaries:
- Define polygon coordinates for allowed area
- Continuously check drone position
- If outside, trigger alert or safety action
- Helps keep drone within safe zones
- Use functions to test point inside polygon

Full Transcript

This visual execution shows how a drone uses geofence boundaries to stay within a safe area. First, the geofence polygon is defined by coordinates. Then, for each drone position, the system checks if it is inside the geofence. If inside, the drone continues flying normally. If outside, an alert is triggered to warn or take action. The execution table traces each position check, showing when alerts happen. Variables like position and inside_geofence update each step. Key moments clarify why alerts occur and how boundaries are handled. The quiz tests understanding of these steps. This helps beginners see how geofence logic works step-by-step.