A request for the travel time and distance between two locations. The locations can either be specified by latitude and longitude,or they may be existing locations within the input data.
Syntax:
[ DynamicComponentDependency ] traveldetailrequest TravelDetailRequestName {
[ TimeSpanUOM ] [ TimeZoneOverride ] [ ChangeDetection ] [ CustomChangeHandler ] #SqlDml.QueryBlock ;
}
Column Name | Data Type | Description | Default Value |
---|---|---|---|
id | String(32) | Specifies the unique identifier for this Travel Detail Request. |
Column Name | Data Type | Description | Default Value |
---|---|---|---|
latitude_from | Double | Defines the latitude of the start location for the travel. | |
latitude_to | Double | Defines the latitude of the end location for the travel. | |
location_id_from | String(32) | Defines the start location for the travel. | |
location_id_to | String(32) | Defines the end location for the travel. | |
longitude_from | Double | Defines the longitude of the start location for the travel. | |
longitude_to | Double | Defines the longitude of the start location for the travel. | |
profile_id_travel | String(32) | Defines the id of the profile to use when calculating the travel. | |
speed_factor | Double | Specifies an additional speed factor to apply when calculating the travel. | |
start_datetime | Date | Defines the travel start time to use when calculating the travel. |
traveldetailrequest TravelDetailRequest {{SelectName}} { SELECT .. id, -- optional columns .. latitude_from, .. latitude_to, .. location_id_from, .. location_id_to, .. longitude_from, .. longitude_to, .. profile_id_travel, .. speed_factor, .. start_datetime FROM {{sourceTableName}} WHERE ...; }
Note: All selected columns must have correct aliases that match a IFS Scheduling TravelDetailRequest.
Syntax:
<Identifier>
This page is generated from IFS Developer Studio at 2021-08-13 08:49.