Routing and distance desk
Independent map, lane, stop, transfer, and mileage verification for brokered freight.
NGI freight agents, brokers, and staff should verify route distance, stops, transfers, toll exposure, restricted roads, equipment limits, and routing source before quoting, dispatching, invoicing, or closing a file. Driver or shipper mileage should be treated as a reference only, not the controlling mileage authority.
Route packet builder
Build a lane packet before pricing or approving a load.
This static page can launch a Google Maps visual preview and prepare the routing facts that NGI should verify in a licensed freight-routing system. The live portal should connect to a commercial routing API and store the mileage source, data version, route settings, user, timestamp, and approval history.
Reliable distance sources
Use licensed routing data for freight decisions.
Consumer maps are useful for orientation, but freight pricing needs settings that account for truck restrictions, stops, transfers, route basis, tolls, ferries, ports, equipment profile, hazmat, and lane-specific requirements.
Trimble Maps / PC*Miler
Useful for truck-specific commercial mileage, route reports, practical miles, calculated miles, costs, tolls, state mileage, and route path reporting when licensed.
Review Trimble routing APIsHERE Routing API
Supports route calculation with transport modes such as truck and can consider restrictions, route sections, summaries, and vehicle properties in supported regions.
Review HERE Routing APIAzure Maps
Microsoft documents truck routing coverage and truck attributes such as width, height, weight, turning radius, and cargo type for supported regions.
Review Azure Maps coverageGoogle Maps URLs and Routes API
Google Maps URLs can launch map directions without an API key, while the Routes API supports route and route-matrix calculations. Visual previews should not be the final freight mileage authority unless NGI formally approves that policy.
Review Google Maps URLsRouting governance
Distance accuracy must be auditable.
Source of truth
Set a written NGI policy naming the primary mileage authority by load type, geography, equipment, and customer agreement.
Multi-stop control
Every pickup, delivery, transfer, port, rail ramp, warehouse, or stop-off should be captured before calculating rate, fuel, tolls, fees, or transit time.
Exception review
Hazmat, oversize, overweight, high-value, refrigerated, port, rail, air, ocean, ferry, island, and international transfers should require additional review.
Record retention
Store route source, data version, distance, settings, map link, user, timestamp, quote/load ID, and reviewer approval with the transaction file.
