Importing flights from a spreadsheet

From ZuluLog Wiki
(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
''You can automatically import flight records from your local hard drive into ZuluLog. To save time, please read the entire page before you start.''
 
 
  
 
====Let us do it for you====
 
====Let us do it for you====
  
We recommend the "Let us do it for you" choice from the Flight Import screen. Importing flights involves knowledge of specific field names and data layouts, and we're happy to import flights for our Platinum customers at no extra charge.
+
We recommend the "Let us do it for you" choice from the Flight Import screen. All you need to do is upload your CSV file, and we will take care of the rest.
  
  
 
====Do it yourself====
 
====Do it yourself====
  
You can also change your CSV file to match ZuluLog's format. We're here to help if you need advice.
+
If you'd prefer to perform the upload yourself, keep these hints in mind:
  
 +
* Files must be in CSV format. You cannot import .XLS or .XLSX files directly. You cannot import other types of binary files directly.
  
: 1.) '''Load your flight records into a spreadsheet''' (Figure 1). You may already have been keeping a spreadsheet of your records; or, if you've been using other logbook software, it most likely has an "export to spreadsheet" or "export to CSV" feature. At this point, the exact order and format of your columns do not matter. We are about to modify the spreadsheet to be compatible with ZuluLog.
+
* Files must contain column headings in row 1.
  
 +
* Files must contain flight information starting on row 2. Each row must represent exactly one flight. Flights cannot be spread over multiple rows.
  
[[File:Figure 1 - original spreadsheet.gif||center|frame|<center>'''Figure 1.'''</center>]]
+
* Delete any other rows, such as blank rows, or total rows at the end.
  
 +
* For flight imports, ZuluLog understands most common column names. For example, for the "Aircraft ID" column, any of these column names will work:
 +
**Aircraft ID
 +
**Registration
 +
**Tail Number
 +
**AC ID
 +
**Aircraft Ident
 +
**Reg
  
: 2.) '''Save a copy of your spreadsheet''' with extraneous information removed (Figure 2). This includes any total rows, spacer rows, and so on. You should be left with only a header row (in row 1) and data rows.
+
* For flight imports, many aircraft type columns are also supported. Aircraft definitions will automatically be created as applicable. A few examples of supported columns are:
 +
**Manufacturer
 +
**Model
 +
**SEL
 +
**Rotorcraft
 +
**Complex
  
 +
* Capitalization does not matter for column headings.
  
[[File:Figure 2 - extraneous information removed.gif||center|frame|<center>'''Figure 2.'''</center>]]
+
* ZuluLog recognizes dates in virtually any format. All of the following will work:
 +
**1/31/2014 (if American date formatting is set in your user preferences)
 +
**31/1/2014 (if European date formatting is set in your user preferences)
 +
**Jan 31 2014
 +
**31 January, 2014
  
 +
* If your date fields also include times, the time must be after the date, must be in 24-hour format, and must contain a colon (':') separating the hour and minute, for example:
 +
**1/31/14 15:09
  
: 3.) '''Rename your column headings''' in row 1 to the names that ZuluLog expects to see (Figure 3). This is how ZuluLog knows which information is contained in each column. Note that spelling and capitalization must match exactly. If any extra columns are left over, you may either delete the columns entirely, or change the column headings to values starting with "Ignore".
+
** Columns of type "True/False" (such as "X/Ctry", "Course Interception/Tracking", etc.) should contain TRUE or FALSE. If left blank, a value of FALSE will be assumed.
  
 +
** For columns that map to drop-downs in ZuluLog, the spelling and capitalization must exactly match what's contained in the ZuluLog drop-down. For example, if you have a column called Flight Review, valid values are "None", "Flight Review", "Checkride", and so on.
  
[[File:Figure 3 - new column headings.gif||center|frame|<center>'''Figure 3.'''</center>]]
 
  
 
: 4.) '''Reformat your flight data as necessary''' so that ZuluLog can interpret your data correctly (Figure 4).
 
 
 
[[File:Figure 4 - modified data to match requirements.gif||center|frame|<center>'''Figure 4.'''</center>]]
 
 
 
: 5.) '''Save your spreadsheet to a CSV text file''' (Figure 5). How you do this will depend on which spreadsheet program you use. Usually, you can select "Save as..." from the File menu. When the dialog box comes up, select "CSV (Comma delimited)" under the "Save as type" selection list.
 
 
 
[[File:Figure 5 - save spreadsheet to CSV format.gif|center|center|frame|<center>'''Figure 5.'''</center>]]
 
 
 
: 6.) '''You're ready to import!''' Select the appropriate import from the Console.
 
 
 
[https://www.zululog.com/docs/UploadFieldNames.jsp?impfmt=csv View the list of supported column/field names]
 
  
 
  [[Important hints for importing flights]]
 
  [[Important hints for importing flights]]
 
 
====General hints====
 
 
* ZuluLog recognizes dates correctly in virtually any format.
 
* Columns of type "True/False" should contain TRUE or FALSE. If left blank, a value of FALSE will be assumed.
 
* Columns of type "Select From List" may contain only a specified set of values depending on the column. Note that spelling and capitalization must match exactly.
 
 
 
 
[[Reference Manuals|&larr; Return to Reference Manuals]]
 

Revision as of 20:02, 6 November 2014

Let us do it for you

We recommend the "Let us do it for you" choice from the Flight Import screen. All you need to do is upload your CSV file, and we will take care of the rest.


Do it yourself

If you'd prefer to perform the upload yourself, keep these hints in mind:


Important hints for importing flights
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox