Skip to main content

Release Notes


Dec. 16, 2020

  • NEW A 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.

Dec. 14, 2020

  • IMPROVED The sideOfStreetAdherence parameter in Routing APIs has been updated so if it is set to “Off” for an individual stop, that stop setting will override any global side-of-street setting for the entire trip.

  • IMPROVED The Reverse Geocoding API’s units parameter can now be set to “2” - Regional to automatically return posted road speed limits in MPH or KPH depending on the country of the geocoded location.

  • IMPROVED A new parameter, IncludeRoadClass, can be added to POST calls for Route Reports. If set to true, the road class will be returned in Detailed and Directions reports.

  • IMPROVED A new parameter, useCrossStreetTurnAvoidance, has been added to the route options for Routing APIs. When set to true, it reduces the chances the route generated includes turns that go across the street in front of oncoming traffic. These turns will still be included if there is no reasonable alternative. (For auto and van Vehicle Routing Profiles only)

  • IMPROVED A new parameter in the Time Window Routing API, ApplyStopLocalTimeZones, can be set to “False” if you would like to force all time windows to behave as if they were in the same time zone. By default, the Time Window Routing API automatically adjusts time windows, ETAs and ETDs to account for a stop’s local time zone.

  • IMPROVED Multiple geocoding improvements were made for individual locations in North America and Europe.

  • FIXED Fixed an issue that could cause a route to be run when the lon/lat for a stop was incorrectly placed over a body of water.

  • FIXED Fixed an issue that could cause routes generated in Sweden to include ferry mileage when the ferryDiscourage parameter is set to true.

  • FIXED Fixed the translation of warnings in reports.

  • FIXED Fixed the Time Window Routing API so that the HighwayOnly parameter is always set to false.

Dec. 1, 2020

  • IMPROVED The following enhancements were made to the Single Search Geocoding service:

    • You can now search for nearby POIs without a query text string. For example:,40.288822&poiCategories=Hotel+or+Motel would search for hotels and motels near those GPS coordinates.

    • Improved handling of searches that include misspelled words

    • Updated to 2020 Q3 data in Europe

    • Updated to PC*Miler 34 Worldwide data

Nov. 5, 2020

  • IMPROVED Multiple improvements have been made to the speed limit data returned by the Reverse Geocoding API. (Requires Posted Speed Limit Add-on License) They include:

    • Updates of Trimble Maps link-based road speeds in North America
    • Updates of road speed data provided by HERE in North America and Europe
    • Improved accuracy and deprecated unnecessary parameters

  • IMPROVED Improved caching of Avoid/Favor sets for faster response times.

  • IMPROVED Improved the ability of our Routing APIs to dynamically select the active HOS rule (U.S. or Canada) based on the location of stops.

Oct. 21, 2020

The following updates were made to the Single Search Geocoding API:

  • NEW More than 104 million point addresses have been added to the Single Search map data in the United States. Point addressing assigns GPS coordinates to each street address, which can improve routing accuracy in both densely populated areas and rural areas where addresses are unevenly spread out along a road.

  • IMPROVED Updated to 2020 Q3.1 data in North America.

Oct. 21, 2020

The following updates were made in the Trip Management APIs:

  • IMPROVED For rest stops, the EarliestArrivalTime is now set by default to 1 hour before the CurrentETA, and LatestArrivalTime is set to 1 later than the CurrentETA.

  • FIXED Fixed an issue that could cause ETAs to be re-calculated using old GPS pings.

  • FIXED Fixed an issue that was preventing earliest and latest arrival times from being retained when the Modify Trip API is called.

Oct. 20, 2020

  • IMPROVED Updated to PC*Miler 34 Worldwide data

  • FIXED Fixed Hours of Service (HOS) time tracking to include rest stop dwell time in our calculations when a user inputs their own stop with off-duty time.

  • FIXED Fixed an issue that could cause an invalid time at the first stop (the route’s origin) when the departure time was set to within 15 minutes of the current Eastern Standard Time in our Routing APIs.

Oct. 7, 2020

The following updates were made in the Trip Management APIs:

  • IMPROVED If 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 actualArrivalTime, plannedDepartureTime, or a GPS ping timestamp.

  • FIXED Fixed 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).

Oct. 1, 2020

  • IMPROVED The weather radar coverage area for our JavaScript maps and Mapping APIs has been expanded to show more detail in regions throughout the world.

Sept. 24, 2020

  • IMPROVED The number of stops that can be entered and optimized using our Time Window Routing API has been increased to 500.

  • IMPROVED Our Derived Route API can now take into account map edits from MapExact, a licensed web tool that allows you to make custom edits to our map data to suit your company’s needs.

  • FIXED Fixed an issue that could cause our Routing APIs to fail when requesting Hours of Service rest stops on routes along the border of Mexico.

June 25, 2020

  • NEW Our annual version release incorporates the latest map data as well as routing, location and mapping API enhancements that have been made throughout the year. Highlights for version 34 of PC*Miler Web Services, include:

    • Better handling of “no through traffic” roads to prevent a circuitous route to reach a destination, while also avoiding these roads as a cut through.
    • A new sub-local road class in the map data for parking lot roads, park roads, alleyways, etc. Routing onto these roads is restricted, which prevents PC*Miler from using these roads as a cut through.
    • Updated commercial vehicle specific data, including:
      • Improved street-level map data, including weight limits, vertical clearances and truck through-travel restrictions. - Newly constructed roads and exit interchanges.
      • Improved city and ZIP/Postal Code placement and alignment.
      • Improved geocoding to better match an address to its actual “ground truth” latitude/longitude point.
      • Reducing the number of duplicate addresses.
      • Thousands of customer-recommended map improvements submitted via MapSure, our easy-to-use, online map reporting tool—directly into map data.
      • Updated toll data in California, Colorado, Florida, Georgia, Illinois, Indiana, Kentucky, Maryland, New Hampshire, New Jersey, North Carolina, Ohio, Ontario, Oregon, Pennsylvania, Prince Edward Island, Quebec, Rhode Island, South Carolina, Texas, Vermont, Virginia, Washington.
      • Improved road speed data used to calculate ETA and ETT in Montana.

  • IMPROVED PC*Miler 34 includes access to data about tens of thousands of additional commercial locations across North America that serve the transportation industry. Called “Places,” these locations range from distribution centers and manufacturing facilities to truck stops and rest areas. Places help you visualize an entire site on the map, such as a manufacturing plant, and they include additional details such as specific truck entrances and exits for more precise last-mile routing. Details about Places can be called using our Places API.

  • NEW A PlaceId can be entered as a stop in our Route Path and Route Reports APIs. If PlaceId is included, other location attributes included in the request are ignored, including an address or coordinates. The PlaceId for a location can be retrieved using our Places API.

  • NEW An ID can now be included for each stop in our Route Reports and RouteSync APIs.

  • NEW Two new toll discount programs, EZPass-MD and EZPass-ME, have been added to PC*Miler for use in toll cost calculation.

June 16, 2020

  • IMPROVED The following enhancements were made to our Single Search Geocoding service:
    • Updated to 2020 Q1 data in Europe.
    • Added Truck Stop as a filter in poiCategories.
    • Improved handling of missing spaces within a search query.

June 5, 2020

  • NEW A Route Path Report has been added to our Route Reports API. The report retrieves a series of geographic coordinates that make up a route. To call this report, you must be licensed to use our JavaScript Maps.

June 4, 2020

  • NEW A new parameter, FinalStopIsEndDepot, was added to our Time Window Routing API. It allows you to choose whether the final stop in the time window stop list should be treated as a fixed end depot or as another delivery stop.

June 1, 2020

May 27, 2020

  • NEW Our Places API can now retrieve Facility Information, if it is available for a given location. This information includes things such as the Place’s fuel options, parking information, amenities, and repair services.

May 20, 2020

  • NEW New parameters were added to our Routing and Mapping APIs that allow you to:

    • Choose whether toll roads should be avoided when generating a route. Options for the new tollRoads parameter include use, avoid if possible, and always avoid.

    • Apply multiple hazmat types and tunnel categories (Europe only) when generating a route. The new hazMatTypes parameter can accept an array of hazmat values, and tunnelCategories can accept an array of tunnel categories.

    • Choose to avoid or favor specific states or countries when generating a route. The new parameters are: avoidCountry, avoidState, favorCountry, and favorState.

    • Pass in an ID to uniquely identify assets in each routing call using a new assetId parameter.

  • NEW If a stop’s coordinates fall within a location that is part of the Trimble Maps Places database, and that Place includes hours of operation, Route Reports now return a warning if the ETA for reaching that location is outside of its operating hours.

  • IMPROVED The POIs Along the Route API now excludes POIs that are closed due to COVID-19.

  • IMPROVED The Time Window Routing API now better organizes twin stops in a more logical order. Twin stops are two or more stops with the same exact lat/long but different house or apartment numbers.

  • IMPROVED The emiType parameter used in Toll Detail Reports in Europe supports two additional emissions types: EURO 0 and EURO EEV.

  • IMPROVED A SideOfStreetAdherence level can now be added to each Stop object (StopLocation) in POST or SOAP requests to the Route Path, Route Reports and RouteSync APIs.

  • IMPROVED Geocoding was improved to find better matches for roads with fractional number names (i.e. Road 13.5 NW), road links with no postal code, and batch geocodes.

  • FIXED Fixed an issue that could cause an incorrect geocoding result when a ZIP code is entered without the leading “0.”

  • FIXED Fixed an issue that was causing the inclFerryDist parameter setting to be ignored in CalcMiles reports.

April 9, 2020

  • IMPROVED A new endpoint, /updatedplaces, has been added to the Places API to allow users who store location information locally to check whether a Place has recently been updated.

April 8, 2020

  • IMPROVED Hours of Service reports will not include rest stops in the U.S. that are known to be closed due to COVID-19.

  • NEW Updated to 2020 Q1-A data in Europe.

  • IMPROVED Trips will not include HOS rest stops in the U.S. that are known to be closed due to COVID-19.

March 16, 2020

  • IMPROVED Reverse geocoding will now return intersecting street names when a lat/lon is at or near an intersection.

March 10, 2020

  • NEW Updated to 2020 Q1 data in North America.

  • NEW The following enhancements were made to our Single Search and Reverse Geocoding services:

    • A new parameter, includeTrimblePlaceIds, allows you set whether search should return the TrimblePlaceId for a location, if one exists. Trimble Maps maintains an ever-growing Places database that includes tens of thousands of commercial locations across North America that serve the transportation industry. Places provide additional information about a location—ranging from entry and exit gates to site hours—that can be called using our new Places API.

      Every location in the Places database is identified by a unique TrimblePlaceId. That ID ensures you receive the exact same information about a Place—address, contact information, etc.—regardless of whether you are calling the Places API from your transportation management system (TMS) or accounting software.

      In Single Search, TrimblePlaceId is returned as a separate field, while Reverse Geocoding returns it within a field titled PlaceName.

    • Single Search geocoding in Europe has been enhanced using point addressing. Point addressing assigns GPS coordinates to each street address, which can improve routing accuracy—especially in densely populated urban areas.

Feb. 20, 2020

  • IMPROVED Multiple enhancements were made to the Time Window Routing API, including:

    • A new DeliveryType parameter that allows you to identify whether the stop is a delivery or a pickup. The value is used to better cluster together deliveries and pickups—ideally to make deliveries first and complete pickups after all deliveries are made.
    • Better support of stop locations that contain postal codes.
    • Improved break time calculations.
    • General performance improvements, including the use of live traffic closures in route calculations. (Account must be licensed for traffic.)
  • IMPROVED Tunnel categories used for hazardous materials routing are now automatically identified based on the worldwide region.

  • IMPROVED Geocoding of intersections as well as geocoding of addresses with a directional component (North, South, East, West) has been enhanced.

  • IMPROVED The TollDistance field is no longer returned in toll reports for Europe if the toll system is not distance-based.

  • IMPROVED Geocoding was improved in the Netherlands.

  • IMPROVED Traffic map tiles can now show traffic up to a map zoom level of 20.

  • IMPROVED Traffic incidents map tiles now show more real-time incidents and provide better translations in Europe.

  • FIXED Fixed an issue where incorrect Point of Interest (POI) data was being returned in certain cases.

  • FIXED Fixed an issue in the Time Window Routing API that prevented a stop from properly being removed when it has a later start time than end time.

  • FIXED Fixed an issue that could cause the Time Window Routing API to return different results when the same stops are passed in a different order.

January 13, 2020

The following updates were made to the Trip Management APIs:

  • NEW A new externalOrderIds field has been added, allowing you to include a list of orders associated with a trip.

  • IMPROVED The tripStatus field is now marked as InProgress once the first GPS position is received for the trip.

  • IMPROVED The Get Route Path API can now be used for trips with the initial tripStatus of Planned, in addition to trips that are InProgress or Completed.

Jan. 8, 2020

  • NEW Updated to 2019 Q4 data in Europe.

  • IMPROVED ETA calculations were improved when no traffic information is being used for routes in Europe.

  • FIXED Fixed an issue that could cause a geocoding error if a route number is included in addition to the local street name.

  • FIXED Toll costs were added for the Liefkenshoektunnel between Antwerp and Beveren in Belgium.

Last updated June 7, 2024.
API Endpoint: