Our users want to keep track of consumption and control their costs, of course. We were asked for precise data of used loadings. In the analytics section of each of your events, you can now access all hourly loadings.

The syntax of the URL uses the eventID and the start- and the end time: 

*/api/events/eventID/pageviews?startTime=2021-08-21T04:15:00.000Z&endTime=2021-08-31T23:59:59.999Z 

We published an add-on, you will love to monitor live tracking during your races. You can now work with our monitor. This dashboard summarizes relevant information for security and is the perfect copilot for organizing your race.

• battery state 
• alerts 
• network reception 
• GPS fix 
• last known location 
• non-movement 
• leaving the track and much more. 

Check the sample of a past event: https://racemap.com/monitor/5a535fdf787fe25ece1a0cc8

You can now adjust the size of geofences for virtual detections. Just provide the needed value in meters in the data feed settings of your event.

More about our API for reads and detections: https://docs.racemap.com/data-api/times

New feature in the Tracker Management. You can now delete commands which have not been sent from the queue. Such as if an old "Shut down" command is on hold, you can prevent sending this command to the tracker before switching on.

Tracker Management >> specific GPS unit >> Send Command

Our data feeds are used for 3rd party applications such as timing software. We improved the data feed for specific timekeeping points and added two parameters

• name of timekeeping in Racemap and 
• distance in m of the detection from geolocation of timekeeping point

All information about */times/id data feed in our documentation https://docs.racemap.com/data-api/times#reads-at-specific-virtual-timekeeping-point

We improved to match the entries in your participant list with selected devices from your tracker management.

Import or sync the participant list of your event from your online registration for example with the generic API (https://docs.racemap.com/api-import-and-export-data/import-basics/metadata-api).

In your tracker management https://racemap.com/admin/trackers

1. Select GPS trackers to use for live tracking
2. Add these devices to an event
3. Select from your event list

The GPS units are added automatically to the participants in your event. The participant list shows the device name from tracker management, also.

Corresponding to this process there is no need for CSV files to update the participant list, anymore.

We were asked for the option of other maps than from mapbox. You can now paste the URL of the external map source for your tracking map. Open the dialogue in the map editor under external layers. 

Select the source to provide for your single map, group- and stage event from your custom app(s).

Basic >> Other Settings >> Maintenance

Some users like to show their contact information, that way participants reach out to the support team easily. In "event logo and description" you can now provide the website and the contact email for each event, separately. These parameters are shown in the info of the corresponding tracking map. 

Users customize their race visualization and virtual timing in the map editor. We developed several enhancements to work more efficiently. 

Now you can add the point of interest (POI) property to a split, directly. Define name and color respectively the icon to be visualized at the location of the split.

You can center the map editor around the location of your device.