Place ID search

The Place ID is defined when creating custom Places in Content Tools, and it can be added either per Place (create or modify), or through the import process for bulk changes.

The Search by Place ID is an offboard search. Once the driver enters the text string and taps Search, CoPilot calls Trimble Maps servers and checks for matches. Results include any custom Places in the account with a matching Place ID or Place name (exact match required, not case sensitive).

Depending on the search string, the driver may need to select from one or multiple results. The driver should verify the name and street address before adding it as a stop.

In CoPilot 10.27 and higher, the Place ID can be entered directly in the Search address or a place box at the top of the map screen.

In CoPilot 10.26 and lower, you need to specifically Search by Place ID.

Most fleets dispatch work to drivers based on a unique identifier within their TMS or dispatch software. This may be called location ID or customer code. Regardless of the name, this identifier can be applied to your custom Places as the Place ID.

Note: It is common to have multiple unique identifiers for one physical location. For example, a warehouse might have different identifiers for dry goods vs. frozen docks, or for different tenants. As long as the custom Place is created and the Place ID assigned, any work communicated outside of the integrated dispatching system can be added to the driver’s trip by manually searching for the Place ID.

Each stop added to a trip through Search by Place ID behaves the same as a stop added through the standard onboard custom Place search. If Sites functionality is active, the stop’s latitude/longitude will be compared against both the onboard cache of previously routed Sites and the full offboard set of your fleet’s custom Places with Sites data defined. The most up-to-date version found will be used to enhance the route results. If no matching Site is found, CoPilot will route to the stop’s location as usual.