Reference · built on requestConnectorFleet & telematics

Trimble Maps

Truck routing, geocoding, places and geofences, and trip management with ETAs and notifications from Trimble Maps.

About

Trimble Maps publishes RESTful web services built on PC*Miler: Routing, Location, Places, Mapping, Trip Management, Multi-Vehicle Routing, Fleet Configuration, Freight Rail, and Account Manager. Route Reports return mileage, directions, tolls, state distances, and weather alerts for a vehicle profile. Trip Management stores a trip under a Trip ID, recalculates ETAs from GPS positions, and raises Out of Route, ETA change, and weather notifications.

Through Fibric, an operator reads ETAs, trip notifications, and route reports, then proposes a new trip, a stop change, or a geofence for your approval. Approved changes are sent once and leave a receipt.

This is a reference listing. It documents what Fibric would read from Trimble Maps and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Route Reports such as Mileage, Detailed, Directions, State, TollDetail, HoursOfService, and WeatherAlerts through /route/routeReports
  • Trip details, ETAs per stop, and the route path through GET /trip/{tripId}, Get Route Path, and Get Route to Next Stop
  • Trip notifications for Out of Route events, ETA changes, and weather alerts through Get Trip Notifications
  • Single Search, Geocoding, and Reverse Geocoding results from https://singlesearch.alk.com and the Location APIs
  • Custom Places, Sites with gates, facility information, and dwell time through the Places API at https://api.trimblemaps.com/places/v1
  • Drivers, Vehicles, VehicleGroups, and DriverGroups through the Fleet Configuration API at https://fleets.trimblemaps.com/api/assets/v1

Proposed actions

  • Target capability: propose a planned trip with stops, dwell times, HOS breaks, and a Vehicle Routing Profile through POST /trip
  • Target capability: propose stop additions, removals, or changes through PUT /trip/modify, with ETAs recalculated
  • Target capability: propose a trip or stop status change through POST /trip/tripStatus and POST /trip/stopStatus
  • Target capability: propose a geofence set or a Site through the Geofences endpoints and the Places API
  • Target capability: propose a vehicle or driver record through the Fleet Configuration API, up to 50 per call

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Tell the receiver when the truck will arrive

    Trip Management recalculates ETAs as GPS positions arrive. When an ETA moves past the appointment window, the operator proposes a notice to the consignee and records the new time.

    With ETA Notice

  • Catch a driver off the planned route

    An Out of Route notification names the trip and stop. The operator checks the vehicle profile and the remaining stops and proposes a recalculated trip or a call to dispatch.

    With Route Deviation

  • Resequence stops for the vehicle

    Route Reports cost the same stops in a different order for a given truck profile. The operator proposes the sequence with the lowest miles and time, with the report attached.

    With Route Resequence

  • Hold a trip ahead of weather

    The WeatherAlerts report lists alerts along the route. The operator proposes a delayed departure or a modified trip and records the alert that drove it.

    With Weather Hold

Requirements

  • A Trimble Maps subscription and API key; a free trial key is available for a limited time
  • Add-on licensing for some APIs and data sets, arranged with a Trimble representative
  • Premium Web Services subscriber status for the Places API
  • Firewall rules that allow https://*.alk.com and https://*.trimblemaps.com
  • For Fleet Configuration, unique names and IDs for every vehicle, driver, and group in the account
Authentication
An API key from Trimble Maps sent in the Authorization header on POST requests, or as the authToken query parameter on GET requests; Trip Management accepts the API key for enterprise apps or a Single Sign-On token for consumer apps.

Limits

  • Route Reports accept up to 20 routes in a single POST call
  • Only trips marked InProgress receive event notifications
  • Fleet Configuration adds at most 50 vehicles or drivers per API call
  • Coverage is documented for the U.S., Canada, Mexico, and Europe; the TollDetail report applies to Europe

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Trimble Maps ↗

Questions and answers

How is an API key sent?
On POST requests, in the Authorization header. On GET requests, as the authToken query parameter. Trip Management takes the API key for enterprise apps or a Single Sign-On token for consumer apps in the same Authorization header.
How does Trip Management report problems on a trip?
You mark the trip InProgress through POST /trip/tripStatus and feed positions through POST /trip/gpsposition. The service compares them with the plan and raises notifications for Out of Route events, ETA changes, and weather alerts, readable through Get Trip Notifications.
Which Route Reports exist?
Mileage, Detailed, CalcMiles, Directions, GeoTunnel, HoursOfService, LeastCost, Road, State, TollDetail, RoutePath, and WeatherAlerts. Most run on GET or POST; HoursOfService and TollDetail are POST only. A POST batches up to 20 routes.
Ask about Trimble Maps

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.