Checklist
Checklist for flight safety and metadata logs compatible with oucass-profiles.
To run, simply ensure that click is installed and type the command "checklist" into the terminal.
Safety checks include
- Check for visual obstacles and potential source of interference
- Clear and agree on a takeoff and landing zone
- Decide if current weather conditions are appropriate for safe flight
- Visual inspection of the vehicle
- Verify Mission Planner software prepared
- Connect ground station RF to laptop
- Verify controller prepared
- UAV battery setup
- Connect telemetry
- Confirm no error messages with Mission Planner
- Confirm GPS fix type (outdoors must get 3D fix)
- Check data logging
- Place vehicle at launch point
- Check flight mode on controller
- Confirm data logging software running
- Check sensors are in correct range
- Review flight plan - verbal and on Mission Planner
- Test audio communications among participants
- Check if all participants ready for flight
- Arm UAV
- Check GPS lock
- Clear props
- Notify participants mission is complete
- Disarm UAV
- Disconnect battery
- Inspect UAV
Metadata logs include
- Location name and ID
- Location info, such as the surface altitude, nearby Mesonet stations, and region from the CF Standard Region List
- Pilot in command
- Other pilots on site for COA flights
- Flight objective
- FAA authorization type
- Platform (UAV) ID
- Scoop ID
- Battery ID
- Initial and final battery voltages
- Cloud cover
- Rain (yes/no)
- Maximum planned and maximum obtained altitudes
- Launch and land times (in UTC)
- Emergency documentation
- Private and public remarks
Use Admin mode to
- add, remove, or reorder saved platforms
- add, remove, or reorder saved locations
- add, remove, or reorder saved objectives
Metadata
Release files for oucass-checklist 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| oucass-checklist-0.3.0.tar.gz | 13.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oucass_checklist-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.4 kB
Release files / oucass-checklist-0.3.0.tar.gz
| Download URL | oucass-checklist-0.3.0.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
82bb4c96e9d3b14d5c586df8e790b98674a63ee151cdabad1cebaccc492b58b8
|
|
BLAKE2b-256 checksum How to use checksums |
341496e91fbd4889a56dfd0dee19c2cceaafa2052b1b681b13f95c1fd5f6fb9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.6.9
|
Release files / oucass_checklist-0.3.0-py3-none-any.whl
| Download URL | oucass_checklist-0.3.0-py3-none-any.whl |
|---|---|
| Size | 27.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
998188cb33a91b428bbc1b367f1fddc39afec1fc3eacc3dcc210fa2a45f6051b
|
|
BLAKE2b-256 checksum How to use checksums |
22b847d1ce3626ee18b920104a6df6910474669d7a79c5d61ab1240445c6683f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.6.9
|
Security for oucass-checklist 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.