4.2.1. Call Vetting and Processing • Contractor must complete auto-ID analysis of all calls provided and manually vet high-quality bat call files (i.e. NABat guidance recommends manual verification of a minimum of one audio file per species per night to establish presence-absence) o When able, calls must be identified to species or species group o Due to the abundance of calls at some locations, our project objectives, and NABat requirements, not all calls need manually vetted. See USGS reports “A Plan for the North American Bat Monitoring Program (NABat)” and “A Guide to Processing Bat Acoustic Data For the North American Bat Monitoring Programs (NABat)” for appropriate protocols. 4.2.2. Data Formatting and Return to KDWP • Contractor will document and provide KDWP the analysis software used, input parameters, ID classifiers, and other settings used to complete call file auto-ID o Contractor should follow protocols set in the “Guide to Processing Bat Acoustic Data for the North American Bat Monitoring Program (NABat)”. Deviations from this document should be reported and justified. • All auto-ID metadata and/or output files produced by the Contractors analysis software will be provided to KDWP. • All output call files that have been reviewed by analysis software and contractor manual identification will be returned to KDWP and contain the attributes included by the software and/or the manual reviewer. • For each GRTS cell, an Excel Spreadsheet or CSV will be provided to KDWP that is formatted using the most recent NABat Stationary Acoustic Full Metadata bulk upload template (will be provided by KDWP). Template must be populated with: o Metadata that will be provided by KDWP such as GRTS cell, audio recording name, call timestamp, etc. o Species auto-ID determined by the contractor’s software o Manual vetting identification when species or species groups are identified
