A study site in Wildbook (also called an Encounter's "location ID") is a fixed value that represents a specific area where wildlife data is collected. A study site is one of Wildbook's three "where" data fields, which also include the more exact GPS coordinates (exact positioning) and the less exact verbatim locality (simply called "location"). Study sites defined in Wildbook can be used to search and filter data, define location-specific permissions, and filter computer vision matching to only likely or realistic resighting locations.
In this example, "Maldives" is the location ID for this reported Encounter. Location IDs can be as large as oceans or continents and as small as specific SCUBA diving buoys. The base definition of a study site is a location that you repeatedly visit to observe wildlife.
When you report an Encounter, you can set its location ID directly. Location IDs are hierarchical and nested, allowing for regional organization.
An important aspect of setting a location ID on an Encounter submission is that the location ID will be used to filter automatic matching to only that study site and species. If you wish to match against the entire Flukebook catalog or other study sites (such as regional study sites nearby), you can start a manual match from the Encounter, which allows you to multi-select location IDs to match an Annotation against, as shown below.
Assigning your Encounters to the correct location IDs will ensure your data is easy to find and that computer vision matching can be filtered to a specific site and other logical sites in the region. Avoiding global photo ID matching for a species and excluding implausible movement can help improve matching accuracy by removing potential false positives in the match results.
To add a new study site, you'll need to contact your Wildbook's administrator or make the request at the Wildbook Community. Location IDs are added to a file in Wildbook named locationID.json. Each location ID is defined in the JSON format as follows:
and can be nested.
The fields are used as follows:
- name - the descriptive, human-readable name of the study site
- id - the value of the study site to store in the "ENCOUNTER" table of the Wildbook database in the "LOCATIONID" column. This value must be unique in locationID.json
- locationID - a JSON array of other location IDs that are nested and logical subsites of this location
- prefix(optional) - an abbreviation to the study site that can optionally be used to name new individuals when an incremental naming system is desired (e.g., "Ice-0001", "Ice-0002", "Ice-0003", etc.)
- prefixDigitPadding (optional) - the number of orders of magnitude that you expect with the (optional) incremental individual naming system. For instance, picking
"prefixDigitPadding": 5(instead of 4 as in the example above) would result in individual names such as "Ice-00001", "Ice-00002", "Ice-00003", etc. (note the additional 0).
- defaultLatitude (optional) - if there are no explicitly designated GPS coordinates for a particular encounter, the locationID can be used to designate a default latitude when exporting encounter search results using the "Exported Excel spreadsheet (.xls) file in OBIS format with locale inclusion for unreported GPS" option.
- defaultLongitude (optional) - if there are no explicitly designated GPS coordinates for a particular encounter, the locationID can be used to designate a default longitude when exporting encounter search results using the "Exported Excel spreadsheet (.xls) file in OBIS format with locale inclusion for unreported GPS" option.
Restart Tomcat after making changes.