This track contains information about a subset of the
single nucleotide polymorphisms
and small insertions and deletions (indels) — collectively Simple
Nucleotide Polymorphisms — from
build 142, available from
Only SNPs that have a minor allele frequency of at least 1% and
are mapped to a single location in the reference genome assembly are
included in this subset. Frequency data are not available for all SNPs,
so this subset is incomplete.
The selection of SNPs with a minor allele frequency of 1% or greater
is an attempt to identify variants that appear to be reasonably common
in the general population. Taken as a set, common variants should be
less likely to be associated with severe genetic diseases due to the
effects of natural selection,
following the view that deleterious variants are not likely to become
common in the population.
However, the significance of any particular variant should be interpreted
only by a trained medical geneticist using all available information.
The remainder of this page is identical on the following tracks:
Common SNPs(142) - SNPs with >= 1% minor allele frequency (MAF), mapping
only once to reference assembly.
Mult. SNPs(142) - SNPs mapping in more than one place on reference assembly.
All SNPs(142) - all SNPs from dbSNP mapping to reference assembly.
Interpreting and Configuring the Graphical Display
Variants are shown as single tick marks at most zoom levels.
When viewing the track at or near base-level resolution, the displayed
width of the SNP corresponds to the width of the variant in the reference
sequence. Insertions are indicated by a single tick mark displayed between
two nucleotides, single nucleotide polymorphisms are displayed as the width
of a single base, and multiple nucleotide variants are represented by a
block that spans two or more bases.
On the track controls page, SNPs can be colored and/or filtered from the
display according to several attributes:
Class: Describes the observed alleles
Single - single nucleotide variation: all observed alleles are single nucleotides
(can have 2, 3 or 4 alleles)
Microsatellite - the observed allele from dbSNP is a variation in counts of short tandem repeats
Named - the observed allele from dbSNP is given as a text name instead of raw sequence, e.g., (Alu)/-
No Variation - the submission reports an invariant region in the surveyed sequence
Mixed - the cluster contains submissions from multiple classes
Multiple Nucleotide Polymorphism (MNP) - the alleles are all of the same length, and length > 1
Insertion - the polymorphism is an insertion relative to the reference assembly
Deletion - the polymorphism is a deletion relative to the reference assembly
Unknown - no classification provided by data contributor
Validation: Method used to validate
the variant (each variant may be validated by more than one method)
By Frequency - at least one submitted SNP in cluster has frequency data submitted
By Cluster - cluster has at least 2 submissions, with at least one submission assayed with a non-computational method
By Submitter - at least one submitter SNP in cluster was validated by independent assay
By 2 Hit/2 Allele - all alleles have been observed in at least 2 chromosomes
By HapMap (human only) - submitted by HapMap project
By 1000Genomes (human only) - submitted by
Unknown - no validation has been reported for this variant
Function: dbSNP's predicted functional effect of variant on RefSeq transcripts,
both curated (NM_* and NR_*) as in the RefSeq Genes track and predicted (XM_* and XR_*),
not shown in UCSC Genome Browser.
A variant may have more than one functional role if it overlaps
These terms and definitions are from the Sequence Ontology (SO); click on a term to view it in the
MISO Sequence Ontology Browser.
Unknown - no functional classification provided (possibly intergenic)
A sequence variant where there is no resulting change to the encoded amino acid
(dbSNP term: coding-synon)
A transcript variant occurring within an intron
(dbSNP term: intron)
A sequence variant whereby at least one base of a codon is changed, resulting in
a premature stop codon, leading to a shortened transcript
(dbSNP term: nonsense)
A sequence variant, where the change may be longer than 3 bases, and at least
one base of a codon is changed resulting in a codon that encodes for a
different amino acid
(dbSNP term: missense)
A sequence variant where at least one base of the terminator codon (stop)
is changed, resulting in an elongated transcript
(dbSNP term: stop-loss)
A sequence variant which causes a disruption of the translational reading frame,
because the number of nucleotides inserted or deleted is not a multiple of three
(dbSNP term: frameshift)
A coding sequence variant where the change does not alter the frame
of the transcript
(dbSNP term: cds-indel)
Genomic - variant discovered using a genomic template
cDNA - variant discovered using a cDNA template
Unknown - sample type not known
Unusual Conditions (UCSC): UCSC checks for several anomalies
that may indicate a problem with the mapping, and reports them in the
Annotations section of the SNP details page if found:
AlleleFreqSumNot1 - Allele frequencies do not sum
to 1.0 (+-0.01). This SNP's allele frequency data are
MixedObserved - Multiple distinct insertion SNPs have
been mapped to this location, with either the same inserted
sequence (Duplicate) or different inserted sequence (Mixed).
FlankMismatchGenomeShorter - NCBI's alignment of
the flanking sequences had at least one mismatch or gap
near the mapped SNP position.
(UCSC's re-alignment of flanking sequences to the genome may
MultipleAlignments - This SNP's flanking sequences
align to more than one location in the reference assembly.
NamedDeletionZeroSpan - A deletion (from the
genome) was observed but the annotation spans 0 bases.
(UCSC's re-alignment of flanking sequences to the genome may
NamedInsertionNonzeroSpan - An insertion (into the
genome) was observed but the annotation spans more than 0
bases. (UCSC's re-alignment of flanking sequences to the
genome may be informative.)
NonIntegerChromCount - At least one allele
frequency corresponds to a non-integer (+-0.010000) count of
chromosomes on which the allele was observed. The reported
total sample count for this SNP is probably incorrect.
ObservedContainsIupac - At least one observed allele
from dbSNP contains an IUPAC ambiguous base (e.g., R, Y, N).
ObservedMismatch - UCSC reference allele does not
match any observed allele from dbSNP. This is tested only
for SNPs whose class is single, in-del, insertion, deletion,
mnp or mixed.
ObservedTooLong - Observed allele not given (length
ObservedWrongFormat - Observed allele(s) from dbSNP
have unexpected format for the given class.
RefAlleleMismatch - The reference allele from dbSNP
does not match the UCSC reference allele, i.e., the bases in
the mapped position range.
RefAlleleRevComp - The reference allele from dbSNP
matches the reverse complement of the UCSC reference
SingleClassLongerSpan - All observed alleles are
single-base, but the annotation spans more than 1 base.
(UCSC's re-alignment of flanking sequences to the genome may
SingleClassZeroSpan - All observed alleles are
single-base, but the annotation spans 0 bases. (UCSC's
re-alignment of flanking sequences to the genome may be
Another condition, which does not necessarily imply any problem,
SingleClassTriAllelic, SingleClassQuadAllelic -
Class is single and three or four different bases have been
observed (usually there are only two).
Miscellaneous Attributes (dbSNP): several properties extracted
from dbSNP's SNP_bitfield table
(see dbSNP_BitField_v5.pdf for details)
Clinically Associated (human only) - SNP is in OMIM and/or at
least one submitter is a Locus-Specific Database. This does
not necessarily imply that the variant causes any disease,
only that it has been observed in clinical studies.
Has Microattribution/Third-Party Annotation - At least
one of the SNP's submitters studied this SNP in a biomedical
setting, but is not a Locus-Specific Database or OMIM/OMIA.
Submitted by Locus-Specific Database - At least one of
the SNP's submitters is associated with a database of variants
associated with a particular gene. These variants may or may
not be known to be causative.
MAF >= 5% in Some Population - Minor Allele Frequency is
at least 5% in at least one population assayed.
MAF >= 5% in All Populations - Minor Allele Frequency is
at least 5% in all populations assayed.
Genotype Conflict - Quality check: different genotypes
have been submitted for the same individual.
Ref SNP Cluster has Non-overlapping Alleles - Quality
check: this reference SNP was clustered from submitted SNPs
with non-overlapping sets of observed alleles.
Some Assembly's Allele Does Not Match Observed -
Quality check: at least one assembly mapped by dbSNP has an allele
at the mapped position that is not present in this SNP's observed
Several other properties do not have coloring options, but do have
some filtering options:
Average heterozygosity should not exceed 0.5 for bi-allelic
Weight: Alignment quality assigned by dbSNP
Weight can be 0, 1, 2, 3 or 10.
Weight = 1 are the highest quality alignments.
Weight = 0 and weight = 10 are excluded from the data set.
A filter on maximum weight value is supported, which defaults to 1
on all tracks except the Mult. SNPs track, which defaults to 3.
Submitter handles: These are short, single-word identifiers of
labs or consortia that submitted SNPs that were clustered into this
reference SNP by dbSNP (e.g., 1000GENOMES, ENSEMBL, KWOK). Some SNPs
have been observed by many different submitters, and some by only a
single submitter (although that single submitter may have tested a
large number of samples).
AlleleFrequencies: Some submissions to dbSNP include
allele frequencies and the study's sample size
(i.e., the number of distinct chromosomes, which is two times the
number of individuals assayed, a.k.a. 2N). dbSNP combines all
available frequencies and counts from submitted SNPs that are
clustered together into a reference SNP.
You can configure this track such that the details page displays
the function and coding differences relative to
particular gene sets. Choose the gene sets from the list on the SNP
configuration page displayed beneath this heading: On details page,
show function and coding differences relative to.
When one or more gene tracks are selected, the SNP details page
lists all genes that the SNP hits (or is close to), with the same keywords
used in the function category. The function usually
agrees with NCBI's function, except when NCBI's functional annotation is
relative to an XM_* predicted RefSeq (not included in the UCSC Genome
Browser's RefSeq Genes track) and/or UCSC's functional annotation is
relative to a transcript that is not in RefSeq.
dbSNP uses a class called 'in-del'. We compare the length of the
reference allele to the length(s) of observed alleles; if the
reference allele is shorter than all other observed alleles, we change
'in-del' to 'insertion'. Likewise, if the reference allele is longer
than all other observed alleles, we change 'in-del' to 'deletion'.
UCSC Re-alignment of flanking sequences
dbSNP determines the genomic locations of SNPs by aligning their flanking
sequences to the genome.
UCSC displays SNPs in the locations determined by dbSNP, but does not
have access to the alignments on which dbSNP based its mappings.
Instead, UCSC re-aligns the flanking sequences
to the neighboring genomic sequence for display on SNP details pages.
While the recomputed alignments may differ from dbSNP's alignments,
they often are informative when UCSC has annotated an unusual condition.
Non-repetitive genomic sequence is shown in upper case like the flanking
sequence, and a "|" indicates each match between genomic and flanking bases.
Repetitive genomic sequence (annotated by RepeatMasker and/or the
Tandem Repeats Finder with period <= 12) is shown in lower case, and matching
bases are indicated by a "+".
Coordinates, orientation, location type and dbSNP reference allele data
were obtained from b142_SNPContigLoc.bcp.gz and
b142_SNPMapInfo.bcp.gz provided the alignment weights.
Functional classification was obtained from
b142_SNPContigLocusId.bcp.gz. The internal database representation
uses dbSNP's function terms, but for display in SNP details pages,
these are translated into
Sequence Ontology terms.
Validation status and heterozygosity were obtained from SNP.bcp.gz.
SNPAlleleFreq.bcp.gz and ../shared/Allele.bcp.gz provided allele frequencies.
For the human assembly, allele frequencies were also taken from
Submitter handles were extracted from Batch.bcp.gz, SubSNP.bcp.gz and
SNP_bitfield.bcp.gz provided miscellaneous properties annotated by dbSNP,
such as clinically-associated. See the document
dbSNP_BitField_v5.pdf for details.
The header lines in the rs_fasta files were used for molecule type,
class and observed polymorphism.
Note: It is not recommeneded to use LiftOver to convert SNPs between assemblies,
and more information about how to convert SNPs between assemblies can be found on the following
FASTA files that have been modified to use
ambiguous nucleotide characters at
each base covered by a single-base substitution are available for download:
Note that only single-base substitutions (no insertions or deletions) were used
to mask the sequence, and these were filtered to exclude problematic SNPs.