586a03e6ff6d676406d62106ae7e2e8539f52a4d dschmelt Tue Feb 4 11:22:26 2020 -0800 Documenting GTF downloads directory #20867 diff --git src/hg/htdocs/FAQ/FAQformat.html src/hg/htdocs/FAQ/FAQformat.html index 5b3d43f..720cb5f 100755 --- src/hg/htdocs/FAQ/FAQformat.html +++ src/hg/htdocs/FAQ/FAQformat.html @@ -454,31 +454,31 @@ <strong>seqname</strong> - The name of the sequence. Must be a chromosome or scaffold.</li> <li> <strong>source</strong> - The program that generated this feature.</li> <li> <strong>feature</strong> - The name of this type of feature. Some examples of standard feature types are "CDS" "start_codon" "stop_codon" and "exon"li> <li> <strong>start</strong> - The starting position of the feature in the sequence. The first base is numbered 1.</li> <li> <strong>end</strong> - The ending position of the feature (inclusive).</li> <li> <strong>score</strong> - A score between 0 and 1000. If the track line <em>useScore</em> attribute is set to 1 for this annotation data set, the <em>score</em> value will determine the level of gray in which this feature is displayed (higher numbers = darker gray). If there is no score - value, enter ":.":. + value, enter ".". <li> <strong>strand</strong> - Valid entries include "+", "-", or "." (for don't know/don't care).</li> <li> <strong>frame</strong> - If the feature is a coding exon, <em>frame</em> should be a number between 0-2 that represents the reading frame of the first base. If the feature is not a coding exon, the value should be ".".</li> <li> <strong>group</strong> - All lines with the same group are linked together into a single item.</li> </ol> <p> <strong><em>Example:</em></strong><br> Here's an example of a GFF-based track. This data format require tabs and some operating systems convert tabs to spaces. If pasting doesn't work, this <a href="../goldenPath/help/regulatory.txt" target="blank">example's</a> contents or the url itself can be pasted into the custom track text box.