Search Results

Back to Search ERROR WARNING: Name of Species List for Manual Id must be specified when Manual Id is specified. HOW TO RESOLVE: Species list errors will appear as missing-field or invalid-categorical errors. When uploading acoustic data, you must specify which custom species list was used for Auto ID and Manual ID -- the corresponding fields are 'Name of Species List for Auto Id' and 'Name of Species List for Manual Id'. These fields behave like controlled categorical fields but are managed in the Partner Portal rather than in your CSV. Create or edit your project's species lists in the Partner Portal, then enter the exact list names in your upload file. ADDED EXPLANATION: Knowing which species were considered during Auto ID and Manual ID analyses is essential for estimating detection probabilities and modeling populations. Errors involving the 'Name of Species List for Auto ID' and 'Name of Species List for Manual ID' fields arise when the names provided in the CSV do not match any list defined in the Partner Portal. To resolve these errors, navigate to your project's Species Lists tab, enter edit mode, and add a new list. Give the list a clear name, provide a brief description, and use the Definition column to include or exclude species. After saving, enter the exact list name in the 'Name of Species List for Auto Id' and/or 'Name of Species List for Manual Id' fields in your CSV. Projects may use different lists for Auto ID and Manual ID—for example, a comprehensive regional list for automated classification and a smaller subset for manual verification. Ensure every list referenced in your data has been created in the Partner Portal and is named exactly as it appears in your upload file.

Back to Search ERROR WARNING: invalid input syntax for type time: HOW TO RESOLVE: This error is due to a date and/or time formatting issue. Use the template's second header row the view data type requirements and replace the erroneous data in flagged fields accordingly. Adjust cell formats or use find/replace to convert values to the correct type. ADDED EXPLANATION: Each field in the template requires a particular data type (text, integer, decimal, date-time, or true/false) or a controlled categorical response. Values that don't match these requirements will be rejected. In a spreadsheet, adjust cell formats or use find/replace to convert values—for example, changing numbers stored as text into actual numbers, converting decimals to integers, or trimming time-zone suffixes from date-time strings. For widespread issues in non-required fields, consider omitting the column entirely and re-uploading.

Back to Search ERROR WARNING: A Internal winter hibernaculum survey must have a site use type of hibernacula or winter roost HOW TO RESOLVE: 'Site Use Type' missing required entry of 'winter hibernacula' or 'winter non-hibernacula'. Ensure each record includes values for all required fields before re-uploading. ADDED EXPLANATION: Surveys must include key fields that answer the "where, what, when, and who" questions: either a GRTS Cell ID or latitude/longitude to locate the survey, a Site Name to describe the place, survey start and end times, and the names of surveyors. Each survey type may also require a few additional fields. If required columns are missing entirely, the upload wizard will block the file. If required columns are present but individual rows lack values, those rows will be flagged while the rest of the file can load. Use the template's informational header rows to identify which fields are required and ensure each data entry row contains values for these fields before uploading.

Back to Search ERROR WARNING: needs to include date and time HOW TO RESOLVE: Use the template's second header row to view data type requirements and replace erroneous data in flagged fields accordingly. Accepted timestamp formats are listed in the second header row for the 'Audio Recording Time' field. Adjust cell formats for errored records or use find/replace to convert values to the correct type. Example: The 'Audio Recording Time' field accepts timestamps listed in the format displayed above. ADDED EXPLANATION: Each field in the template requires a particular data type (text, integer, decimal, date-time, or true/false) or a controlled categorical response. Values that don't match these requirements will be rejected. In a spreadsheet, adjust cell formats or use find/replace to convert values—for example, changing numbers stored as text into actual numbers, converting decimals to integers, or trimming time-zone suffixes from date-time strings. For widespread issues in non-required fields, consider omitting the column entirely and re-uploading.

Back to Search ERROR WARNING: Unable to distrubte transect points HOW TO RESOLVE: Ensure each row has a valid location combination: 'GRTS Cell Id' alone, 'GRTS Cell Id' with 'Quadrant', or 'Latitude'/'Longitude'. Verify longitudes are negative and lat/long values aren't swapped. If both 'GRTS Cell Id' and coordinates are present but conflict, remove whichever you trust less—delete the 'GRTS Cell Id' value (keeping the column) if you trust coordinates, or omit lat/long to let the system match on cell ID and site name. Ensure site names are unique to prevent ambiguity. For repeat visits to established sites, verify coordinates remain consistent—new coordinates within 55m of an existing site are ignored, coordinates 55–100m away create a new map point but maintain site association, but coordinates exceeding 100m generate an entirely new site record, breaking data continuity and preventing trend analyses. Mobile transect surveys operate under different logic that matches primarily on unique Site Name values; see "ADDED EXPLANATION" for details. ADDED EXPLANATION: NABat requires at least a 'GRTS Cell Id' to assign surveys to a 10×10 km grid cell, but recommends providing additional granularity via 'Quadrant' or 'Latitude'/'Longitude' when possible. Location errors occur when this information is missing, ambiguous, or internally conflicting. Ambiguity commonly arises when generic site names (e.g., "Bridge 1" or "Cave") are reused across multiple locations, or when provided coordinates fall outside the boundaries of the stated GRTS cell. For large datasets, load coordinates into GIS or mapping tools to verify placements and catch systematic issues such as swapped lat/long columns or missing negative signs. To avoid unintentional site splits when revisiting established sites, verify coordinates match prior uploads or omit coordinates entirely to let the system match on Site Name alone. Mobile transect surveys can match solely on a unique 'Site Name' value, bypassing some ambiguity checks applied to other survey types. It is recommended that users draw a line object representing their route on the project map, named to exactly match the Site Name value(s) in the upload file. The portal can then estimate missing lat/long coordinates by combining route geometry with elapsed time during the survey. Without a defined line object, surveys traversing multiple GRTS cells with missing coordinates cannot be processed—users must estimate coordinates themselves or provide the 'GRTS Cell Id' for each record. Surveys occurring entirely within a single cell should still have their route drawn; however, users preferring coarser resolution can provide only the 'GRTS Cell Id'.

Back to Search ERROR WARNING: A recording name is unique to a project and can only be processed as part of one deployment. An entry of this recording name already exists HOW TO RESOLVE: Duplicate errors occur when the system encounters repeated survey records. This error typically occurs when duplicate records occur within an individual csv. Use conditional formatting on a unique identifier—such as 'Audio Recording Name' for acoustic surveys, or a concatenated set of fields (using CONCAT or TEXTJOIN) for other survey types—to highlight repeated rows, then delete or consolidate them. If duplicates persist despite removing and re-uploading affected data, contact the NABat Technical Outreach Team. ADDED EXPLANATION: The duplicate detection logic in the NABat database varies by survey type. For emergence count surveys, each unique combination of Site Name, Exit Identifier (if provided), Surveyor, and Species should appear in a single row—multiple rows from the same surveyor for the same combination are flagged as duplicates, whereas rows from different surveyors are averaged to produce the final count. Roost count surveys use different logic: counts are summed within each surveyor's report for a given site, section, and species, and if multiple surveyors report, their sums are averaged—so duplicates are not flagged in the same way. Beyond survey-type logic, duplicate errors can arise from re-uploading the same data in quick succession, inadvertently uploading the same survey under different file names, accidental copy/paste duplication within a file, or leftover data from older versions of the upload logic. When identifying duplicates within a file, Excel's Conditional Formatting (Home → Styles → Conditional Formatting → Highlight Cells → Duplicate Values) can highlight repeated values in a unique identifier column. For surveys lacking a single unique field, create a new column that concatenates key fields to form a composite identifier. When comparing across uploads, note the conflicting file's name and created date in the Partner Portal, download it, and review side-by-side with your current file to determine which version is more complete or accurate. In rare cases, the database may retain artifacts of previously deleted data that trigger duplicate errors on subsequent uploads—if you suspect this scenario after repeated removal and re-upload attempts, contact the NABat Technical Outreach Team to investigate.

da614f33-c539-44a0-9514-ed406ede658c Photo credit: J. Scott Altenbach USFWS Next WNS & Listing Status Myotis velifer Order: Chiroptera Suborder: Yangochiroptera Family: Vespertilionidae Call characteristics: High frequency caller (~40 kHz range) Weight 1/4 - 1/2 oz (7 - 14 g) Body Length 2.25 in (5.6 cm) There are various sources for bat species range maps including IUCN , NatureServe , U.S. Fish and Wildlife Service ECOS , and the National Atlas of the United States . US SWAP National List IUCN Red List Canada Species at Risk Mexico Cave Myotis The cave Myotis varies in appearance depending on region, with individuals in the eastern portion of the range having paler brown fur and individuals in the west appearing darker brown. The face, ears, and wing membranes are a dark, dusky color. Prey includes moths, beetles, weevils, and other insects. The cave Myotis prefers forested habitat across a range of elevations. This species roosts in caves, tunnels, buildings, and abandoned mines. Some cave Myotis have been observed migrating south for winter, while others hibernate near their summer habitat. Disturbance and encroaching vegetation that impedes access to cave roosts pose a threat to this species. Information used to populate this page was obtained from the following sources: NatureServe Explorer United States Fish and Wildlife Service Environmental Conservation Online System Bat Conservation International Bat Profiles National Atlas of the United States. (2011). North American Bat Ranges, 1830-2008. National Atlas of the United States. Available at: http://purl.stanford.edu/pz329xp4277. Taylor, M. 2019. Bats: an illustrated guide to all species. Washington, DC: Smithsonian Books. Conservation Status Previous Next

Back to Search ERROR WARNING: null value in column "" violates not-null constraint HOW TO RESOLVE: Enter missing required data based on the template's header rows—the third row indicates 'required' status by field, and the second row lists data type restrictions. Ensure each record includes values for all required fields before re-uploading. ADDED EXPLANATION: Surveys must include key fields that answer the "where, what, when, and who" questions: either a GRTS Cell ID or latitude/longitude to locate the survey, a Site Name to describe the place, survey start and end times, and the names of surveyors. Each survey type may also require a few additional fields. If required columns are missing entirely, the upload wizard will block the file. If required columns are present but individual rows lack values, those rows will be flagged while the rest of the file can load. Use the template's informational header rows to identify which fields are required and ensure each data entry row contains values for these fields before uploading.

Back to Search ERROR WARNING: Audio recording metadata is required to upload acoustic survey results HOW TO RESOLVE: Enter missing required data based on the template's header rows—the third row indicates required status by field, and the second row lists data type restrictions. Ensure each record includes values for all required fields before re-uploading. Example: Providing a unique 'Audio Recording Name' is a 'REQUIRED' for each record to ensure a successful data upload. ADDED EXPLANATION: Surveys must include key fields that answer the "where, what, when, and who" questions: either a GRTS Cell ID or latitude/longitude to locate the survey, a Site Name to describe the place, survey start and end times, and the names of surveyors. Each survey type may also require a few additional fields. If required columns are missing entirely, the upload wizard will block the file. If required columns are present but individual rows lack values, those rows will be flagged while the rest of the file can load. Use the template's informational header rows to identify which fields are required and ensure each data entry row contains values for these fields before uploading.

Back to Search ERROR WARNING: No location found matching location name. HOW TO RESOLVE: This error occurs when 'GRTS Cell Id' and 'Latitude'/'Longitude' are both missing from a record. Ensure the ''GRTS Cell Id' field or "Latitude'/'Longitude' fields are completed for each submitted record. ADDED EXPLANATION: Surveys must include key fields that answer the "where, what, when, and who" questions: either a GRTS Cell ID or latitude/longitude to locate the survey, a Site Name to describe the place, survey start and end times, and the names of surveyors. Each survey type may also require a few additional fields. If required columns are missing entirely, the upload wizard will block the file. If required columns are present but individual rows lack values, those rows will be flagged while the rest of the file can load. Use the template's informational header rows to identify which fields are required and ensure each data entry row contains values for these fields before uploading.

Rename Acoustic Files Transpose Colony Counts from Columns to Rows Generate Timestamps from AnaBat Filenames R Code for Mobile Transects: Auto Assign GRTS Cell to Recordings NABat R Package

BACKGROUND Scientists, resource managers, and bat-enthusiasts have been concerned about the future of bat populations for decades. NABat was designed to unify this continental community to collaboratively monitor bats, assemble data in a centralized database, and deliver status and trends for one of North America's critical resources -- BATS! Bats are Amazing Photo: Roxanne Pourshoustari Bats make up the second largest order of mammals, Chiroptera, and comprise one-fifth of all mammalian species. They perform numerous ecosystem services like insect pest control and plant pollination, and provide enormous economic benefits through ecotourism, medical research, and novel biotechnologies. Learn More Monitoring Need Photo: Jordi Segers There are 47 bat species in the U.S. and Canada, more than half of which are of current conservation concern. Eight are listed as federally endangered. Despite the importance of bats and growing concern about their status, prior to 2015 there was no program to conduct standardized monitoring of bat species across multiple taxa in North America. Bats are notoriously difficult to monitor adding to the need for a coordinated effort. Learn More Spread of WNS Photo: U.S. Fish and Wildlife Service White-nose syndrome (WNS), an emerging fungal disease, was discovered in North America in the winter of 2006. The rapid spread of the disease and associated mortality further prioritized the need to understand population trends. Subsequently the U.S. WNS National Response Plan (2011) and the WNS Implementation Plan (2014) identified the need for a national framework to model and monitor bat populations. Members of the WNS Response Team's Conservation and Recovery working group developed A Plan for the North American Bat Monitoring Program . Learn More Multiple Threats Photo: Paul Cryan It was evident among members of the bat research and management community that they were tackling similar issues. Because factors like WNS and wind turbines affect bat populations across political borders, it was determined that a comprehensive bat monitoring program for all species shared among the United States, Canada, and Mexico was required. By monitoring population and distribution trends across North America, NABat will not only provide information about the impacts of WNS, but also inform land managers and policymakers about the impacts of wind energy development, climate change, habitat loss, and other unanticipated threats that may arise in the future. Learn More