The name of the track, as shown in the tier-identification tab.
A longer description of the content, shown when clicking on the tier-identification tab. Currently only
plain text supported -- should probably allow a subset of HTML as well (TBD).
If true, the source is disabled by default (can be manually re-enabled from the
URI of a DAS Stylesheet
to use when displaying this data. For DAS sources, this overrides the source's default stylesheet.
For other sources, this allows richer style configuration. More information about Dalliance's implementation
of DAS stylesheets can be found here.
Disable any feature info plugins that would normally be added by the data source for this tier.
Configuring a DAS source
Base URI for the DAS server. Used to construct URIs for requesting features, sequence, and
(if not over-ridden) stylesheets. e.g.
Setting this to the string 'sequence' indicates that this should be a DAS sequence
tier rather than a DAS features tier.
Enables/disables the maxbins DAS extension for server-side downsampling
of quantitative data. Default is true.
Configuring a binary sequence source
URI for the .2bit sequence file. Alternatively, twoBitBlob can be used to configure
a local file as the sequence source.
Setting this to the string 'sequence' indicates that this is a sequence tier.
Configuring a bigwig or bigbed source
BigWig and BigBed files are configured in the same manner -- Dalliance automatically distinguished between
the two when loading. big* sources are recognized by the presence of a bwgURI option in
The URI for the big* file. Despite the name, this can be used with both BigWig and BigBed files.
Takes an integer parameter. Forces one of the 'reduced' forms of the data to be used. 0=first reduction, 1=second reduction, etc.
Alternatively, a value less than zero can be used to ensure that reduced data is never used.
Enables leap-by-threshold functionality. Takes a numerical parameter which is the default threshold.
Configuring a BAM source
Dalliance can directly view BAM files so long as they're sorted and indexed. BAM source configurations are recognized by
the presence of a bamURI option.
URI of a BAM file to access. e.g.
Explicitly specify the URI for the BAM index (.bam.bai) file. If not specified, Dalliance tries appending '.bai' to the value
of the bamURI parameter.
Configuring a Tabix source
Dalliance can access Tabix-indexed flatfiles. Currently supported payloads are VCF and BED, but other
formats may be added in future.
Configuring a Memstore source
Dalliance can directly access small textual files (currently supported formats are VCF, BED, and WIG -- more may be
added in future). Since these don't support random access, the whole file will be loaded when the track is initialized,
hence "memory store" (memstore). Configuration is very similar to tabix