Additional resources
The Genome Browser supports three varieties of data filter options for bigBed data. These can improve data usability in many ways, such as displaying specific data by default (e.g. only items that pass certain quality scores), allow for filtering based on pre-specified categories (e.g designate only LINE repetitive elements from a list of options) and more.
For more information on the options available and examples on how to set up filters, see our Track Hub Filters Quick Start Guide and the filter entries in the Track Database Definition Document.
+ + ++Track Hubs also support the use of include statements, which allow one to insert a file +containing a set of trackDb stanzas into the primary trackDb. This can be useful when you +have a hub where you have the same track across several assemblies, e.g. you're creating +a new gene annotation pipeline and have generated predictions across several species to +compare. You can also use include statements for breaking up large, complex track configurations, +such as those with several large container tracks. You can put the trackDb configuration stanzas for each container +track into a separate file and then use an include statement in the primary trackDb.txt +to pull them all into your hub. Include statements also function with the +useOneFile setting.
+ +Here's an example of what your hub directory structure might look like: +
myHub/ - directory containing track hub files
+
+hub.txt
+genomes.txt
+trackDb.geneAnnotations.txt
+hg38/
+ trackDb.txt
+ gene_annotations.bigBed
+ trackDb.cell_type_rnaseq.txt
+ rnaseq_files/
+ ...
+mm10/
+ trackDb.txt
+ gene_annotations.bigBed
+
+To include these two trackDb files for hg38, you would add
+the following lines to your hg38/trackDb.txt:
+
include ../trackDb.geneAnnotations.txt
+include trackDb.cell_type_rnaseq.txt
+Note: Using include statements may cause slower load times on high-latency +connections due to our software checking the time of all included files. +If this is the case, you should avoid include statements and instead concatenate your +trackDb files. This shouldn't be a problem on low-latency connections. +
+If you would like to share your track hub with other Genome Browser users, you can register your hub with UCSC by contacting the Genome Browser technical support mailing list at genome@soe.ucsc.edu. Please include the URL of your hub.txt file in the message. Once registered, your hub will appear as a link on the Public Hubs tab on the Track Hubs page. To assist developers of Public Hubs, there is a Public Hub Guidelines page. The page shares pointers and preferred style approaches, such as the need for creating description html pages for your data that display any available references and an email contact for further data questions.
Alternatively, you can share your track hub with selected colleagues by providing them with the URL