1 · Supply
Provide event rows and a pre-calculated geofence_distance_m field from your simulator or analysis workflow.
Open Studio · No-Spray Guard v0.1.0
Audit drone no-spray zone events before release.
No-Spray Guard audits recorded or simulated drone-spray events against an explicit review profile. It exposes boundary, altitude, speed, and state/flow inconsistencies as source-row-linked findings—without calculating a legal geofence or issuing an actuator command.
public browser releasebrowser-onlysimulator / recorded datano actuator path
- Published
- 2026-08-26
- Reviewed
- 2026-08-31
- Version
- 0.1.0
- Owner
- UAM Korea Tech
- Review
- Internal release review
- Evidence
- E2 · local functional checks
- Status
- Public browser tool · no command path
- License
- Apache-2.0 · public source package
Audit boundary
A rule profile, a source row, and a human decision.
2 · Audit
Deterministic browser code applies visible thresholds for boundary distance, altitude, speed, and flow-state consistency.
3 · Disposition
Block and review findings retain the source CSV row so a human can verify, document, and resolve each event.
WORKING TOOL · RULE AUDIT ONLY
No-Spray Guard
Audit recorded or simulated events against an explicit review profile. Processing stays in your browser; no aircraft, pump, valve, payload, or chemical command is created.
Review profile
These are user-selected screening thresholds, not legal, agronomic, or manufacturer limits.
Safety and evidence boundary
This tool audits supplied values only. geofence_distance_m must be calculated and supplied by the user or simulator. It does not calculate a legal exclusion polygon, certify compliance, or issue actuator commands.
- 01
Load the bundled sample and confirm 10 valid rows, 1 block finding, and 5 review findings under the default profile.
- 02
Adjust one screening threshold and confirm that the queue changes deterministically.
- 03
Choose a compatible CSV only after supplying geofence_distance_m from a documented simulator or analysis process.
- 04
Export the JSON audit and preserve it with the source CSV and the profile used for review.
Rule set
Four narrow checks, no hidden compliance claim.
Exclusion boundary
Spray-on event inside the user-selected boundary distance → block.
Altitude envelope
Spray-on event outside the selected altitude range → review.
Speed envelope
Spray-on event above the selected speed threshold → review.
State / flow consistency
Spray state and supplied flow rate disagree → review.
License and limits
A rule audit is not a flight-safety or legal determination.
The UAMKT-authored source package is available under Apache-2.0 with its notices and synthetic sample. The tool audits supplied values only. It does not calculate an exclusion polygon, prescribe a no-spray distance, certify compliance, validate a chemical label, or control an aircraft, pump, valve, payload, or dose. Operators remain responsible for authoritative maps, local aviation and environmental rules, equipment validation, and qualified human review.
Source package · LIVE
Inspect the package and validation boundary before downloading.
No-Spray Guard v0.1.0 is distributed as a self-contained, inspectable archive. Review the manifest and checksum before use.
- Archive
- 8.1 KB
- Version
- v0.1.0
- License
- Apache-2.0
- Updated
- 2026-08-31
- Evidence level
- E2 · local functional checks
Package manifest · 6
- README.md
- LICENSE
- THIRD_PARTY_NOTICES.md
- package.json
- examples/sample-no-spray-events.csv
- src/index.ts
SHA-256
56a43034e087a4c62f15fe0f37c80f47871fcfd15032e82bae3418eba15ae17bThe checksum detects changes to the downloaded file only. It does not certify code safety, fitness, identity, or chain of custody.