delivery table structure#
An output table for the freight tours synthesized by CRISTAL, including their mode, volume, trip type, origin and destination
Field |
Type |
NULL allowed |
Default Value |
Foreign key |
Description |
|---|---|---|---|---|---|
tour |
INTEGER |
NO |
0 |
Freight tour identifier |
|
leg |
INTEGER |
NO |
0 |
Freight trip leg identifier within a tour |
|
origin_location |
INTEGER |
NO |
0 |
The trip’s origin location (foreign key to the Location table) |
|
destination_location |
INTEGER |
NO |
0 |
The trip’s destination location (foreign key to the Location table) |
|
volume |
INTEGER |
NO |
0 |
Shipment volume (units: lbs.) |
|
is_e_commerce |
INTEGER |
NO |
0 |
boolean flag - is this an e-commerce delivery? |
|
pickup_trip |
INTEGER |
NO |
0 |
boolean flag - is this a pick up trip? |
|
off_hour_delivery |
INTEGER |
NO |
0 |
boolean flag - is this delivery performed in off hours? |
(* - Primary key)
The SQL statement for table and index creation is below.
CREATE TABLE Delivery (
"tour" INTEGER NOT NULL DEFAULT 0,
"leg" INTEGER NOT NULL DEFAULT 0,
"origin_location" INTEGER NOT NULL DEFAULT 0,
"destination_location" INTEGER NOT NULL DEFAULT 0,
"volume" INTEGER NOT NULL DEFAULT 0,
"is_e_commerce" INTEGER NOT NULL DEFAULT 0,
"pickup_trip" INTEGER NOT NULL DEFAULT 0,
"off_hour_delivery" INTEGER NOT NULL DEFAULT 0
);