Introducing Geofenced Triggers

You can now setup a geofenced trigger for a data stream containing latitude/longitude coordinates. Whenever an asset enters or leaves the programmed geofence, set by a latitude/longitude coordinate center plus a specified radius, a trigger action will fire. This post goes through a step-by-step example of setting up a geofence and testing trigger alerts by sending location data through URL parameters. Step 1: Create a Data Bucket Click the +Cloud icon in the bucket shelf to create a new, empty data bucket. Step 2: Configure Endpoint Keys (optional) Two keys are needed to stream data into this new data bucket, the bucket key that you choose (or use the one generated for you) and your access key. Click the “Configure Endpoint Keys” checkbox to set these keys. Step 3: Get the API Endpoint URL After the bucket has been created, click on the settings link under the data bucket name on the bucket shelf. The API endpoint URL is located in the data tab. The URL will look something like this but with the bucketKey and accessKey you chose in Step 2: https://groker.initialstate.com/api/events?accessKey=8aqrx5GmVoCSCvh9ojV18boUHy5C3SUa&bucketKey=8EUT6VF3KMPD Step 4: Get a Valid Latitude/Longitude Coordinate Go to Google Maps (or the map of your choice) and search for …
The post Introducing Geofenced Triggers appeared first on .

Thanks to Initialstate.com for these Posts and details

The post Introducing Geofenced Triggers appeared first on Technology.

Leave a Reply

Your email address will not be published. Required fields are marked *