The Samdesk feed in ArcGIS Velocity connects to the Samdesk API to ingest real-time crisis and event alerts from the Samdesk global event detection platform. Samdesk monitors social media, news, and other open sources to find emerging incidents, such as natural disasters, threats, fires, and other public safety events in one or more geographic locations.
Examples
The following are example use cases for the feed:
- A public safety agency uses the Samdesk feed to monitor emerging incidents in real time, so emergency operations centers can triage and dispatch resources as events unfold.
- A logistics and supply-chain operator uses the Samdesk feed to detect disruptions near ports, distribution centers, and transit corridors.
- A defense or intelligence agency uses the Samdesk feed to maintain country- and region-level situational awareness of global events.
- A risk and insurance analyst uses the Samdesk feed to track incidents that may impact insured assets and areas of interest.
Usage notes
Note the following when working with the feed:
- Samdesk uses the API key generated during feed configuration and the feed item’s URL to push data to the feed. Store the API key for later reference. If the key is misplaced, generate a new API key in the feed configuration, and provide the new one to Samdesk.
- Each Samdesk feed must use a unique API key.
- You must obtain the Search Stream ID parameter value from Samdesk to configure the feed.
- Velocity automatically handles the data schema. Adding new fields is not supported because the schema is predetermined by Samdesk. You can remove or rename existing fields.
- The Samdesk data is in JSON format, and the Location parameter is handled automatically when identifying key fields.
- Velocity automatically handles the key field parameters for the Date and time and Tracking sections. The Start time parameter is set as event_time, and the Track ID parameter is set as event_id.
- Velocity automatically constructs point geometry from each alert location’s lat and lng fields.
- The minimum polling interval in Velocity is five seconds.
- The Samdesk default API rate limit is five requests per minute, per account. Polling intervals faster than approximately 12 seconds or running multiple Samdesk feeds using the same API key, may exceed this limit. Contact Samdesk to request a higher rate limit for your account if needed.
Parameters
The following are the parameters for the feed:
| Parameters | Description | Data type |
|---|---|---|
| API version (required) | Select the Samdesk API version used for this connection. Currently, only version 1 is supported. | API version number |
| API Key (required) | The API key used to authenticate requests to the Samdesk API. An example is https://api.samdesk.io/1/search_streams/{SEARCH_STREAM_ID}/alerts?api_key={API_KEY}. Click the Generate API Key option to generate an API key for the feed. Provide the API key and the feed item’s URL to Samdesk to start receiving data. | Samdesk format type |
| Search Stream ID (required) | A unique identifier for a Samdesk search stream. A search stream stores keywords, areas of interest, event types, topics, severity thresholds, and tags used to determine which events generate alerts. Sign in to the Samdesk dashboard to locate the ID of the search stream you want to poll. | String |
| Additional logging (optional) | Specify whether to log raw HTTP requests and responses issued by Velocity to Samdesk. Note:Turn this parameter on for troubleshooting purposes and turn it off when troubleshooting is complete. After turning it on, start the feed; the debug-level logs are available on the feed logs page. Contact Esri Technical Support for help with troubleshooting if necessary | Boolean |