Search Results

Back to Search ERROR WARNING: Location name is not unique and GRTS Cell ID or latitude and longitude were not provided. 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.

Back to Search ERROR WARNING: No GRTS Cell in this sample frame at this latitude and longitude 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 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 'GRTS 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'. 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'.

8d2c6646-52d8-4a64-901f-a3bc337b8d47 Photo credit: Audrey Holstead USFWS Next WNS & Listing Status Eptesicus fuscus Order : Chiroptera Suborder : Yangochiroptera Family : Vespertilionidae Call characteristics: Low frequency caller (~30 kHz range) Weight 1/2 - 3/4 oz (14 - 20 g) Body Length 3 3/8 - 5 3/8 in (8.7 - 13.8 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 Big Brown Bat Big brown bats are medium brown in color, with darker facial features and ears. Their small ears and eyes sit upon a blunt face. This bat can be seen in urban and suburban environments of mixed agricultural use. As generalists, the species can be at home among timberline meadows to lowland deserts, and abundant in deciduous forest areas. Big brown bats will roost in artificial structures, including buildings, bridges, and bat houses. When selecting for hibernation roosts, this species can tolerate hibernating in areas that experience very cold temperatures. Big brown bats have a preference for munching on beetles but will eat a variety of insects. Females can consume up to their body weight in insects in a single night. In the west half of this species' range, females have been found to produce a single pup (baby bat), whereas twins are more frequent in the east. 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: Latitude and longitude not in specified GRTS Cell 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 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 'GRTS 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'. 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: There already exists an entry for this species, for this observer, for this emergence event HOW TO RESOLVE: Duplicate errors occur when the system encounters repeated survey records. First determine whether duplicates are within the current file or span multiple uploads. For within-file duplicates, 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. For emergence counts specifically, group data by 'Site Name', 'Exit Identifier', 'Surveyor', and 'Species', then sum counts into a single row. If duplicates span multiple uploads, locate the conflicting file in the Partner Portal's Surveys tab, download it from Project Files, and compare contents with your current file. Keep the most complete version and remove overlapping rows from the other, then re-upload. If duplicates persist despite removing and re-uploading affected data, contact the NABat Technical Outreach Team. ADDED EXPLANATION: Duplicate detection logic 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.

Back to Search ERROR WARNING: Invalid option for Classifier --> [custom text] 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: line_interpolate_point: [custom text] 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: is an invalid boolean HOW TO RESOLVE: Use the template's second header row to view data type requirements and replace erroneous data in flagged field based on the field's listed requirements. Adjust cell formats or use find/replace to convert values to the correct type. Example: The "Microphone Weather Proofing" field in the stationary acoustic template allows for only "True" or "False" entries. If any other entry is included for this field, the "invalid boolean" warning will appear. If the "|" pipe symbol at the start of header row gets accidentally removed, those rows will no longer be treated as headers and instead will be read in as data rows. This results in categorical or data type errors like, " is an invalid boolean". Simply make sure a pipe symbol "|" is included at the start of each header row and re-upload your csv to the Partner Portal. 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.

579822fb-6332-4a38-bd46-208416277bdb Photo credit: Dane Smith USFWS Next WNS & Listing Status Myotis sodalis Order: Chiroptera Suborder: Yangochiroptera Family: Vespertilionidae Call characteristics: High frequency caller (~40 kHz range) Weight 1/8 - 3/8 oz (5 - 11 g) Body Length 2.75 - 3.6 in (7.1 - 9.1 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 Indiana Myotis The Indiana Myotis is a medium sized bat with longer ears and a short face. Its fur ranges from grayish to chestnut, with dull-lead colored fur at the base of the hairs and pinkish-cinnamon fur underneath the body. The Indiana Myotis diet includes a variety of aerial insects. During summer, the Indiana Myotis roosts beneath the exfoliating bark of dead trees, commonly known as snags. During winter, the species prefers to hibernate in cold sites, often limestone caves containing pools of water. The Indiana Myotis was one of the first bat species to be listed as endangered by the U.S. Fish and Wildlife Service. Despite measures to protect the species' winter hibernacula, populations continue to decline, due partly to its susceptibility to the fungal disease white-nose syndrome, which impacts winter populations, as well as threats like pesticide use and deforestation which limit suitable summer habitat. 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: is an invalid integer HOW TO RESOLVE: Use the template's second header row to view data type requirements and replace erroneous data in flagged field based on the field's listed requirements. Adjust cell formats or use find/replace to convert values to the correct type. Example: The "GRTS Cell Id" field in the stationary acoustic template accepts integer data. Non-integer data (e.g., string values or floats - numbers with decimals like 1.5) entered into this column will result in an error warning. If the "|" pipe symbol at the start of header row gets accidentally removed, those rows will no longer be treated as headers and instead will be read in as data rows. This results in categorical or data type errors like, " is an invalid integer". Simply make sure a pipe symbol "|" is included at the start of each header row and re-upload your csv to the Partner Portal. ADDED EXPLANATION: Each field in the template requires a particular data type (e.g., text, integer, string, date-time, or true/false) or a controlled categorical response. Values that don't match these data type requirements will be rejected. In a spreadsheet application, resolve by adjusting cell formats. Examples include, changing numbers stored as text into integer format, 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.

185712bc-0a92-4e67-868f-fd766d18d8c0 Photo credit: Andrea Schuhmann USFWS Next WNS & Listing Status Myotis septentrionalis Order: Chiroptera Suborder: Yangochiroptera Family: Vespertilionidae Call characteristics: High frequency caller (~40 kHz range) Weight 1/4 - 3/8 oz (6 - 9 g) Body Length 3 1/8 in (7.8 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 Northern Long-eared Myotis The northern long-eared Myotis has light brown fur on its back with paler gray fur on its underside. The face, ears, and membranes are dark. This species' ears are long compared to other bats in the Myotis genus and feature a characteristically sharp and pointed tragus. In the summer, the northern long-eared Myotis can be found in its more northern range, preferring dense forest stands. Roosts are primarily located in trees and buildings, with maternity roosts often found beneath the exfoliating bark of dead trees or within tree cavities. Winter roosts are typically located in small caves or crevices, such as underground mines. Typically, this species roosts alone or in small groups (about 20-60 females to a maternity roost). Moths constitute the primary diet of this species. The fungal pathogen white-nose syndrome, has caused population declines of up to 99% at hibernation sites. 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: Capture Time not within Start and End Times HOW TO RESOLVE: This survey window conflict occurs when a "Time of Observation" falls outside the reported "Survey Start Time" and "Survey End Time". To resolve, directly adjust start/end times of the survey event, or, manually adjust the "Time of Observation" of the errored record(s). If many records are affected, check for consistent time offsets or other systemic shifts, then resolve by batch-shifting times for uniform offsets, or extending survey window start/end times to include errored records. For non-acoustic surveys, errors usually stem from typos or rough estimates. Fix these manually or with simple {Find/Replace} tools.