Some workflows need only the aircraft inside a particular area. dump1090-geofence lets you describe that area explicitly and forward the matching observations, reducing the amount of downstream logic each consumer needs to maintain.
Choose the boundary that fits
Supported regions include bounding boxes, circles, and GeoJSON polygons with holes. Additional altitude and address-list filters can refine the selection. Deny rules take precedence, making an exclusion explicit instead of relying on the order in which a consumer happens to process conditions.
Keep outputs consistent
The project can produce filtered Beast or SBS streams and aircraft JSON. A linger setting helps manage aircraft near the edge of a selection rather than making a downstream display depend only on the latest instantaneous position. The correct choice depends on whether you need strict filtering or continuity in an interface.
Inspect before forwarding
Dry-run output explains allow and deny decisions so you can review the rules before relying on the filtered feed. Test boundaries with known positions, particularly around polygon edges and excluded areas. The filter operates on received observations; it cannot classify aircraft that your upstream feed has not supplied.
Explore dump1090-geofence → · Source and documentation ↗