FlyBase:Downloads Overview

From FlyBase Wiki
Revision as of 08:35, 21 June 2019 by Steven marygold (talk | contribs) (Human disease model data (disease_model_annotations_fb_*.tsv.gz))

Jump to: navigation, search

Contents

Introduction

The Current Release page is a web interface allowing easy access to the main directories and the individual bulk data files available at the current FlyBase FTP repository. Files can be downloaded either directly through the web interface or by connecting to the FTP site using an ftp client such as wget. Note that the Safari browser does not support browsing of FTP site directories, though it does allow download of individual files. The ftp client wget accepts wild card patterns which means you can use a query of the following kind to obtain the latest file without having to specify the FlyBase release number:

$ wget ftp://ftp.flybase.net/releases/current/precomputed_files/genes/fbgn_annotation_ID_*.tsv.gz

Opening compressed files

Most of the files are compressed with the GNU gzip program and have the suffix '.gz'. Most modern computers will unpack and open these files automatically after download. Alternatively, the gunzip command may be used on machines runnign Apple OS X or Unix. On a Windows machine we suggest you use the program 7-zip to open these files as several people have reported problems using WinZip. The resulting file should open with any standard text editor.

Archived Data

Data files from previous releases, as well as links to servers hosting older releases of FlyBase, can be accessed via the Archived Data webpage.

Using an FTP client, data files from previous releases can be obtained by including the FlyBase release in the path /releases/<RELEASE_NUMBER>/. For example to retrieve the 'fbgn_annotation_ID' file for the FB2018_06 release, type:

wget "ftp://ftp.flybase.net/releases/FB2018_06/precomputed_files/genes/fbgn_annotation_ID_*.tsv.gz"

or more specifically:

wget ftp://ftp.flybase.net/releases/FB2018_06/precomputed_files/genes/fbgn_annotation_ID_fb_2018_06.tsv.gz

The /releases/current/ path will always point to latest FlyBase release and this directory will have only one copy of the file.

Main Data Set

This section contains links to top-level directories of the FlyBase FTP repository.

Postgres Chado Database Dump

The Chado database link leads to the psql directory of the current FTP repository where you can obtain a dump of the PostgreSQL Chado database. If you have a PostgreSQL client application installed and would like to access the latest FlyBase release without installing the database you can connect to the FlyBase public read only Chado database as: $ psql -h chado.flybase.org -U flybase flybase

The version running on this service is identical to the current web site release.

Drosophila Data

This section contains links to:

  • the current Chado-XML repository, containing the chado XML files generated from the PostgreSQL database for each FlyBase data class for the current FlyBase release. These files contain all the information used to generate FlyBase report pages and reflect the organization of the data in the database. The DTDs for these XML files, listing the structure of the files, are included in this directory.
  • the Genomes FTP repository, containing genome and genome annotation data files (including FASTA, GFF and GTF files) for D. melanogaster and other Drosophila species, organized by genome/FlyBase release number. For release FB2018_05 and earlier, data are available for each of the original 12 sequenced Drosophila species. From release FB2018_06 onward, data are available only for D. melanogaster, D. simulans, D. ananassae, D. pseudoobscura and D. virilis.

Bulk data files

The remaining sections of the Current Release page are organized by data class/type and provide direct downloads of the current bulk data files from the FTP site. Most files are from the current precomputed files directory of the FTP site and contain useful data for the specified data type (described in detail below). The Genomes files are from the current D. melanogaster FTP genomes directory or the current files for selected other Drosophila species.

The first part of a filename always describes the content of the file, and the second part may contain a FlyBase or genome annotation version number. For example, the file "fbgn_annotation_ID_fb_2018_06.tsv.gz" maps the primary FlyBase gene identifiers (FBgn) to their annotation IDs for the FB2018_06 release of FlyBase. The "dmel-all-CDS-r6.25.fasta.gz" files contains the coding sequences for all D. melanogaster genes from the release 6 of the sequence assembly, annotation release 25.

At the top and bottom of each tab separated text file there are a few lines that describe the file. These lines start with a '#' symbol. The line immediately before the start of the data contains headings for each of the tab separated columns in the file. The file can also include some blank lines to separate information about the version of the file from the description of data in the file.

Superscripts and subscripts are represented in the precomputed data files in the ASCII text format used by FlyBase, which is described in section 10.3 of the Nomenclature document.

Each precomputed data file contains the complete data set for the FlyBase release. If you are looking for information on a defined subset of genes or other FlyBase data type, you can use the Batch Download tool to query the precomputed data files and thus obtain only the data you require. This approach is described in more detail here.


Synonyms

FlyBase Synonyms (fb_synonym_*.tsv)

The file reports current symbols and synonyms for the following objects in FlyBase: genes (FBgn), alleles (FBal), balancers (FBba), aberrations (FBab), transgenic constructs (FBtp), insertions (FBti), transcripts (FBtr), and proteins (FBpp).

The file includes:

  • nuclear genes located to the sequence
  • mitochondrial genes
  • genes not located to the sequence
  • genes from drosophilid species and genes from non-drosophilids that have been introduced into transgenic flies

File format:

Column heading Content Description
primary_FBid Primary FlyBase identifier for the object.
organism_abbreviation Abbreviation (from the Species Abbreviations list) indicating the species of origin.
current_symbol Current symbol used in FlyBase for the object.
current_fullname Current full name used in FlyBase for the object.
fullname_synonym(s) Non-current full name(s) associated with the object (comma separated values).
symbol_synonym(s) Non-current symbol(s) associated with the object (comma separated values).


Genes

Genes data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'genes' data class.

Genetic interaction table (gene_genetic_interactions_*.tsv)

The file reports the summary of gene-level genetic interactions in FlyBase. This data is computed from the allele-level genetic interaction data captured by FlyBase curators.

The file includes information for Dmel genes only.

Interactions involving any of the following kinds of allele are considered when the gene-level genetic interaction data is computed:

  • classical mutations
  • alleles carried on transgenic constructs
  • loss-of-function mutations
  • gain-of-function mutations

File format:

Column heading Content Description
Starting_gene(s)_symbol Current FlyBase symbol of gene(s) involved in the starting genotype.
Starting_gene(s)_FBgn Current FlyBase identifier (FBgn#) of gene(s) involved in the starting genotype.
Interacting_gene(s)_symbol Current FlyBase symbol of gene(s) involved in the interacting genotype.
Interacting_gene(s)_FBgn Current FlyBase identifier (FBgn#) of gene(s) involved in the interacting genotype.
Interaction_type Type of interaction observed, either 'suppressible' or 'enhanceable'.
Publication_FBrf Current FlyBase identifier (FBrf#) of publication from which the data came.


Notes:

  • Each row contains information from a single reference. Thus if the same genetic interaction has been reported in multiple references, multiple rows will exist for that genetic interaction in the file.
  • 'suppressible' in column 5 indicates that phenotypes caused by mutation of the gene(s) listed in the starting genotype (column 1) are suppressed by mutation of the gene(s) listed in the interacting genotype (column 3).
  • 'enhanceable' in column 5 indicates that phenotypes caused by mutation of the gene(s) listed in the starting genotype (column 1) are enhanced by mutation of the gene(s) listed in the interacting genotype (column 3).

e.g.

Pten FBgn0026379 Akt1 FBgn0010379 suppressible FBrf0127089

indicates that phenotype(s) caused by a mutation of Pten are suppressed by a mutation of Akt1.

  • For cases where multiple genes are simultaneously mutated in either (or both) the starting and interacting genotype, then the genes involved are separated by a '|' in the relevant columns. In this case, the order of the list of symbols and of the list of ids in columns 1 and 2, or in columns 3 and 4 respectively are the same, so that the FBgn corresponding to the symbol for each gene can easily be identified.

e.g.

robo1|sli FBgn0005631|FBgn0264089 RhoGAP93B FBgn0038853 enhanceable FBrf0191476

indicates that:

  • phenotype(s) caused by a robo1, sli double mutant combination are enhanced by a mutation of RhoGAP93B.
  • FBgn0005631 corresponds to robo1, FBgn0264089 corresponds to sli


RNA-Seq RPKM values (gene_rpkm_report_fb_*.tsv.gz)

This file reports gene expression values based on RNA-Seq experiments, calculated as reads per kilobase per million reads (RPKM). RPKM values are calculated only for the unique exonic regions of the gene (excluding segments that overlap other genes), except for genes derived from dicistronic/polycistronic transcripts, in which case all exon regions are used in the RPKM expression calculation.

File format:

Column heading Content Description
Release_ID The D. melanogaster annotation set version from which the gene model used in the analysis derives.
FBgn# The unique FlyBase gene ID for this gene.
GeneSymbol The official FlyBase symbol for this gene.
Parent_library_FBlc# The unique FlyBase ID for the dataset project to which the RNA-Seq experiment belongs.
Parent_library_name The official FlyBase symbol for the dataset project to which the RNA-Seq experiment belongs.
RNASource_FBlc# The unique FlyBase ID for the RNA-Seq experiment used for RPKM expression calculation.
RNASource_name The official FlyBase symbol for the RNA-Seq experiment used for RPKM expression calculation.
RPKM_value The RPKM expression value for the gene in the specified RNA-Seq experiment.
Bin_value The expression bin classification of this gene in this RNA-Seq experiment, based on RPKM value. Bins range from 1 (no/extremely low expression) to 8 (extremely high expression).
Unique_exon_base_count The number of exonic bases unique to the gene (not overlapping exons of other genes). Field will be blank for genes derived from dicistronic/polycistronic transcripts.
Total_exon_base_count The number of bases in all exons of this gene.
Count_used Indicates if the RPKM expression value was calculated using only the exonic regions unique to the gene and not overlapping exons of other genes (Unique), or, if the RPKM expression value was calculated based on all exons of the gene regardless of overlap with other genes (Total). RPKM expression values are typically reported for the "Unique" count, except for genes on dicistronic/polycistronic transcripts, in which case the "Total" count is reported.


Physical interaction table (physical_interactions_fb_*.tsv.gz)

This file reports unique gene pairs with curated support for some type of physical interaction. The file does not currently distinguish between genes that are involved in protein-protein or RNA-protein interactions (or both).

File format:

Column heading Content Description
gene_FBgn1 The unique FlyBase gene ID for the first gene of the interacting pair.
gene_symbol1 The official FlyBase symbol for the first gene of the interacting pair.
gene_FBgn2 The unique FlyBase gene ID for the second gene of the interacting pair.
gene_symbol2 The official FlyBase symbol for the second gene of the interacting pair.
FBrf(s) The unique FlyBase IDs for the publications supporting this interaction.
FBig_id The unique FlyBase ID for this pairwise interaction.
#_reported_interactions The number of distinct experiments in support of this interaction.


Physical interaction MITAB file (physical_interactions_mitab_fb_*.tsv.gz)

This file reports each individual experiment curated by FlyBase that supports a physical interaction between two gene products. There can be multiple experiments (multiple rows in the file) between products of the same gene pair. Interaction molecule types currently curated are protein-protein, protein-RNA or RNA-RNA.

This file is in PSI-MI TAB format, a tab-delimited format developed by the HUPO Proteomics Standards Initiative (PSI) Molecular Interactions (MI) working group to facilitate interactomics data comparison and exchange. Details on the general MITAB format can be found here. The file makes use of the Molecular Interactions ontology which can be searched or browsed here. Fields are filled with “-” if values are missing or not relevant.


File format:

Column number Column heading General format FlyBase example Content description
1 ID(s) Interactor A database:identifier flybase:FBgn0002121 The unique Flybase identifier for the first gene of the interacting pair.
2 ID(s) Interactor B The unique Flybase identifier for the second gene of the interacting pair.
3 Alt ID(s) Interactor A database:identifier flybase:CG2671|entrez gene/locuslink:33156 The alternative gene identifiers currently provided are Flybase annotation IDs (CG#) and NCBI’s Entrez Gene ID separated by “|”.
4 Alt ID(s) Interactor B
5 Alias(es) Interactor A database:name(alias type) flybase:l(2)gl(gene name) The official Flybase gene symbol. It is referred to as “gene name” to adhere to the psi-mi ontology.
6 Alias(es) Interactor B
7 Interaction Detection Method(s) ontology:identifier(method name) psi-mi:"MI:0006"(anti bait coimmunoprecipitation) The assay used to detect the interaction, taken from the psi-mi ontology.
8 Publication 1st Author(s) surname initial(s) (publication year) Betschinger K. (2003) The first author and year of the publication where the interaction is described.
9 Publication ID(s) database:identifier flybase:FBrf0157155|pubmed:12629552 The unique FlyBase identifier for the publication followed by the unique PubMed identifier (if there is one) separated by “|”.
10 Taxid Interactor A taxid:identifier taxid:7227("Drosophila melanogaster") The NCBI taxonomy identifier for the source organism of the interactor. The vast majority of interactors in FlyBase come from D. melanogaster. There are, however, a few interspecies interactions consisting of a D. melanogaster interactor and an interactor of a different species.
11 Taxid Interactor B
12 Interaction Type(s) ontology:identifier(interaction type) psi-mi:"MI:0915"(physical association) Taken from the psi-mi ontology. Most often “physical association” for FlyBase.
13 Source Database(s) ontology:identifier(database name) psi-mi:"MI:0478"(flybase) All interactions are curated by FlyBase.
14 Interaction Identifier(s) database:identifier flybase:FBrf0157155-13.coIP.WB The unique FlyBase identifier for this interaction.
15 Confidence Value(s) Not applicable
16 Expansion Method(s) Not applicable
17 Biological Role(s) Interactor A Not applicable
18 Biological Role(s) Interactor B Not applicable
19 Experimental Role(s) Interactor A ontology:identifier(experimental role name) psi-mi:"MI:0496"(bait) The role played by the interactor in the experiment. Taken from the psi-mi ontology.
20 Experimental Role(s) Interactor B
21 Type(s) Interactor A ontology:identifier(interactor type name) psi-mi:"MI:0326"(protein) The molecule type. For FlyBase, these are limited to protein or ribonucleic acid. Taken from the psi-mi ontology.
22 Type(s) Interactor B
23 Xref(s) Interactor A Not applicable
24 Xref(s) Interactor B Not applicable
25 Interaction Xref(s) database:identifier flybase:FBig0000000103 Cross references for the interactions. For Flybase, these include an interaction group identifier (FBig) and possibly a collection identifier (FBlc) separated by “|”. All experiments that show an interaction between the products of gene A and gene B are compiled into an A-B interaction group, such that all interactions are associated with an interaction group identified by an FBig number. Interactions identified as part of a large scale study are also associated with the collection identifier, or FBlc number.
26 Annotation(s) Interactor A topic:text isoform-comment:a isoform Information on whether the interaction is specific to a particular interactor isoform.
27 Annotation(s) Interactor B
28 Interaction Annotation(s) topic:text comment:Phosphorylated isoforms of @l(2)gl@ are absent when @aPKC@ is knocked down by RNAi. Describes the source(s) of the interaction participants and includes free text comments about the interaction.
29 Host Organism(s) Not applicable
30 Interaction Parameters Not applicable
31 Creation Date Not applicable
32 Update Date Not applicable
33 Checksum Interactor A Not applicable
34 Checksum Interactor B Not applicable
35 Interaction Checksum Not applicable
36 Negative FALSE All interactions in FlyBase are positive.
37 Feature(s) Interactor A feature_type:range(text) sufficient binding region:aa 1-58(N-terminal region) Describes features of Interactor A such as binding sites, mutations that disrupt the interaction, epitope tags, etc.
38 Feature(s) Interactor B
39 Stoichiometry Interactor A Not applicable
40 Stoichiometry Interactor B Not applicable
41 Identification Method(s) Participant A Not applicable
42 Identification Method(s) Participant B Not applicable


Functional complementation table (gene_functional_complementation_*.tsv)

This file reports when functional complementation of Dmel genes by non-Dmel orthologs has been observed. This data is computed by FlyBase using a combination of the orthology data obtained from DIOPT and OrthoDB and the allele-level genetic interaction data curated from the literature. The file contains a list of gene Dmel - to - non-Dmel-ortholog gene pairs where a transgenic construct/mutant allele of the non-Dmel ortholog has been shown to at least partially suppress mutant phenotype(s) of an allele of the Dmel gene.

File format:

Column number Column heading Content Description
1 Dmel gene (symbol) Current FlyBase symbol of Dmel gene.
2 Dmel gene (FBgn) Current FlyBase identifier (FBgn#) of Dmel gene in column 1.
3 Functionally complementing ortholog (symbol) Current FlyBase symbol of a non-Dmel ortholog of the Dmel gene in column 1 where this non-Dmel gene has been show to functionally complement the Dmel gene.
4 Functionally complementing ortholog (FBgn#) Current FlyBase identifier (FBgn#) of a non-Dmel ortholog of the Dmel gene in column 1 where this non-Dmel gene has been show to functionally complement the Dmel gene.
5 Supporting_FBrf Current FlyBase identifier (FBrf#) of the publication that provides support for the functional complementation statement (the publication that reported the suppression of a mutant phenotype of the Dmel gene by a transgenic construct/mutant allele of the non-Dmel ortholog).

Notes:

  • Each row contains information from a single reference. Thus if multiple references support the same functional complementation statement, multiple rows will exist for that statement in the file.


FBgn <=> DB Accession IDs (fbgn_NAseq_Uniprot_*.tsv)

The file reports EMBL/GenBank/DDBJ nucleotide and protein accessions, UniProtKB/SwissProt/TrEMBL protein accessions, NCBI Entrez gene IDs and NCBI RefSeq transcript and protein accessions associated with FlyBase genes.

The file includes:

  • nuclear genes with sequence accession numbers
  • mitochondrial genes

it excludes:

  • genes without sequence accession numbers

File format:

Column number Column heading Content Description
1 gene_symbol Current symbol of gene.
2 organism_abbreviation Abbreviation (from the Species Abbreviations list) indicating the species of origin of the gene.
3 primary_FBgn# Current FlyBase identifier (FBgn#) of gene.
4 nucleotide_accession EMBL/GenBank/DDBJ nucleotide accession associated with the gene.
5 na_based_protein_accession EMBL/GenBank/DDBJ protein accession associated with the gene and the nucleotide accession in the preceeding 'nucleotide_accession' column
6 UniprotKB/Swiss-Prot/TrEMBL_accession UniProtKB/SwissProt/TrEMBL protein accession associated with the gene.
7 EntrezGene_ID NCBI Entrez ID associated with the gene.
8 RefSeq_transcripts NCBI RefSeq transcript accession associated with the gene.
9 RefSeq_proteins NCBI RefSeq protein accession associated with the gene and the transcript accession in the preceeding 'RefSeq_transcripts' column.

Notes:

  • Each row contains information about a single accession associated with a gene, thus if a gene has multiple accessions associated with it, multiple rows will exist for that gene in the file.
  • A single row contains only information about an EMBL/GenBank/DDBJ accession or information about a UniProtKB/SwissProt/TrEMBL accession or an NCBI Entrez gene ID or an NCBI RefSeq transcript accession.
  • For rows containing information about a EMBL/GenBank/DDBJ accession, a nucleotide accession associated with the gene is listed in column 4 ('nucleotide_accession'). If there is also a EMBL/GenBank/DDBJ protein accession associated with that gene and with the nucleotide accession in column 4, this protein accession is listed in column 5 ('na_based_protein_accession'). In this case, columns 6, 7, 8 and 9 are always empty.
  • For rows containing information about a UniProtKB/SwissProt/TrEMBL protein accession, a protein accession associated with the gene is listed in column 6 ('UniprotKB/Swiss-Prot/TrEMBL_accession'). In this case, columns 4, 5, 7, 8 and 9 are always empty.
  • For rows containing information about an NCBI Entrez gene, an ID associated with the gene is listed in column 7 ('EntrezGene_ID'). In this case, columns 4, 5, 6, 8 and 9 are always empty.
  • For rows containing information about an NCBI RefSeq accession, a transcript accession associated with the gene is listed in column 8 ('RefSeq_transcripts'). If there is also an NCBI RefSeq protein accession associated with that gene and with the transcript accession in column 8, this protein accession is listed in column 9 ('RefSeq_proteins'). In this case, columns 4, 5, 6 and 7 are always empty.


FBgn <=> Annotation ID (fbgn_annotation_ID_*.tsv)

The file reports current and secondary FlyBase identifiers associated with FlyBase genes, including current and secondary gene identifiers (FBgn#), and current and secondary annotation identifiers (CG#).

The file includes:

  • nuclear genes located to the sequence
  • mitochondrial genes

it excludes:

  • genes not located to the sequence

File format:

Column heading Content Description
gene_symbol Current symbol of gene.
organism_abbreviation Abbreviation (from the Species Abbreviations list) indicating the species of origin of the gene.
primary_FBgn# Current FlyBase identifier (FBgn#) of gene.
secondary_FBgn#(s) Secondary FlyBase identifier(s) (FBgn#) associated with the gene (comma separated values).
annotation_ID Current annotation identifier associated with the gene.
secondary_annotation_ID(s) Secondary annotation identifier(s) associated with the gene (comma separated values).

Notes:

  • If a gene has multiple secondary identifiers, all the values are stored within one tab separated column and are separated by commas (for example as: FBgn0034701,FBgn0034702).


FBgn <=> GLEANR IDs (fbgn_gleanr_*.tsv)

This file reports the relationship between the symbols and gene identifiers used by FlyBase for non-melanogaster genes identified by the AAA consortium, and the GLEANR identifier assigned to the gene during the initial annotation of the genome sequence.

The file includes:

  • non-melanogaster genes located to the sequence

it excludes:

  • D. melanogaster genes
  • non-melanogaster genes not located to the sequence

File format:

Column heading Content Description
organism_abbreviation Abbreviation (from the Species Abbreviations list) indicating the species of origin of the gene.
gene_symbol Current FlyBase gene symbol.
primary_FBgn# Current FlyBase identifier (FBgn#) of the gene.
GLEANR_ID GLEANR identifier assigned by the AAA Consortium.


FBgn <=> FBtr <=> FBpp IDs (fbgn_fbtr_fbpp_*.tsv)

This file reports the relationship of gene identifiers used by FlyBase for sequence localized genes, and the identifiers used for the transcript and polypeptide products of these genes.

The file includes:

  • genes located to the sequence

it excludes:

  • genes not located to the sequence

File format:

Column heading Content Description
FlyBase_FBgn Current FlyBase identifier (FBgn#) of the gene.
FlyBase_FBtr Current FlyBase identifier (FBtr#) of a transcript encoded by the gene listed in the preceeding 'FlyBase_FBgn' column.
FlyBase_FBpp Current FlyBase identifier (FBpp#) of a polypeptide encoded by the transcript listed in the preceeding 'FlyBase_FBtr' column, where this is relevant.

Notes:

  • Each row contains information about a single transcript and the polypeptide it encodes (if relevant). Thus if a gene encodes multiple isoforms, multiple rows with exist for that gene in the file.


FBgn <=> FBtr <=> FBpp IDs (expanded) (fbgn_fbtr_fbpp_expanded_*.tsv)

This expanded version of the "FBgn <=> FBtr <=> FBpp IDs" file adds organism, symbol and type information to the identifiers for sequence localized genes and their related transcript and protein products.

The file includes:

  • sequence localized nuclear genes with transcript/polypeptide annotations.
  • sequence localized mitochondrial genes with transcript/polypeptide annotations.

it excludes:

  • genes that have not been localized to the reference genome assembly for a given species.

File format:

Column number Column heading Content Description
1 organism Abbreviation (from the Species Abbreviations list) indicating the species of origin of the gene.
2 gene_type The type of gene, represented by a Sequence Ontology term.
3 gene_ID Current "FBgn" identifier of gene.
4 gene_symbol Current symbol of the gene.
5 gene_fullname Current full name of the gene.
6 annotation_ID Current FlyBase annotation identifier of the gene.
7 transcript_type The type of transcript, represented by a Sequence Ontology term.
8 transcript_ID Current FlyBase annotation identifier of the transcript.
9 transcript_symbol Current symbol of the transcript.
10 polypeptide_ID Current FlyBase annotation identifier of the polypeptide.
11 polypeptide_symbol Current symbol of the polypeptide.

Notes:

  • Each row contains information about a single transcript annotation, and if applicable, its associated polypeptide annotation.
  • Multiple rows may exist for a given gene in the file.
  • The "polypeptide_ID" and "polypeptide_symbol" columns are blank for non-mRNA transcript types.
  • For non-melanogaster annotations derived from NCBI Gnomon, some genes may be associated with a mix of coding and non-coding transcripts.
  • For D. melanogaster annotations, annotation IDs have a "CG" prefix for coding genes, or a "CR" prefix for non-protein-coding genes.
  • For non-melanogaster annotations, the annotation ID prefix varies by organism: "GD" for D. simulans ("Dsim"), "GF" for D. ananassae ("Dana"), "GA" for D. pseudoobscura ("Dpse") and "GJ" for D. virilis ("Dvir")

FBgn exons <=> Affy1 (fbgn_exons2affy1_overlaps.tsv)

The file is generated by testing for overlaps, no matter how small, of the locations of Affy1 oligos in the genome with the locations of gene exons, as defined by the Dmel gene models for the current release of FlyBase. If the location of an Affy1 oligo shows any kind of overlap with an exon of a gene, a Gene=>Affy reference is recorded in this file.

The extent of the overlap has no influence on the inclusion of a crossreference in this file. The overlap might be just one nucleotide, or it could be an exact match to the exon. For interpretation of the significance of a partial overlap please contact Affymetrix.

The file includes the following Dmel genes:

  • nuclear genes located to the sequence

it excludes:

  • genes not located to the sequence
  • mitochondrial genes

Notes:

  • Each line of the file can contain many tab separated columns:
  • The first column of a line contains the valid FlyBase identifiers of a gene.
  • Subsequent columns: Each Affy1 ID that overlaps with an exon of the gene, as described above, is listed in an additional tab separated column. Thus, this file does not contain a predefined number of columns.


FBgn exons <=> Affy2 (fbgn_exons2affy2_overlaps.tsv)

The file is generated from the location of Affy2 oligos exactly as described for Affy1 oligos above.


Genes map table (gene_map_table_*.tsv)

The file reports available localization information for FlyBase genes.

It includes:

  • nuclear genes located to the sequence
  • mitochondrial genes
  • genes not located to the sequence

File format:

Column heading Content Description
organism_abbreviation Abbreviation (from the Species Abbreviations list) indicating the species of origin of the gene.
current_symbol Current FlyBase gene symbol.
primary_FBid Current FlyBase identifier (FBgn#) of gene.
recombination_loc recombination map location.
cytogenetic_loc cytogenetic location.
sequence_loc genomic location.


Automated gene summaries (automated_gene_summaries.tsv)

The file contains the summaries found on gene report pages and the pop-ups in GBrowse and Interactions Browser in plain text.

It includes:

  • nuclear genes located to the sequence
  • mitochondrial genes
  • genes not located to the sequence

File format:

Column heading Content Description
- FlyBase ID. The Valid FlyBase identifier number for the gene.
- The gene summary as a string of plain text.


Gene Snapshots (gene_snapshots_*.tsv)

The file contains in plain text the gene snapshot information visible on gene report pages.

It includes only Dmel protein coding genes.

File format:

Column heading Content Description
FBgn_ID Current FlyBase identifier number for the gene.
GeneSymbol Current FlyBase symbol of the gene.
GeneName Current FlyBase name of the gene.
datestamp Date on which the information was last reviewed.
gene_snapshot_text Gene snapshot information for the gene. Cases that are in progress or are deemed to have insufficient data to summarize are stated as such.


Unique protein isoforms (dmel_unique_protein_isoforms_fb_*.tsv.gz)

The file reports D. melanogaster genes and their unique protein isoforms.

The file includes:

  • melanogaster genes located to the sequence

it excludes:

  • melanogaster genes not located to the sequence
  • non-melanogaster genes

File format:

Column heading Content Description
FBgn Current FlyBase identifier (FBgn#) of the gene.
FB_gene_symbol Current FlyBase gene symbol of the gene.
representative_protein Current FlyBase protein symbol of the representative protein isoform.
identical_protein(s) Current FlyBase protein symbol(s) of identical protein isoforms.


Non-coding RNAs (JSON) (ncRNA_genes_fb_*.json.gz)

This file reports all ncRNAs for D. melanogaster, D. ananassae, D. pseudoobscura pseudoobscura, D. simulans and D. virilis (i.e. those with gene models supported by FlyBase) in JSON format, as submitted to RNAcentral. Pseudogenes are excluded. In addition to the symbols and IDs for ncRNAs, this file also includes their associated gene, genomic location, sequence, Sequence Ontology classification, etc. The full schema for this file is available here.

Gene Ontology annotation files (go)

Gene Association File - GAF (gene_association.fb.gz)

The file contains the Gene Ontology (GO) controlled vocabulary (CV) terms assigned to FlyBase genes.

The file includes the following Dmel genes:

  • nuclear genes located to the sequence
  • mitochondrial genes
  • genes not located to the sequence

The columns of the file are described in section G.3.1. of the Reference manual.

Gene to Protein file (gp2protein.fb.gz)

The mapping file, gp2protein.fb, contains a full set of D.melanogaster protein coding genes localized to the genome mapped to UniProtKB protein identifiers.


To minimise redundancy, where there are multiple UniProtKB accessions for an FBgn, where a Swiss-Prot accession exists, this is used. Otherwise all TrEMBLs are listed. Multiple UniProtKB accessions are separated using a semi-colon.


Example format: FB:FBgn0086681 UniProtKB:Q0GYU3;UniProtKB:Q8INX4


Gene groups

Gene group data (gene_group_data_*.tsv)

This file reports all Gene Groups in FlyBase, together with their hierarchical relationships (where relevant) and member genes.

File format:

Column heading Content Description
FB_group_id Current FlyBase identifier (FBgg##) of Gene Group.
FB_group_symbol Current FlyBase symbol of Gene Group.
FB_group_name Current FlyBase full name of Gene Group.
Parent_FB_group_id Current FlyBase identifier (FBgg##) of parent of given Gene Group (if relevant).
Parent_FB_group_symbol Current FlyBase symbol of parent of given Gene Group (if relevant).
Group_member_FB_gene_id Current FlyBase identifier (FBgn##) of member gene (if terminal group).
Group_member_FB_gene_symbol Current FlyBase symbol of member gene (if terminal group).

Notes:

  • Where groups are arranged into hierarchies:
    • the member genes are only associated with the terminal subgroups,
    • the immediate parent of any subgroup is identified in the ‘Parent_FB_group_id' and 'Parent_FB_group_symbol' columns.
  • Separate lines are used for each member gene, meaning that each terminal group is listed multiple times (equal to the number of member genes).


Gene groups with HGNC IDs (gene_groups_HGNC_*.tsv)

This file reports all Gene Groups in FlyBase, together with the corresponding HGNC 'gene family' ID (where relevant).

File format:

Column heading Content Description
FB_group_id Current FlyBase identifier (FBgg##) of Gene Group.
FB_group_symbol Current FlyBase symbol of Gene Group.
FB_group_name Current FlyBase full name of Gene Group.
HGNC_family_ID HGNC ID of equivalent human 'gene family'.

Notes:

  • The absence of an HGNC_family_ID entry indicates there is no equivalent HGNC gene family for that FlyBase gene group.
  • Because of different sub-group structures (etc), a single HGNC family may be associated with multiple FlyBase gene groups.
  • Similarly, a single FlyBase gene group may be associated with multiple HGNC gene families - these are shown on separate lines.


Alleles and Stocks

Allele data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'alleles' data class.


Stock data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'stocks' data class.


Stock data (stocks_*.tsv.gz)

This file reports genetic components and related information about Stocks in FlyBase.

File format:

Column heading Content Description Example
FBst The unique identifier assigned to this stock by FlyBase. FBst0000002
collection_short_name A short name for the stock collection that holds the stock. Bloomington
stock_type_cv The controlled vocabulary term and unique identifier that describe the state of the stock. living stock ; FBsv:0000002
species Abbreviation (from the Species Abbreviations list) indicating the species of the stock. Dmel
FB_genotype Genetic components of the stock corresponding to alleles, aberrations, balancers, or insertions in FlyBase. May be empty. w[*]; betaTub60D[2] Kr[If-1]/CyO
description Genetic components of the stock as provided to FlyBase by the collection that holds the stock. FlyTrap: ZCL1796 III
stock_number The stock identifier provided to FlyBase by the collection that holds the stock. May be empty. 110818


Genetic interactions (allele_genetic_interactions_*.tsv)

The file reports controlled vocabulary (i.e. not free text) genetic interaction data associated with alleles. This is the data reported in the "Phenotypic Class" and "Phenotype Manifest in" subsections of the "Interactions" section of each Allele Report.

File format:

Column heading Content Description
allele_symbol Current FlyBase allele symbol.
allele_FBal# Current FlyBase identifier (FBal#) of allele.
interaction Interaction information associated with allele.
FBrf# Current FlyBase identifer (FBrf#) of publication from which data came.

Notes:

  • Each row contains information about a single interaction from a single reference. Thus if multiple genetic interactions have been reported for a given allele, or if multiple references report the same interaction for a given allele, multiple rows will exist for that allele in the file.


Phenotypic data (allele_phenotypic_data_*.tsv)

The file reports controlled vocabulary (i.e. not free text) phenotypic data associated with alleles. This is the data reported in the "Phenotypic Class" and "Phenotype Manifest in" subsections of the "Phenotypic Data" section of each Allele Report.

File format:

Column heading Content Description
allele_symbol Current FlyBase allele symbol.
allele_FBal# Current FlyBase identifier (FBal#) of allele.
phenotype Phenotypic data associated with allele.
FBrf# Current FlyBase identifer (FBrf#) of publication from which data came.

Notes:

  • Each row contains information about a single phenotype from a single reference. Thus if multiple phenotypes have been reported for a given allele, or if multiple references report the same phenotype for a given allele, multiple rows will exist for that allele in the file.


Alleles <=> Genes (fbal_to_fbgn_fb_*.tsv)

This file reports the relationship between gene identifiers and the identifiers used for alleles of these genes.

File format:

Column heading Content Description
AlleleID Current FlyBase identifier (FBal#) of the allele.
AlleleSymbol Current symbol of the allele.
GeneID Current FlyBase identifier (FBgn#) of the gene.
GeneSymbol Current symbol of the gene.


Orthologs

Drosophila Orthologs (dmel_orthologs_in_drosophila_species_fb_*.tsv.gz)

The file reports D. melanogaster genes and their orthologs in other sequenced Drosophila genomes, as determined by OrthoDB. (The version of OrthoDB currently being used is shown in the 'Orthologs' -> 'Orthologs (via OrthoDB)' section of a Gene Report.)

The file includes:

  • nuclear genes located to the sequence

it excludes:

  • genes not located to the sequence
  • mitochondrial genes

File format:

Column heading Content Description
FBgn_ID Current FlyBase identifier (FBgn#) of the D. melanogaster gene.
GeneSymbol Current FlyBase gene symbol of the D. melanogaster gene.
Arm/Scaffold Arm upon which the D. melanogaster gene is localized.
Location Location of D. melanogaster gene on the arm.
Strand Strand of D. melanogaster gene ('1' indicates the positive strand, '-1' indicates the negative strand).
Ortholog_FBgn_ID Current FlyBase identifier (FBgn#) of the non-melanogaster orthologous gene.
Ortholog_GeneSymbol Current FlyBase gene symbol of the non-melanogaster orthologous gene.
Ortholog_Arm/Scaffold Arm upon which the non-melanogaster orthologous gene is localized.
Ortholog_Location Location of non-melanogaster orthologous gene on the arm.
Ortholog_Strand Strand of non-melanogaster orthologous gene ('1' indicates the positive strand, '-1' indicates the negative strand).
OrthoDB_Group_ID OrthoDB orthology group ID to which the pair-wise association belongs.

Notes:

  • Each row is a pair-wise association beween a D. melanogaster gene and a non-melanogaster ortholog. Thus, multiple rows exist for each D. melanogaster gene in the file.


Human Orthologs (dmel_human_orthologs_disease_fb_*.tsv.gz)

This file reports the human orthologs of D. melanogaster genes using the DIOPT dataset. Each line reports a single orthologous pair, which means that each human and D. melanogaster gene can appear in multiple lines. Note that ortholog calls supported by only 1 or 2 algorithms (DIOPT score <3) have been removed. Human genes are also associated with diseases (OMIM phenotypes) using the OMIM dataset.

File format:

Column heading Content Description
Dmel_gene_ID Current FlyBase identifier (FBgn#) of the D. melanogaster gene.
Dmel_gene_symbol Current FlyBase gene symbol of the D. melanogaster gene.
Human_gene_HGNC_ID HGNC ID of orthologous human gene.
Human_gene_OMIM_ID OMIM ID of orthologous human gene.
Human_gene_symbol HGNC gene symbol of orthologous human gene.
DIOPT_score DIOPT 'score' for orthology call (i.e. the number of individual algorithms that support the call).
OMIM_Phenotype_IDs OMIM Phenotype ID of orthologous human gene (comma separated values).
OMIM_Phenotype_IDs[name] OMIM Phenotype ID of orthologous human gene (with the corresponding OMIM name in square brackets). Multiple phenotype[name] entries are separated by a comma.


Human disease

Human disease model data (disease_model_annotations_fb_*.tsv.gz)

This file reports (i) all experimental-based disease model annotations, associated with alleles; and (ii) all 'potential' disease models based on orthology to human disease genes in OMIM (see FBrf0241599 for more information on this pipeline) for D. melanogaster. 'Alleles' encompass both classical alleles and transgenic alleles; the latter may relate to transgenic constructs of D. melanogaster genes or non-D. melanogaster genes (often human genes) inserted into the D. melanogaster genome. These disease model annotations are reported in the "Human Disease Model Data" -> "Disease Ontology (DO) Annotations" section of the Gene and Allele Reports.

File format:

Column heading Content Description
FBgn ID Current FlyBase identifier (FBgn#) of the gene associated with the allele of an experimental annotation, or the D. melanogaster ortholog of a human gene associated with a disease in OMIM.
Gene symbol Current FlyBase symbol of the gene in column 1.
HGNC ID HGNC ID of the gene identified in column 1 where it is a human gene (experimental-based annotations only).
DO qualifier Type of association between the object of annotation and the disease - one of 'model of', 'ameliorates', 'exacerbates', 'DOES NOT model', 'DOES NOT ameliorate' or 'DOES NOT exacerbate'.
DO ID Disease Ontology (DO) ID.
DO term Disease Ontology (DO) term.
Allele used in model (FBal ID) Current FlyBase identifier (FBal#) of allele (experimental-based annotations only).
Allele used in model (symbol) Current FlyBase symbol of allele (experimental-based annotations only).
Based on orthology with (HGNC ID) HGNC ID of the human ortholog used for annotations based on orthology to human disease genes.
Based on orthology with (symbol) HGNC gene symbol of the human ortholog used for annotations based on orthology to human disease genes.
Evidence/interacting alleles Evidence code, with interacting allele(s) where appropriate. For experimental-based annotations, the evidence code is one of: 'inferred from mutant phenotype', 'in combination with', 'modeled by', 'is ameliorated by', 'is exacerbated by', 'is NOT ameliorated by' or 'is NOT exacerbated by'. Interacting alleles are give as 'FLYBASE:<allele_symbol>; FB:<FBal_ID>', with multiple alleles separated by a comma. For orthology-based annotations, the evidence code is 'inferred from electronic annotation'.
Reference (FBrf ID) Current FlyBase identifier (FBrf#) of the source publication.

Human Orthologs (dmel_human_orthologs_disease_fb_*.tsv.gz)

This file reports the human orthologs of D. melanogaster genes using the DIOPT dataset. Each line reports a single orthologous pair, which means that each human and D. melanogaster gene can appear in multiple lines. Note that ortholog calls supported by only 1 or 2 algorithms (DIOPT score <3) have been removed. Human genes are also associated with diseases (OMIM phenotypes) using the OMIM dataset.

This is identical to the file of the same name listed under the 'Orthologs' section above.

Nomenclature

Species abbreviation list (species-ab.gz)

The species-abbreviations.txt file lists all the species for which FlyBase has some information. FlyBase includes gene reports for genes derived from species within the family Drosophilidae, as well as gene reports for non-drosophilid genes ("foreign genes") that have been introduced into Drosophila via transgenic constructs and for engineered objects such as a fusion gene between two D.melanogaster genes. In addition, information about non-Drosophilid species is also displayed in GBrowse, for example in the "Similarity: Proteins" evidence tier. Thus, the file contains information for both Drosophilid and non-Drosophilid species.

There are 8 columns of data in the file, each separated by " | ".

Column heading Content Description
Internal_id The Primary FlyBase identifier of the organism.
Taxgroup A grouping term, currently one of "drosophilid", "non-drosophilid eukaryote", "prokaryote", "transposable element" or "virus".
Abbreviation The standard FlyBase prefix for the species. This abbreviation is used in FlyBase as the first part of the symbol (before the '\') of any object, e.g. a gene or allele, that originates from this species. This column may be blank, if data from a species is displayed in an evidence tier on GBrowse but no individual report page exists for that species in FlyBase.
Genus The genus name of the organism.
Species name The species name of the organism.
Common name The common name of the organism. This column may be blank.
Comment A free text field for additional comments. This column may be blank.
Ncbi-taxon-id The NCBI Taxonomy Database Taxon ID for the organism. This column may be blank.

An html version of this file is also available - see the Species Abbreviations page.


Ontology Terms

The ontology files used by FlyBase are in the OBO format used by the Open Biomedical Ontology group, and may be viewed using the free OBO-Edit tool.

Ontologies undergo continual development. Links are provided to the 'frozen versions' used for the current release of FlyBase, together with links to the current 'live' versions at external sites.

Frozen files used for this release of FlyBase

List of ontologies available for download:

  • FBbt: fly_anatomy
  • FBdv: fly_development
  • FBcv: flybase controlled vocabulary
  • FBsv: stock ontology
  • GO: gene ontology
  • FBbi: image ontology
  • SO: sequence ontology
  • DO: human disease ontology


Current 'Live' Files

List of ontologies available for download:

  • FBbt: fly_anatomy

Note: link points to the ontology version fbbt-simple.obo, which lacks a few minor FlyBase specific changes that are present in the 'fly_anatomy.obo' version

  • FBdv: fly_development

Note: link points to the ontology version fbbt-simple.obo, which lacks a few minor FlyBase specific changes that are present in the 'fly_development.obo' version

  • FBcv: flybase controlled vocabulary

Note: link points to the ontology version fbcv-simple.obo, which lacks a few minor FlyBase specific changes that are present in the 'flybase_controlled_vocabulary.obo' version

  • FBsv: stock ontology
  • GO: gene ontology
  • FBbi: image ontology
  • SO: sequence ontology
  • DO: human disease ontology


Genomes: Annotation and Sequence

All Sequenced Drosophila Species

Links are available to the following FTP repositories:

  • Current FTP repository
  • Current FastA repository
  • Current GFF repository
  • FTP archive (previous releases)
  • Current list of individual FASTA files
  • Current list of individual GFF files


Individual Sequenced Drosophila Species

For release FB2018_06 onward, the above links are available for the following sequenced Drosophila species:

Species name Abbreviation
Drosophila melanogaster Dmel
Drosophila ananassae Dana
Drosophila pseudoobscura pseudoobscura Dpse
Drosophila simulans Dsim
Drosophila virilis Dvir


For earlier archived releases, the above links are also available for these additional species (other members of the original 12 sequenced Drosophila species):

Species name Abbreviation
Drosophila erecta Dere
Drosophila grimshawi Dgri
Drosophila mojavensis Dmoj
Drosophila persimilis Dper
Drosophila sechellia Dsec
Drosophila willistoni Dwil
Drosophila yakuba Dyak

FASTA files

The FlyBase FASTA files generally follow the FASTA format guidelines with one exception being that our header lines sometime exceed the 80 character limit. The FASTA filenames follow these formats:

dmel-all--r<release-number>.fasta.gz

or

dmel-<chromosome_arm>-<data_type>-r<release-number>.fasta.gz

Where data_type is one of the following entries in the table below. The all files contain sequences for those data types on all chromosome arms whereas the specific chromosome arm have only those features for that particular chromosome.

Data Type Content Description
aligned The region of genomic sequence that analysis features align to.
CDS The contiguous protein coding sequence which begins with, and includes, a start codon and ends with, and includes, a stop codon.
chromosome The sequence of each chromosome arm.
clones The sequence of full length cDNA, 3' and 5' ESTs, and partial length clones.
exon The sequence of each exon split up into individual FASTA records.
five_prime_UTR The sequence of 5' untranslated regions.
gene The sequence of the gene span.
gene_extended2000 The sequence of the gene span with 2000 base pairs added upstream and downstream.
intergenic The sequence of chromosomal regions between genes that do not contain known gene models.
intron The sequence of each intron split up into individual FASTA records.
miRNA The sequence of transcripts that are typed as micro RNAs.
miscRNA The sequence of transcripts that are typed as small nuclear RNA (snRNA), small nucleolar RNA (snoRNA), or ribosomal RNA (rRNA). May also contain other transcript types that do not exist in their own individual files.
ncRNA The sequence of transcripts that are typed as non coding RNAs (ncRNA).
predicted The sequence of various features that are derived from a variety of prediction algorithms. These can encompass analyses conducted by FlyBase or by 3rd party groups.
pseudogene The sequence of transcripts that are typed as pseudogenes.
sequence_features The sequence of sequence features, which currently describe data about RNAi reagents. In the future, it will also contain natural genomic features (aside from transcribed regions), such as replication origins, transcription factor binding sites and boundary elements, and other experimental reagents that map to the genome, such as microarray oligonucleotides and rescue fragments.
synteny The sequence of syntenic regions between two species.
three_prime_UTR The sequence of 3' untranslated regions.
transcript The sequence of transcripts that are typed as messenger RNAs (mRNA).
translation The resulting protein sequence from protein coding transcripts.
transposon The sequence of transposable elements.
tRNA The sequence of transcripts that are typed as transfer RNAs (tRNA).


The typical format of our FASTA header begins with an ID followed by any number of fields that follow this format

field_name=value;

Multiple field values are separated by commas

field_name=value1,value2;

This table describes some of the field names found in our FASTA headers

Field Name Description
type The feature type of the FASTA sequence record.
loc The genomic location given in the NCBI's feature location format. Please see the NCBI's site for more information.
ID A unique ID. IDs in the form of FBxx[0-9]+ are a unique FlyBase object identifier.
name The name or symbol of the feature.
dbxref Database cross references relating to the FASTA record. The dbxref values use a 'dbname:dbid' format.
MD5 An MD5 checksum calculated from the sequence that can be used to identify identical sequences.
length The length of the sequence found in the FASTA record.
release The release number denotes the annotation release which this FASTA record corresponds to.
species The species abbreviation that this FASTA record corresponds to.


GFF files

The FlyBase GFF files follow the GFF v3 specification. The GFF files contain feature line definitions for gene models, predicted features, alignments, and many other features.

For melanogaster, there are 3 GFF files distributed, they include:

dmel-all-r<release-number>.gff.gz
Contains all chromosome arms
dmel-all-no-analysis-r<release-number>.gff.gz
Same as above except all match and match_part features have been removed
dmel-<chromosome_arm>-r<release-number>.gff.gz
Contains only a single chromosome arm as identifed by the filename

The other species have the all chromosome arm file and also a tar and gzipped file containing the individual scaffolds. Please note that the tarball contains thousands of files in a single directory level so extracting them may result in filesystem performance issues.

The GFF files are produced for each species and can be downloaded from our FTP site using this URL form:

ftp://ftp.flybase.org/genomes/<species abbreviation>/current/gff/

e.g. ftp://ftp.flybase.org/genomes/dmel/current/gff/


GTF files

The FlyBase GTF files follow the GTF v2.2 specification. The GTF files contain feature line definitions for gene models.

The GTF are produced for each species and can be downloaded from our FTP site using this URL form:

ftp://ftp.flybase.org/genomes/<species abbreviation>/current/gtf/

e.g. ftp://ftp.flybase.org/genomes/dmel/current/gtf/


Transcripts and Polypeptides

Transcript data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'transcripts' data class.


Polypeptide data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'polypeptide' data class.


Non-coding RNAs (JSON) (ncRNA_genes_fb_*.json.gz)

This file reports all ncRNAs for D. melanogaster, D. ananassae, D. pseudoobscura pseudoobscura, D. simulans and D. virilis (i.e. those with gene models supported by FlyBase) in JSON format, as submitted to RNAcentral. Pseudogenes are excluded. In addition to the symbols and IDs for ncRNAs, this file also includes their associated gene, genomic location, sequence, Sequence Ontology classification, etc. The full schema for this file is available here.

Transposons, Transgenic Constructs, and Insertions

Insertions (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'insertions' data class.


Transgenic Constructs (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'transgenic constructs' data class.


Transgenic construct maps (construct_maps.zip)

The construct_maps.zip file unpacks as a directory containing maps of recombinant constructs and transgenic transposons generated by FlyBase, that are based on the compiled sequence data curated by FlyBase. The name of each PNG image in the directory corresponds to the FlyBase identifier of the respective recombinant construct or transgenic transposon.

Please note: For transgenic transposons, the image may be a map of the corresponding plasmid form.


Map data for insertions (insertion_mapping_*.tsv)

The insertion mapping table reports available localization information for Dmel insertions.

File format:

Column heading Content Description
insertion_symbol Current symbol of insertion.
FBti# Current FlyBase identifier (FBti#) of insertion

.

genomic_location Genomic location of insertion.
range Range (t/f) indicates whether genomic location is range or single base.
orientation Orientation (1/0) indicates orientation of insertion on chromosome.
estimated_cytogenetic_location Estimated cytogenetic location based on correlation of genomic location and estimated genomic location of cytological bands.
observed_cytogenetic_location Observed cytogenetic location reported in the literature.


Transposable elements (canonical set) (transposon_sequence_set.embl.txt)

This is a file of 'canonical' sequences of the transposable elements from Drosophila maintained by M. Ashburner.

The first section of the file outlines the history and revisions to the file and also lists the current set of elements, their size and whether the subsequent sequence data is complete.

The second section of the file, which is separated from the first by a line of "_" characters contains the sequence data of all the elements in EMBL format. The record for each element starts with a line prefixed by "ID" and ends with a line containing "//".


Frequently-used GAL4 drivers table (JSON) (fu_gal4_table_fb_2018_06.json.gz)

This file reports a list of all GAL4 drivers that have been curated to at least 21 references and/or are among 150 most frequently requested GAL4 stocks from the Bloomington Drosophila Stock Center, in JSON format. In addition to the symbols and IDs for Scer\GAL4 alleles, this file also includes their associated transposon or insertion, associated gene, expression pattern in controlled vocabulary stage and anatomy terms, stocks, and publications, all with IDs, as well as free text expression pattern descriptions. This file, except for publications and stocks, is also available in TSV format here.

Aberrations

Aberration data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'aberrations' data class.


Balancer data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'balancers' data class.


Large dataset metadata

Dataset metadata members (dataset_metadata_fb_*.tsv.gz)

This file lists all features that are associated with a dataset/collection (e.g., genes, cDNA clones, TF_binding_sites, Affymetrix probes).

File format:

Column heading Content Description
Dataset_Metadata_ID The unique FlyBase ID for the dataset.
Dataset_Metadata_Name The official FlyBase symbol for the dataset.
Item_ID The unique FlyBase ID for the feature associated with this dataset.
Item_Name The official FlyBase symbol for the feature associated with this dataset.


Clones

Clone data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'clones' data class.


cDNAs: FBcl <=> acc. ID (cDNA_clone_data_*.tsv)

The file reports basic cDNA clone data in FlyBase.

File format:

Column heading Content Description
FBcl# Current FlyBase identifier (FBcl#) of cDNA clone.
organism_abbreviation Abbreviation (from the Species Abbreviations list) indicating the species of origin of the clone.
clone_name Clone name.
dataset_metadata_name Name of dataset associated with clone.
cDNA_accession(s) EMBL/GenBank/DDBJ cDNA accession number.
EST_accession(s) EMBL/GenBank/DDBJ EST accession number.


Genomic: FBcl <=> acc. ID (genomic_clone_data_*.tsv)

The file reports basic genomic clone data in FlyBase.

File format:

Column heading Content Description
FBcl# Current FlyBase identifier (FBcl#) of genomic clone.
organism_abbreviation Abbreviation (from the Species Abbreviations list) indicating the species of origin of the clone.
clone_name Clone name.
accession EMBL/GenBank/DDBJ cDNA accession number.


References

Combined reference data (Chado XML)

The chado XML file generated from the FlyBase PostgreSQL database for the 'references' data class.


FlyBase FBrf <=> PubMed ID <=> PMCID <=> DOI (fbrf_pmid_pmcid_doi_fb_*.tsv.gz)

This file lists all publications in the FlyBase bibliography that have a PubMed ID. Additional identifiers are listed as applicable.

File format:

Column heading Content Description
FBrf The unique FlyBase ID for this publication.
PMID The unique PubMed ID for this publication.
PMCID The unique PubMed Central ID for this publication, if applicable.
DOI The digital object identifier assigned to the publication.
pub_type The publication type (for example, paper, review, erratum, abstract, book, etc.)
miniref A short citation listing the first author, year of publication, journal, volume, issue and page numbers.
pmid_added The FlyBase release in which the publication was first incorporated into the FlyBase bibliography. Note: as this report first generated for fb_2012_01 release, all publications associated with a Pub Med ID prior to this release have pmid_added = fb_2011_10.


Map conversion tables

Cytological <=> Sequence (genome-cyto-seq.txt)

This is a tab delimited file that FlyBase uses to relate sequence coordinates from release 5 of the Drosophila melanogaster sequence assembly to published cytogenetic map positions. A description of how this is calculated is provided in section G.5.1. of the Reference manual.

The data for each chromosome arm is separated by a line starting with a '#' that lists the name of the chromosome arm and corresponding sequence scaffold.

The columns in the file are:

Column heading Content Description
- Cytogenetic map position as described by Bridges.
- First sequence coordinate for this map position in the sequence scaffold corresponding this chromosome arm.
- Last sequence coordinate for this map position in the sequence scaffold corresponding this chromosome arm.


Cytological <=> Genetic (cytotable.txt)

This is the table that FlyBase uses to infer a genetic map position from a published cytogenetic map position for Drosophila melanogaster.

The first six lines of the file describe the contents of the file or are blank. The data in the file is organized with the cytological position in first four characters of a line followed by a run of spaces and then the genetic map position.


Cyto <=> Genetic <=> Seq (cyto-genetic-seq.tsv)

This is a tab separated file generated from the cytotable.txt and genome-cyto-seq.txt files that infers the relationship between published cytogenetic map positions, genetic map positions and release 6 sequence assembly coordinates for Drosophila melanogaster. Please note that band numbers are not given in this file because they are absent in cytotable.txt.

File format:

Column heading Content Description
Cytogenetic map position Cytogenetic map position.
Genetic map position Genetic map position.
Sequence coordinates (release 6) Sequence coordinates (release 6) for the interval.
R6 conversion notes


An html version of this file is also available - see the Map Conversion Table page.


Genes map table (gene_map_table_fb_*.tsv)

This is identical to the file listed under the genes section above.