9a051963c7dc7cafea316417701cae4570aff029 braney Sun Jul 13 13:07:07 2025 -0700 templates for bedMethyl and bigMethyl diff --git src/hg/htdocs/goldenPath/help/customTrackText.html src/hg/htdocs/goldenPath/help/customTrackText.html index f2a2506ed07..6e17315fdce 100755 --- src/hg/htdocs/goldenPath/help/customTrackText.html +++ src/hg/htdocs/goldenPath/help/customTrackText.html @@ -54,30 +54,31 @@ Format your data as a tab-separated file using one of the formats supported by the Genome Browser. You may include more than one data set in your annotation file; these need not be in the same format. For many formats, chromosome names can either be UCSC-style names (e.g. 'chr1', 'chrX') or aliases from other sources (e.g. '1' or 'NC_000001.11'). Annotation data can be in a format designed specifically for the Human Genome Project or UCSC Genome Browser, including:
If you would like to share a URL that your colleague can click on directly, rather than loading it
in the Custom Track tool (as in Example #5), then the URL will need a few extra parameters. Let's
assume that your data is on a server at your institution in one of the large data formats:
bigBed,
bigWig,
bigPsl,
bigBarChart,
bigChain,
bigInteract,
bigGenePred,
bigMaf,
bigNarrowPeak,
+bigMethyl,
BAM,
CRAM, or
VCF.
In this case, the URL must include an hgct_customText
parameter, which
simulates the text box on the Custom Tracks page. Also, the URL must include
the bigDataUrl
that points to the data file on your server.
So, a clickable URL that opens a remote bigBed track for the hg18 assembly to a certain location on
chr21 would look like this:
http://genome.ucsc.edu/cgi-bin/hgTracks?db=hg18&position=chr21:33038447-33041505&hgct_customText
=track%20type=bigBed%20name=myBigBedTrack%20description=%22a%20bigBed%20track%22%20visibility=
full%20bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigBedExample.bb
Tip: Multiple tracks can be placed into one custom track submission. To do so,