Import tracks

Tracks (see Tracks) are imported in a special way, because extra information is needed in order to interpret the files correctly.

Tracks are imported using:

        click Import (Image Next_Folder_16_n_p) in the Toolbar | Tracks

This will open a dialog as shown in figure 6.2.

Image importtracks_step1
Figure 6.2: Select files to import.

At the top, you select the file type to import. Below, select the files to import. If import is performed with the batch option selected, then each file is processed independently and separate tracks are produced for each file. If the batch option is not selected, then variants for all files will be added to the same track (or tracks in the case VCF files including genotype information).

The formats currently accepted are:

This is the standard fasta importer that will produce a sequence track rather than a standard fasta sequence. Please note that this could also be achieved by importing using Standard import and subsequently converting the sequence or sequence list to a track (see Converting data to tracks and back).
Annotations in gff/gtf/gvf formats. This is explained in detail in the user manual for the GFF annotation plugin: This can be particularly useful when working with transcript annotations downloaded from from Ensembl available in gvf format:

This is the file format used for variants by the 1000 Genomes Project and it has become a standard format. Read how to access data at When importing a single VCF file, you will get a track for each sample contained in the VCF file. In cases where more than one sample is contained in a VCF file, you can choose to import the files together or individually by using the batch mode found in the lower left side of the wizard shown in figure 6.2. The difference between the two import modes is that the batch mode will import the samples individually in separate track files, whereas the non-batch mode will keep variants for one sample in one track, thus merging samples from the different input files (in cases where the same sample is contained in different input files). If you import more than one VCF file that each contain more than one sample, the non-batch mode will generate one track file for each unique sample. The batch mode will generate a track file for each of the original VCF files with the entire content, as if importing each of the VCF files one by one. E.g. VCF file 1 contains sample 1 and sample 2, and VCF file 2 contains sample 2 and sample 3. When VCF file 1 and VCF file 2 are imported in non-batch mode, you will get three individual track files; one for each of the three samples 1, 2, and 3. If VCF file 1 and VCF file 2 were instead imported using the batch function, the result of the import would be four track files: a track from sample 1 from file 1, a track from sample 2 from file 1, a track from sample 2 from file 2, and a track from sample 3 from file 2.
Complete Genomics master var file
This is the file format used by Complete Genomics for all kinds of variant data and can be used to analyze and visualize the variant calls made by Complete Genomics. Please note that you can import evidence files with the read alignments into the CLC Genomics Workbench as well (refer to the Complete Genomics import section of the Workbench user manual).
Simple format for annotations. Read more at This format is typically used for very simple annotations, for example target regions for sequence capture methods.
The Wiggle format as defined by UCSC (, is used to hold continuous data like conservation scores, GC content etc. When imported into the CLC Genomics Workbench, a graph track is created. An example of a popular Wiggle file is the conservation scores from UCSC which can be download for human from
UCSC variant database table dump
Table dumps of variant annotations from the UCSC can be imported using this option. Mainly files ending with .txt.gz on this list can be used: Please note that importer is for variant data and is not a general importer for all annotation types. This is mainly intended to allow you to import the popular Common SNPs variant set from UCSC. The file can be downloaded from the UCSC web site here: Other sets of variant annotation can also be downloaded in this format using the UCSC Table Browser.
COSMIC variation database
This lets you import the COSMIC database, which is a well-known publicly available primary database on somatic mutations in human cancer. The file can be downloaded from the UCSC web site here:, and then go to 'Complete COSMIC data' and click on the file link. Users must first register to download the database. Import the file as a track, and then go to Data Management, scroll down to COSMIC and click on Workflow Configuration. Click on 'Select own' and select the track that has just been imported. Through Import->Tracks we support the following COSMIC databases in tsv format that can be manually downloaded from the COSMIC ftp site:
  • Complete COSMIC data (file: CosmicCompleteExport.tsv)
  • Complete mutation data (file: CosmicMutantExport.tsv)
  • All Mutation in census genes (file: CosmicMutantExportCensus.tsv)

Please see Annotation and variant formats for more information on how different formats (e.g. VCF and GVF) are interpreted during import in CLC format.

For all of the above, zip files are also supported.

Please note that for human data, there is a difference between the UCSC genome build and Ensembl/NCBI for the mitochondrial genome. This means that for the mitochondrial genome, data from UCSC should not be mixed with data from other sources (see

Most of the data above is annotation data and if the file includes information about allele variants (like VCF, Complete Genomics and GVF), it will be combined into one variant track that can be used for finding known variants in your experimental data. When the data cannot be recognized as variant data, one track is created for each annotation type.

Genome / gene annotation tracks can be automatically imported from relevant databases as described in the

For all types of files except fasta, you need to select a reference track as well. This is because most the annotation files do not contain enough information about chromosome names and lengths which are necessary to create the appropriate data structures.