Bulk data is delivered as CSV files which Linescape customers pull from our FTP server. Customers then integrate the bulk data into their TMS or other IT system so that the schedule data displays directly in the company system, alleviating the need to search elsewhere for data.
Data is available in a variety of formats, each providing a specific view for a particular use case.
Port Rotation Schedules
Schedule data in the port rotation format consists of the following data fields:
| Data Field | Description |
|---|---|
| carrier_code | Carrier SCAC Code |
| carrier_name | Carrier Name |
| service_code | Service/Route Code |
| service_name | Service/Route Name |
| vessel_imo | Vessel IMO Number |
| vessel_name | Vessel Name |
| vessel_voyage | Vessel Voyage Number |
| port_code | Port UN Locode |
| port_name | Port Name |
| port_eta | Port ETA Date |
| port_etd | Port ETD Date |
| portcalls_sequence | Sequence of Port Calls |
| portcalls_total | Total Number of Port Calls |
It is organized as one port call per record. For example, a vessel voyage which comprises 8 ports of call will be displayed in 8 records, with the portcalls_sequence indicating the chronological order of calls, from 1 to 8. To search for a particular schedule, customers search on the unique combination of Carrier-Service-Vessel-Voyage, which would return all 8 records of the schedule.
Each schedule has two timestamps. One is the date/time that each schedule was last updated. The other is the date/time that the carrier last sent a complete set of updated schedules. If the former timestamp becomes much older than the latter, then that schedule becomes a cancelled schedule and is filtered out of the data feed.
Transhipment Schedules
Schedule data in the transhipment format consists of the following data fields:
| Data Field | Description |
|---|---|
| c1scac | Carrier #1 SCAC |
| r1name | Route #1 Name |
| v1name | Vessel #1 Name |
| s1voy | Voyage #1 Label |
| oport | Origin Port Locode |
| oetd | Origin Port ETD |
| ts1port | Tranship Port #1 Locode |
| ts1eta | Tranship Port #1 ETA |
| omode | Origin Mode (S=”Ship”, T=”Tranship”) |
| c2scac | Carrier #2 SCAC |
| r2name | Route #2 Name |
| v2name | Vessel #2 Name |
| s2voy | Voyage #2 Label |
| ts1etd | Tranship Port #1 ETD |
| ts2port | Tranship Port #2 Locode |
| ts2eta | Tranship Port #2 ETA |
| c3scac | Carrier #3 SCAC |
| r3name | Route #3 Name |
| v3name | Vessel #3 Name |
| s3voy | Voyage #3 Label |
| ts2etd | Tranship Port #2 ETD |
| dport | Destination Port Locode |
| deta | Destination Port ETA |
| dmode | Destination Mode (S=”Ship”, T=”Tranship”) |
| cscac | Booking Carrier |
| dur | Duration (days) |
It is organized as one origin-destination per record. Each record may comprise either a single direct vessel voyage, or two vessel voyages with one transhipment, or three vessel voyages with two transhipments. Each of the three possible vessels may be deep-sea vessels or the first and/or last vessels may be feeder vessels.
Vessel Data
Vessel data can be delivered and associated with either of the schedule data feeds. The most commonly requested information consists of the following data fields:
| Data Field | Description |
|---|---|
| imo | Vessel IMO Number |
| name | Vessel Name |
| flag | Flag Country |
| call_sign | Call Sign |
| mmsi | MMSI Number |
| owner | Vessel Owner |
| operator | Vessel Operator |
| old_names | Previous Names |
| gross_tonnage | Gross Tonnage |
| net_tonnage | Net Tonnage |
| dwt | Deadweight Tons |
| max_teu | Nominal Container Capacity |
| avg_teu | 14mt Container Capacity |
| reefer_teu | Reefer Container Capacity |
| ship_type | Ship Type |
| port_of | Port of Registry |
| year | Year Built |