Rand McNally supports two different distance engine applications: MileMaker has been available for a number of years and provides basic distance retrieval capabilities; IntelliRoute is a newer product with more robust functionality.
There is a separate system-defined external engine representing each of these distance engines from Rand McNally. MileMaker only supports two of the three Route Types available for IntelliRoute.
For MileMaker, latitude and longitude from TM will not be used. For IntelliRoute , latitude and longitude from TM, if available, will be used for distance calculation. Transit time will be calculated by multiplying the distance returned from MileMaker by an average speed. For IntelliRoute, if the transit time is available, it will be used by the Distance Server. Otherwise, the Distance Server will calculate the transit time for IntelliRoute the same way it does for MileMaker.
If the external engine is IntelliRoute, GeoCodes will be used when available. Otherwise, zip / postal code will be used. If the country is USA and the zip code length is greater than 5 digits (Zip + 4 has been used), only the first 5 digits will be used. If this fails, distance retrieval will be attempted using the city and state/province. GeoCodes are not used by MileMaker.
Route Types
The following Route Types (Parameter Name MMRouteType) are supported for TM / MileMaker integration:
The following Route Types (Parameter Name IRRouteType) are supported for TM / IntelliRoute integration:
Options
The following option is supported for TM / MileMaker integration:
Option (Parameter Name) |
Values |
Details |
AverageSpeed |
10 - 80 |
Expressed in Miles per hour |
ComputeEstimateAfterFailure |
T/F |
Default True. This parameter will determine how to handle the situation where the distance engine fails to compute a distance/transit time for any reason, including the case where the distance engine is not available. If True, an approximate distance and time will be computed based on the difference in latitude/longitude between the two locations; if False, the distance/transit time retrieval request will fail. |
The following options are supported for TM / IntelliRoute integration:
Option (Parameter Name) |
Values |
Details |
AverageSpeed |
10 - 80 |
Expressed in Miles per hour (applicable only for Route Type HHG) |
BorderRestriction |
T/F |
|
PhysicalRestriction |
T/F |
|
DefaultZipCode |
T/F |
The default is True. When set to False, if multiple locations match the zip code, distance retrieval using the engine will fail. |
AvoidTollRoadLvl |
<0 to 100> |
The number is a bias level; 0 means do not avoid toll road and 100 means avoid toll road. Default is 20. |
HazardMatProc |
T/F |
Requires separate module |
HazardMat |
T/F |
Requires separate module; occurs 10 times, one for each HazMat level |
53TruckLength |
T/F |
|
102TruckWidth |
T/F |
|
TrailerType |
<0,1,2> |
(0 – Single; 1 – Double; 2 – Triple) |
RouteVarianceTolerance |
<0 – 9999> |
|
ComputeEstimateAfterFailure |
T/F |
Default True. This parameter will determine how to handle the situation where the distance engine fails to compute a distance/transit time for any reason, including the case where the distance engine is not available. If True, an approximate distance and time will be computed based on the difference in latitude/longitude between the two locations; if False, the distance/transit time retrieval request will fail. |
ZeroMile |
T/F |
Use this option to specify whether IntelliRoute should return a zero mileage or an error message when both locations for the request are equal. IntelliRoute determines the distance based on the provided recognized location names and/or zip codes.
When the two locations for a distance request are equal, IntelliRoute returns an error message when Zero Miles Processing is False and returns zero miles when Zero Miles Processing is True.
|