Receiving data from Movebank

Website: https://www.movebank.org/cms/movebank-main

Integration Requires Assistance

⚠️ Work in Progress ⚠️

This integration requires assistance from our support team for setup and configuration. Please contact our support team at support@earthranger.com and we’ll guide you through the process to ensure everything is set up correctly.

We are actively working to make this integration self-service in the future. Stay tuned for updates!

Prerequisites

Data Source

  • Movebank study with tags.
    • Share the list of Study IDs with Support
  • Unless the study is public, share that study with EarthRanger’s Movebank user EarthRanger_Integrations. 
    • Share as the study with this user as a 'Collaborator'.

Data Delivery

  Credentials or an authentication token to access the delivery system.

Configuration

Notes for Support (click to expand)

Important

Create one inbound configuration per study ID.

 

Go to Gundi v1.

Go to the Inbound Integrations and select Add Integration.

Follow the steps below to configure the integration.

Name: Enter a suitable name (e.g., "Sitename - Movebank - StudyID")

Owner:  Select the integration's owner

Type: Movebank

Provider Key:  Leave empty. Gundi will automatically give it a name.

Default Device Group: Leave empty. Gundi will automatically create a default group.

Endpoint:  https://www.movebank.org/movebank/service/direct-read 

Token:  Leave empty

Login/Password:  EarthRanger_Integrations and its password. See 1Password.

State:   

{
 "maximum_lookback_hours": 24,
 "studies": [
   {
     "id": "StudyID",
     "name": ""
   }
 ]
}

Example:

{
 "maximum_lookback_hours": 24,
 "studies": [
   {
     "id": "1345147839",
     "name": ""
   }
 ]
}

Click Save

Configure the Default Device Group to select the destination site. 

 
 

Data Pull Frequency

 

Characteristics

  •  

Internal Documentation

https://allenai.atlassian.net/wiki/spaces/ER/pages/20296925226/Movebank+Gundi

 
 

Data Delivery

The time it takes for data to appear in your destination system depends on several factors, such as latency introduced by the source, network conditions, and intermediary systems. While these factors may vary, Gundi typically checks for available data at scheduled intervals (approximately every 10 minutes).

If data is not available in your system after this interval, please check the source of the data for its availability. If the issue persists, contact our Support team for assistance.

Tags: Animal Tracking, Movement Data, Gundi v1, Pull Integration, Data Provider
Last Update: March 5, 2025