Hello, As directed by previous helpful advice from this list, my lab has decided to go the route of converting client-side wiggle tracks to bigWig files, and specifying the bigWigs in links through the bigDataUrl.
When using the same methodology for .wig and bedGraph file types, gzipped (.gz) file contents would load in the genome browser with no problem. We set up links of the form: http://genome.ucsc.edu/cgi-bin/hgTracks?db=hg19...(rest of browser line)...&hgct_customText=https://webserver.domain/link_text/text_file.txt The text file specifed by hgct_customText is of the form: track type=bigWig name="trackName" description="descr" color=209,46,155 visibility=full horizGrid=on...(rest of track line)... bigDataUrl=https://webserver.domain/data/data.bigWig.gz When the bigDataUrl specifies a gizzped bigWig file, the browser reports that "https://webserver.domain/data/data.bigWig.gz is not a big wig file". When the same file is un-gzipped and specified in the same way, it loads without error. Is there some way to specify a gizpped bigWig file in the bigDataUrl, or are we limited to uncompressed bigWigs? thanks, Rebecca Hudson _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
