Genomic Data Commons (GDC)

The Genomic Data Commons (GDC) is a data repository and analysis platform operated by the National Cancer Institute (NCI), part of the National Institutes of Health. It hosts harmonized genomic, transcriptomic, and clinical data from major NCI cancer sequencing programs — most notably The Cancer Genome Atlas (TCGA) and Therapeutically Applicable Research to Generate Effective Treatments (TARGET) — alongside data submitted directly by individual research projects.

What makes the GDC distinct from a general sequence archive

Unlike a raw-deposit archive such as dbGaP or GenBank, the GDC’s defining feature is its harmonization pipeline: every submitted dataset, regardless of which study or sequencing center produced it, is reprocessed through a common bioinformatics pipeline — aligned to the same reference genome build, run through the same variant-calling and expression-quantification workflows, and standardized against common clinical and biospecimen data dictionaries. This means a researcher comparing TCGA breast-cancer samples against a newer, independently submitted cohort is comparing data that were processed identically, not just data that happen to sit in the same database. That harmonization is what makes cross-study, pan-cancer analysis at the GDC practical in a way that pooling raw files from disparate submissions would not be.

Access tiers

Like dbGaP, the GDC splits data into two access tiers. Open-access data — de-identified clinical metadata, biospecimen annotations, and molecular data that cannot reasonably be used to re-identify a participant (e.g. gene-expression quantification, some somatic mutation calls) — is available to anyone without an application. Controlled-access data — raw sequence reads and germline variant calls that carry re-identification risk — requires the same eRA Commons-linked dbGaP Data Access Request process used for other NIH-designated controlled-access repositories, since the GDC interfaces directly with dbGaP’s authorization system rather than running a separate access-committee process of its own.

How researchers use it

The GDC exposes three access paths built for different use cases: the GDC Data Portal, a web interface for browsing, filtering, and visualizing cohorts by project, disease type, or molecular feature; the GDC API, a programmatic interface for querying metadata and retrieving files inside analysis pipelines and scripts; and the GDC Data Transfer Tool, a high-throughput client for bulk-downloading large controlled-access file sets that would be impractical over a browser.

Examples

• A cancer biology researcher uses the GDC Data Portal to filter TCGA lung adenocarcinoma cases by a specific somatic mutation, then downloads the matched harmonized RNA-seq expression data for those cases — all open-access, no application required.
• A biostatistician building a pan-cancer survival model submits a dbGaP Data Access Request (their institution’s Signing Official co-signs) to obtain controlled-access germline variant calls across several GDC-hosted TCGA cohorts, since germline genotypes carry re-identification risk that the open-access tier excludes.

Counter-example

A single-lab RNA-seq dataset that has not been submitted to and reprocessed by the GDC pipeline is not “GDC data” merely because it concerns cancer — it belongs in a general-purpose repository such as the Gene Expression Omnibus unless and until it is formally deposited and harmonized through the GDC’s own submission process.

Related infrastructure

The GDC is one of several domain-specific data commons that pair a curated dataset with co-located compute and an explicit governance layer, in the sense set out by Grossman et al.’s 2016 “A Case for Data Commons.” Cancer researchers evaluating where to deposit or find harmonized genomic data should also be aware of GEO for functional genomics results and dbGaP for the underlying controlled-access authorization mechanics the GDC relies on.