Trip Management Release Notes
Feb. 18, 2021 #
IMPROVEDOut of Corridor events are now returned with the timestamp of the GPS ping that triggered the event. The date and time are returned in the
Jan. 20, 2021 #
IMPROVEDYou can now edit via API key the radius around your stops that will automatically trigger an
DepartedStopevent and update the stop status in the trip. The default radius is 0.5 miles. Contact to edit that radius.
Jan. 11, 2021 #
IMPROVEDA time window will be assigned to any HOS stop automatically added by the Trip Management service so you can get ETA event notifications to let you know whether a driver may be late to a rest stop. The time window will automatically set the fields
latestArrivalTimeto 15 minutes before and 15 minutes after the HOS stop’s planned ETA.
IMPROVEDThe Get Trip Notifications API can now return stop event updates from a trip. A stop event notification is created whenever there is an update of a stop status to “Arrived” or “Departed,” whether or not the stop status change is automatic or manual.
Dec. 16, 2020 #
NEWA new Trip Settings API allows you to get or set specific values, such as event notification thresholds, for an individual trip. For the specified trip, these settings override the default API key settings that were selected at the time the API key was created.
Oct. 21, 2020 #
IMPROVEDFor rest stops, the
EarliestArrivalTimeis now set by default to 1 hour before the
LatestArrivalTimeis set to 1 later than the
FIXEDFixed an issue that could cause ETAs to be re-calculated using old GPS pings.
FIXEDFixed an issue that was preventing earliest and latest arrival times from being retained when the Modify Trip API is called.
Oct. 7, 2020 #
IMPROVEDIf a vehicle is “Arrived” at a stop, the Recalculate Trip API will use the most recent time available to recalculate the trip’s ETA—whether it’s the
plannedDepartureTime, or a GPS ping time stamp.
FIXEDFixed a bug in which GPS pings weren’t being considered in ETA calculation if they were reported and the Recalculate Trip API was called in direct succession (less than 5 milliseconds).
April 8, 2020 #
IMPROVEDTrips will not include HOS rest stops in the U.S. that are known to be closed due to COVID-19.
January 13, 2020 #
externalOrderIdsfield has been added, allowing you to include a list of orders associated with a trip.
tripStatusfield is now marked as
InProgressonce the first GPS position is received for the trip.
IMPROVEDThe Get Route Path API can now be used for trips with the initial
Planned, in addition to trips that are
October 28, 2019 #
NEWA new Auto-Arrive/Depart feature will automatically mark stops in a trip as “Arrived” or “Departed” by comparing a vehicle’s GPS position with either:
A Site perimeter polygon, if one exists for that stop. That includes polygons created by Trimble MAPS for truck stops, distribution centers, etc., as well as Custom Place Site polygons that you have created in ContentTools.
An air distance of 0.5 miles from a stop. Within that distance a stop will be marked as “Arrived.” Outside of that distance it will be marked as “Departed.”
In the past, users had to enter these stop status changes manually. A notification will also be created for every stop status change. The Auto-Arrive/Depart feature and related notifications are on by default and can be turned off by request.
October 10, 2019 #
IMPROVEDNew API endpoints have been added that allow you to call or modify trip information using either the ALK Trip ID returned when you planned the trip or the TMS Trip ID in your planning system.
July 16, 2019 #
IMPROVEDThe Hours of Service (HOS) features for our Trip Management APIs have been updated to now take into account:
HOS rules in the U.S. and Canada during trips that cross the border.
HOS compliance when team driving with two drivers.