Station
Station DTO is deprecated for providing address data and is superseded by Stop.
See also Transport Order.
Each delivery contains one loading station and one unloading station, which include corresponding station attributes and data, described in the following table.
Attribute | Description | Type (Length) | Example | Mandatory |
---|---|---|---|---|
avis | Dispatcher/recipient advice | CHAR(50) | 4973116906101 | False |
city | City | CHAR(100) | Ulm | False |
comment | Loading/unloading station comment, free text | CHAR(3000) | My loading station comment | False |
company_name | Company name | CHAR(100) | My Company GmbH | False |
country | Country code | CHAR(2) | DE | True |
from | Loading/unloading period begin (date and time) | CHAR(19) | 2021-10-08T12:00:00 | False |
name | Internal loading / unloading station identifier | CHAR(50) | HQ | False |
place_reference_id | Loading/unloading station reference id | CHAR(50) | PLACE_1 | False |
ramp | Gate name | CHAR(100) | Main entrance | False |
state | Federal state | CHAR(2) | BW | False |
street | Street name and number | CHAR(100) | Magirus-Deutz-Str. 16 | False |
timezone1 | Time zone of the loading station/ unloading station | CHAR(50) | Europe/Berlin | False |
until | Loading/unloading period end (date and time) | CHAR(19) | 2021-10-08T14:15:00+02:30 | False |
zip | Postal code | CHAR(20) | 89077 | False |
Although some of the address data is not mandatory for transport creation, they are crucial for the correct geolocation of the station on a map and ETA calculation. Please refer to the chapters Data Quality and Interfaces to Carrier Systems and “Best Practices” for more information.
1Note that the time zone is used in various processes but does not impact the representation of loading and unloading periods in UI (from and until attributes). They are displayed in local time defined by the provided time zone.