March 2022 changelog

Refreshed import experience for geofences and beacons

We’ve added a new import experience to make it easy to upload and update both geofences and beacons from CSV files.

Import geofences modal

  • Importing for geofences and beacons have a new modal experience. In the new import modal you can drag-and-drop upload, see our sample csv format, or download a sample to use as a template. Once you select import, your import job kicks off and you’ll receive an email on completion.
  • Imports have a new, flexible structure. Now only 6 import fields are required. You can read more about import requirements in our docs.
  • Imports now continue after any import errors. Rather than stopping on the first error, imports now continue and show a full record of creations, updates, and failures.
  • Exports include headers to simplify flows that start new imports from previous exports. This can be a common workflow to view all geofence changes on a single file and bulk upsert (creating new items when no existing matches exist and updating existing items with changes to a given row).

Import histories for geofences and beacons

With hundreds or even thousands of rows of data in an import, there are bound to be errors at times and it can be difficult to know what happened on import. We’ve added an import history to help you figure out what was newly created, updated, or resulted in an error.

Geofence import history

  • History and logs are now available for every import. You can now see geofence and beacon import histories along with logs for each item in an import.
  • Imports trigger email notifications that link back to the import history. For every new import, the person who triggered an import will receive an email to access the full import logs.

Locations now available in Radar dashboard

Location updates are the core context type in Radar and are generated by every track event. Making sense of the sheer number of location events can be difficult, and the Locations page makes it a bit easier by showing the most recent updates for debugging.

You can also visualize your locations data with a new charting view that supports flexible filters and aggregations to analyze your full history of location data available in Radar. For example, this can help you understand the number of location events you’re processing by device type or device OS. In the future, you’ll see this flexible charting pattern showing up on more pages in the dashboard.

Locations page

  • Locations view now available to debug and analyze location updates. You can now view location data in table and chart form from the dashboard. In the table view you can analyze the most recent location events that have come in which can be useful in test modes, while the charting view lets you group and filter all location data you have available.
  • Locations can be grouped, filtered, and aggregated with a new charting experience. Location updates can be analyzed with a new visualization experience that will be coming soon to additional context type views.

Adjustable map views

Map views are now adjustable so you can view even more map or even more table, depending on your preference.

Resizable map sections

Integration with Amazon Web Services S3 available in beta

If you want to do a deep analysis of location and events data, you may want it available in a S3 bucket that’s readily accessible to multiple developers or data scientists in your organization. You can now stream your location and event data to your own S3 bucket via Kinesis Data Firehose using Radar’s beta integration.

To learn more about our AWS S3 integration, check out the docs. To set up this integration while in beta, contact your Radar account manager.

Updated ETAs and distances

A significant update was made to improve ETA calculations and distances by updating Radar’s understanding of road networks and potential routes. As a result, ETAs and distance calculations will now be more accurate when using Trips.