Skip to main content

Release Notes

Contents

Nov. 13, 2024

Oct. 12, 2024

  • FIXED Fixed the consolidation logic in the Multi-Vehicle Routing API. Consolidation is determined by the config > consolidation > consolidateBy setting. The possible consolidateBy values are:

    • none - Consolidation will not occur. (This is the default value.)
    • addressOnly - Consolidation occurs during loading when stops with the same latitude/longitude, EQCode, time window and other parameters match even if the accountID does not match.
    • addressandAccount - Consolidation occurs during loading when stops with the same latitude/longitude, EQcode, time window an

    Note: An unloaded stop will not consolidate with a loaded stop during load or optimize. The stop must be moved using the MOVE call to a sequence next to a loaded stop to consolidate them.

Oct. 10, 2024

  • IMPROVED You can now add a StopType to identify special types of stops when requesting an Hours of Service (HOS) report. The two options are: Waypoint and BorderCrossing. A Waypoint modifies the route path so it passes through a specified point, without acting as a full stop for a pickup, a delivery, or a rest break. A BorderCrossing is an international border crossing.

Sept. 12, 2024

  • IMPROVED A PreferredSearchTypes object was added to the HoSOptions used in Hours of Service (HOS) reports. PreferredSearchTypes specifies a driver’s preferred POI types (Rest Area, Parking Lot, LCV Lot, etc.) for HOS-required rest breaks, based on break type (LongBreakType or ShortBreakType). Each break type includes an array of preferred POI types in this format:
"PreferredSearchTypes": {
            "LongBreakType": [55,25],
            "ShortBreakType": [41,34]
}
  • IMPROVED Sites routing is no longer used when routing to a ZIP code or city without specifying an address.

  • IMPROVED Removed warnings from SOAP requests that could inadvertently cause users to believe there was a error. Only actual errors are now returned.

  • FIXED Fixed an issue where the dataset and dataVersion parameters would sometimes use different data for Route Reports even though they were passed with the same value.

Aug. 8, 2024

July 10, 2024

PC*Miler 38 Version Release Highlights of PC*Miler 38, the annual version release include:

  • IMPROVED With each new version, PC*Miler’s routing algorithm is enhanced to generate the best routes and the most accurate travel times and distances for your vehicles. Improvements since version 37 include:

    • Improved routing for 53-foot trailers: PC*Miler 38 includes enhancements that generate more direct (and sometimes shorter) routes for 53-foot trailers as the routing algorithm takes into account state-by-state exemptions to the requirement that 53-foot trailers be routed along the U.S. National Network. Read more about routing 53-foot trailers.
    • Estimated travel time (ETT) enhancement: The Trimble routing algorithm has been updated to provide more accurate estimated travel times (ETT).. To take advantage of this update, the dataVersion must be set to Current in routing calls. (Current is the default.)


  • IMPROVED Discount toll programs added Three new discount programs can be used in toll cost calculations:

    • V-Toll on the Ohio Turnpike.
    • The AVI sticker ticket system for Pharr International Bridge in Texas.
    • The Express Card program for Hammock Dunes Bridge in Florida.


  • IMPROVED Map data updates: Version 38 includes all of the road map data updates in North America starting at Q2.1 2023 and ending with Q2 2024. Some highlights include:

    • 345 new construction road projects were added
    • Over 32,700 new POIs were added to the Places Database
    • Over 27,600 new site locations were coded, including distribution centers, retail storefronts, manufacturing plant, and truck stops and service centers
    • More than 2,800 miles of new highway-level network was added to the United States
    • Truck through-travel restrictions were updated within over 1,000 city limits
    • More than 10,600 customer-reported issues were fixed

For more detail on map data updates, please see our North America map data release notes.

May 31, 2024

  • NEW The Trip Management service now supports appointment time windows. Time windows help improve ETA calculations in cases where there is a defined time an asset needs to arrive at a location. This feature also allows for the calculation of slack time, which denotes how much time (in hours and minutes) an asset will be earlier than the appointment time. To use this feature, appointment times need to be enabled at the API key level by reaching out to your account representative.

May 30, 2024

May 9, 2024

May 2, 2024

  • IMPROVED - Detailed and Hours of Service Route Reports now return a SlackTime field when your POST method request includes a time window for each stop using the EarliestArrivalTime and LatestArrivalTime parameters. SlackTime is the time in hours for how early you are expected to arrive at the stop, based on its time window. It assumes a departure time of right now unless you specify a departure day and time using the EstimatedTimeOptions object.

April 19, 2024

  • NEW Added a new endpoint to the Trip Management service that allows you to retrieve a URL that opens the trip in Trimble’s Trip Viewer.

April 16, 2024

  • IMPROVED Custom road speeds included as part of POST Route Report requests can now be specified as kph or mph based on the DistanceUnits option in your call. (Set to 0 for mph, or 1 for kph.) Contact us if you would like to set your account to always assume road speeds are in mph, regardless of the DistanceUnits setting.

  • IMPROVED Detailed Route Reports outside of North America now include the coordinates of border crossings when a route crosses an international border.

  • IMPROVED Customers licensed for global accounts can now select region specific Vehicle Routing Profiles using the profileName parameter in Routing API calls.

  • FIXED Fixed an issue in the Geocoding APIs where results were not returned when a ZIP code in Mexico was passed without also including a city.

March 21, 2024

March 7, 2024

  • NEW Appointment times for individual stops can now be included in POST method calls to Route Reports APIs. You can add appointment times with two new parameters in a stop location object, EarliestArrivalTime and LatestArrivalTime. Those times are used to used to help calculate the estimated time of arrival or departure for stops on a route.

Feb. 27, 2024

Feb. 7, 2024

Jan. 25, 2024

  • IMPROVED Added a new TimeInSeconds setting for POST Mileage Reports. When set to true, the THours and LHours response parameters are returned with seconds precision. By default, they are rounded to the nearest minute.
  • IMPROVED Updated the UseTraffic setting in Routing APIs so that when it is set to true, it overrides the optional useTraffic setting in a Vehicle Routing Profile.
  • FIXED Fixed time zones returned for certain regions to reflect daylight savings time.
  • FIXED Removed a warning message when using Avoids/Favors and a dataVersion of PCM30 and earlier.
  • FIXED Fixed version PCM26 so that an error is returned when an invalid postal code is submitted in POST Route Report requests.
  • IMPROVED The following updates were made to the Single Search Geocoding API:
    • Updated map data in Europe.
    • Improved support for full postcodes in Argentina.
    • Fixed issues related to the use of the “#” symbol in Place names.

Jan. 11, 2024

Last updated November 14, 2024.
API Endpoint:

Contents
Subscribe RSS