Data
Data Importers
Where | Permission | |
---|---|---|
Orwell -> Data -> Importers | Can See Import |
vAMSYS offers several importers. Before proceeding, it is crucial that you read the Introduction and ensure that you are ready and capable. Importers are advanced and may not be the best option for you.
vAMSYS importers allow you to Create, Update, and Delete records via one file. You can perform multiple actions in one import - editing the CSV accordingly to add, delete, and update entries.
You do not have to import a full set of data (airports, routes, aircraft, etc.) if you are not changing every item. Importers need at least two lines - the 1st line for the headers and the 2nd line for the data you are adding, editing, or deleting. Importing only the data you are changing optimizes the process.
How Importers Work
In simplest terms, vAMSYS importers process one row at a time from the CSV you uploaded. Each row is independent of the others - if one row fails, the others will continue to be processed and imported. Rows that cannot be imported are collected into a new CSV file you can download, with an extra column at the end of each row explaining the failure.
We leverage our infrastructure to process multiple rows simultaneously, typically 50, 100, or 500 at a time, depending on the importer type. Importantly, vAMSYS processes one type of import at a time across the entire system. This means that only one type of import (e.g., one routes and one airports, etc.) is processed at any given time across the entire vAMSYS platform.
Please keep this in mind if you think the importer is stuck.
Creating Entries
Ensure the ID and Delete columns are blank to signal the importer to add the new data to the database.
Editing Entries
Ensure the ID field is present and accurate (get the latest export), and the Delete column is blank to signal the importer to update the record with the provided ID.
Deleting Entries
Ensure the ID field is present and accurate (get the latest export), and set the Delete column to 1 to signal the importer to delete the record.
What is "Blank"?
When we say a column should be "blank," it means the column must contain no data, spaces, or any characters. In a CSV text editor, this will appear as ,,
indicating an empty field.
Importer Failures
Sometimes, malformed data or unexpected inputs can cause the importer to hang. If the Rows, Processed, and Successful columns stop updating, it could be because the importer is busy or due to an error in the data. Allow some time to see if the importer completes.
Never upload the same file again and instead seek support. Re-attempting the same import file can duplicate data and cause more issues. Importers are designed to handle various inputs, but unexpected cases can still cause them to hang.
If the importer cannot perform an action, you will be able to download a file with all failed rows and explanations at the end of the import. Address these issues and re-import only the failed rows.
Importers
It is always best practice to first create some entries in VDS and then run an exporter. vAMSYS Importers use same column structure as exporters and are an ideal starting point.
Further, the columns imported have VDS equivalents - if ever in doubt - see VDS prompts and helper text to assist you. For each importer, we will cover only columns of interest.
Aircraft
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Fleet Type (ID) | Fleet ID can be retrieved from Export or VDS. |
SimBrief Airframe ID | Retrieved from SimBrief. Looks similar to 349674_1719351837546. |
SB OFP Format | OFP formats available by SimBrief, f.ex lido, baw, ryr etc. |
##_units | 'min' (minutes) or 'wgt' (weight). |
Delete | Enter '1' to delete, otherwise blank. |
Airport
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
World airport | Select column containing World Airport ID, or - if adding airports - column with the ICAO or IATA code. |
Base | 1 for yes, 0 for no. |
Delete | Enter '1' to delete, otherwise blank. |
Container
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Incompatible Containers | Can be blank or comma separated list of container IDs - 5, 15, 25, 30. Container IDs can be retrieved from Export or VDS. |
Delete | Enter '1' to delete, otherwise blank. |
Fleet
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Callsign Parameters | Comma separated list of parameter IDs - 5, 15, 25, 30. IDs can be retrieved from Orwell -> Settings -> VDS. |
Scoring Group | ID can be retrieved from Orwell -> Settings -> Scoring Groups |
SimBrief Airframe ID | Retrieved from SimBrief. Looks similar to 349674_1719351837546. |
SB OFP Format | OFP formats available by SimBrief, f.ex lido, baw, ryr etc. |
##_units | 'min' (minutes) or 'wgt' (weight). |
Delete | Enter '1' to delete, otherwise blank. |
Hub
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Default | 1 for yes, 0 for no. |
Airports | Comma separated list of Airport IDs - 5, 15, 25, 30. IDs can be retrieved from Export or VDS. |
Delete | Enter '1' to delete, otherwise blank. |
Load Factor
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Delete | Enter '1' to delete, otherwise blank. |
Route
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Departure ID | The ID for the departure airport can be retrieved from the Airports Export or VDS. If using the airport code, this field should be blank |
Departure Code | The ICAO or IATA code for the departure airport. Note: you should only use one of ID, ICAO or IATA when adding routes and the Import modal will ask which you wish to use. If you're using the ID, this field should be blank |
Arrival ID | The ID for the arrival airport can be retrieved from the Airports Export or VDS. If using the airport code, this field should be blank |
Arrival Code | The ICAO or IATA code for the arrival airport. Note: you should only use one of ID, ICAO or IATA when adding routes and the Import modal will ask which you wish to use. If you're using the ID, this field should be blank |
Callsign | Callsign for the route in the ICAO format. Note: Must be a valid combination of ICAO and IATA code from the Airline Callsign Parameters section in the Orwell Settings -> VDS |
Flight Number | Flight Number for the route in the IATA format. Note: Must be a valid combination of ICAO and IATA code from the Airline Callsign Parameters section in the Orwell Settings -> VDS |
Fleets | Comma separated list of Fleet IDs - 5, 15, 25, 30. IDs can be retrieved from Export or VDS. |
Altitude | Cruise altitude in following formats: 35000, FL350, /350 or 350 Note: Can be blank, in case you want the Simbrief to decide the cruise altitude, but the column is required |
CI | Cost Index for the flight. Can be any value from 0 to 999. Note: Can be blank. In that case, if using the Dispatch via Simbrief, an AUTO value is assigned to determine the Cost Index value for the flight, which is handled by Simbrief |
Route | Route for the flight. vAMSYS will get rid of any SIDs, STARs, and Step Climbs within the route Note: Can be blank, but the column is required. In that case, if using the Dispatch via Simbrief, the Simbrief will assign the route. |
Departure Time | Standard departure time of the flight, in hh:mm format. Note: Can be blank, but the column is required |
Arrival Time | Standard arrival time of the flight, in hh:mm format. Note: Can be blank, but the column is required |
Flight Length | Flight length in hh:mm format. Note: Can be blank, but the column is required. If blank, the value is calculated by vAMSYS by a general equation for an airliner |
Flight Distance | Flight distance in nautical miles. Note: Can be blank, but the column is required. If blank, the value is calculated by vAMSYS as a great circle distance |
Start date | Start date in yyyy-mm-dd hh:mm:ss value, when the flight should start to be bookable. |
End date | End date in yyyy-mm-dd hh:mm:ss value, when the flight should stop being bookable. Note: Can be blank, but the column is required |
Remarks | Any remarks or notes which are visible fo the pilot. Note: Can be blank, but the column is required |
Type | Type of the flight, based on the options in VDS. Can be "scheduled", "cargo", "charter", "training", "vfr", "repositioning", "jumpseat". Note: Mandatory value |
Tag | Tag which can be any text string, based on which the flights can be filtered. Comma separated list. Note: Can be blank, but the column is required |
Departure Stand Group | Stand Group ID can be retrieved from Export. Note: Can be blank, but the column is required |
Arrival Stand Group | Stand Group ID can be retrieved from Export. Note: Can be blank, but the column is required |
PAX LF | A single integer containing relevant PAX Load Factor ID. The ID can be retrieved from VDS or Load Factor export. Note: Can be blank, but the column is required |
Luggage LF | A single integer containing relevant Luggage Load Factor ID. The ID can be retrieved from VDS or Load Factor export. Note: Can be blank, but the column is required |
Cargo (Weight) LF | A single integer containing relevant Cargo Weight Load Factor ID. The ID can be retrieved from VDS or Load Factor export. Note: Can be blank, but the column is required |
Cargo (Volume) LF | A single integer containing relevant Cargo Volume Load Factor ID. The ID can be retrieved from VDS or Load Factor export. Note: Can be blank, but the column is required |
Containers | Comma separated IDs of relevant container types. The IDs can be retrieved from VDS or Containers export. Note: Can be blank, but the column is required |
Flightrules | Simbrief API value for ICAO Flight Plan - Flight Rules field. Can be "i" or "v". Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Flighttype | Simbrief API value for ICAO Flight Plan - Flight Type field. Can be "s", "n", "g", "m","x". Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Contpct | Simbrief API value for Contingency Fuel in percents (0.05), or percents/minutes (0.05/15). Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Resvrule | Simbrief API value for Reserve Fuel in minutes. Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Taxifuel | Simbrief API value for Taxi Fuel in minutes. Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Minfob | Simbrief API value for the Minimum Block fuel in Pounds. Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Minfod | Simbrief API value for the Minimum Arrival fuel in Pounds. Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Melfuel | Simbrief API value for the MEL Fuel in pounds (0.5) or minutes (20). Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
atcfuel | Simbrief API value for the ATC fuel in pounds (0.5) or minutes (20). Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
wxxfuel | Simbrief API value for the Weather fuel in pounds (0.5) or minutes (20). Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
addedfuel | Simbrief API value for the Extra Fuel in pounds (0.5) or minutes (20). Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
tankering | Simbrief API value for the Tankering Fuel in pounds (0.5) or minutes (20). Note: Can be blank, but the column is required. Find out more on the Simbrief API description at the Navigraph Forum |
Minfob units | Simbrief API value for the Minimum Block Fuel units. Can be "min" as minutes, or "wgt" as in weight. Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Minfod units | Simbrief API value for the Minimum Arrival Fuel units. Can be "min" as minutes, or "wgt" as in weight. Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Melfuel units | Simbrief API value for the MEL Fuel units. Can be "min" as minutes, or "wgt" as in weight. Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Atc units | Simbrief API value for the ATC Fuel units. Can be "min" as minutes, or "wgt" as in weight. Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Wxx units | Simbrief API value for the Weather Fuel units. Can be "min" as minutes, or "wgt" as in weight. Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Addedfuel units | Simbrief API value for the Extra Fuel units. Can be "min" as minutes, or "wgt" as in weight. Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Tankering units | Simbrief API value for the Tankering Fuel units. Can be "min" as minutes, or "wgt" as in weight. Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Addedfuel label | Simbrief API value for the Extra Fuel label. Can be "extra", "acf90", "acf99", "addnl", "apu", "hold", "naifr", "opn". Note: Can be blank, and the column is not required. Find out more on the Simbrief API description at the Navigraph Forum |
Hidden | Enter '1' for hidden, 0 for un-hidden. Blank value will assume 0. |
Delete | Enter '1' to delete, otherwise blank. |
Scenery
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Airport ID | ID can be retrieved from Export or VDS. |
Delete | Enter '1' to delete, otherwise blank. |
Stand Group
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Airport ID | ID can be retrieved from Export or VDS. |
Stands | Comma separated list of Stand IDs - 5, 15, 25, 30. IDs can be retrieved from Export. |
Delete | Enter '1' to delete, otherwise blank. |
Stand
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
World Airport ID | ID can be retrieved from Export. |
Delete | Enter '1' to delete, otherwise blank. |
Airport Managers
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Airline Staff Id | ID can be retrieved from Orwell Staff Table. |
Airport Id | ID can be retrieved from VDS or Airport Export. |
Inbound | Whether inbound toggle is on - 0 or Blank for no, 1 for yes |
Delete | Enter '1' to delete, otherwise blank. |
Badges
This import is more advanced than other imports as it uses raw json to record content. Do not experiment unless you are sure you know what you are doing - vAMSYS will not fix the damage caused.
Images cannot be uploaded via CSV, nor can badge order be changed - you will need to perform these actions in Orwell.
Column | Notes |
---|---|
ID | Leave blank for new entries. Existing entries will have it generated by vAMSYS. |
Name | Name of the Badge. |
Description | Description of the Badge. |
Content | Badge page content in json string or blank. |
Rules | Badge rules in json string or blank. |
Category | Category name |
Delete | Enter '1' to delete, otherwise blank. |
Changelog
Date | Notes |
---|---|
2024-07-19 | Initial Release |
2024-10-28 | New Importers |