Website: https://www.wpswatch.org
Tags: Camera Trap, Push Integration, Data Provider
Prerequisites
Data Fetch
- wpsWatch Account
- All deployments for the site must have a location specified in wpsWatch
Data Delivery
EarthRanger
You will need:
- A special EarthRanger user with permissions to post event data.
- Please refer to EarthRanger's documentation or contact Support.
- A long-lived token for the special user.
- Please refer to EarthRanger's documentation or contact Support.
- Confirm that the required event types and schemas are configured in EarthRanger. Consult our references here.
TrapTagger
Coming Soon..
Configuration in Gundi
Click on Create Connection
Select “wpsWatch”
Select your Organization
Write a name for this connection under “Connection Name”
Click Next
Select a Destination. Please consult our guides
Next Steps
Navigate to your Connection
Copy the API Key from the Overview tab
Provide this API key to your WPS point of contact. This authentication key will help them complete the integration for you
WPS Staff will help you with the following actions:
- Make sure that all deployments have a location specified in wpsWatch.
- Edit the Integrations in the wpsWatch site to enable the Gundi integration with the URL and API Key.
- Update the alert configuration(s) in wpsWatch to send the alerts to Gundi.
- Validations.
Considerations
- The current scope does not include event updates, so if a photo is tagged with ‘animal’ in wpsWatch and sent to ER via Gundi, it will create the event with the animal tag, but if a ‘rhino’ tag is then added to the photo in wpsWatch, that tag won’t be added to the event in ER. This will be handled in future development.
- Cmore and TrapTagger are looking at integrating with Gundi, which would be other endpoints we’d route to. There is no timeline on Cmore, but we expect the TrapTagger integration to be available soon.
- The array of tags isn’t reportable in ER, so there’s a separate Tags field that contains a comma-delimited list of tags that can be used for reporting. It isn’t displayed in the UI for the event, but it is included in exports.
Data Delivery
The time it takes for data to appear in your destination system depends on multiple factors, including latency introduced by the original source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data on a scheduled interval of approximately 10 minutes.
If your data is not available in your destination after this interval, kindly refer to the source to review the availability of data, and contact our Support team for further assistance.
Need Help?
Contact Support
If you need help with Gundi, here are some resources to try.
Contact the Gundi team
Send an email to support@earthranger.com with your questions or a description of the issue you have been experiencing.
Help Us Improve Gundi
If you have comments, corrections or suggestions regarding our guides, website, or the Gundi portal, please contact us.
Feel free to explore our website for more contact information.
Last Update: Feb 28, 2025