de3f246c3afa00a564857dad74803c994e9ac22d steve Fri Jan 6 13:46:05 2012 -0800 Merging file format docs. Changed link to point to new location. diff --git src/utils/userApps/bigBedWigs.txt src/utils/userApps/bigBedWigs.txt index 4043f24..d90f68b 100644 --- src/utils/userApps/bigBedWigs.txt +++ src/utils/userApps/bigBedWigs.txt @@ -53,31 +53,31 @@ BIGBED - BigBed files store annotation items that can either be simple, or a linked collection of exons, much as bed files do. BigBed files in fact are created initially from bed files, using the program bedToBigBed. The resulting bigBed files are in an indexed binary format. The main advantage of the bigBed files is that only the portions of the files needed to display a particular region are transfered to UCSC, so for large data sets bigBed is considerably faster than straight bed. The steps for creating a bigBed track are: 1) Download bedToBigBed from the directory of binary utilities: http://genome-test.cse.ucsc.edu/admin/exe/linux.x86_64/ 2) Use the fetchChromSizes script from this same directory to fetch the chrom.sizes file for the UCSC database you are working with. 3) Create bed format files following the definitions in: - http://genome.ucsc.edu/goldenPath/help/customTrack.html#BED + http://genome.ucsc.edu/FAQ/FAQformat.html#format1 4) Run the command line bedToBigBed input.bed.gz chrom.sizes myBigBed.bb if your input.bed.gz file has 'track' and 'browser' lines: zcat input.bed.gz | egrep -v "^track|^browser" \ bedToBigBed stdin chrom.sizes myBigWig.bb make sure you do not have more than one track of data in your input file. 5) Move the output bigBed file to a http, https, or ftp site. 6) Create a custom track with just the track line. This will look something like: track type=bigBed name="My Big Bed" description="Cool Genome Annotations from My Lab" bigDataUrl=http://myorg.edu/mylab/myBigBed.bb (track lines are single lines, no line breaks are allowed) 7) Paste this custom track line into the text box in the custom track management page: