Why Does Ucsc "Exons" Track Overlap With "Introns" Track?
1
4
Entering edit mode
12.2 years ago
Pascal ★ 1.5k

I've downloaded BED files from UCSC Table Browser for the "Exons" track and for the "Introns" track. But I just discovered that these BED files have some overlaps ?!

alt text

Could you please explain me where these overlap come from?

ucsc browser • 4.5k views
ADD COMMENT
1
Entering edit mode

The visual example of what you are referring to is really great for these kinds of questions.

ADD REPLY
10
Entering edit mode
12.2 years ago

The reason is that both introns and exons will be defined in UCSC relative to transcripts and not the overall gene. If you grab the introns and exons for a single transcript you should not see these types of overlaps. But if you take all of the exons for all of the transcripts of a gene you will often see them.

If you truly want your exon and intron BEDs to occupy mutually exclusive space in the genome, you will need to do some extra work. For example you could:

  1. Start with the exons BED file from UCSC.
  2. Use BEDTools to merge overlapping exons in this file. The resulting merged exons for each gene make a sort of 'fake' transcript. Some people refer to these as the 'exon content' of a gene, the 'squashed' transcriptome, etc. Think about how you want to deal with transcripts that overlap on opposite strands at this point.
  3. Now you can extract intron coordinates for each gene using the merged/squashed exons. You should also be able to do this with BEDTools where you have one BED file containing your squashed exons and another containing the outer boundaries of each gene.
ADD COMMENT
2
Entering edit mode

+1. And you can see this in the browser if you set the gene track to visibility full so it shows the various transcripts.

ADD REPLY
0
Entering edit mode

Excellent. Thank you so much for the explanation!

ADD REPLY

Login before adding your answer.

Traffic: 1970 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6