e550e8c40e6139e4570787293063d11c7c40430d dschmelt Mon Dec 20 10:55:55 2021 -0800 Fixing broken link No Rm diff --git src/hg/htdocs/goldenPath/help/api.html src/hg/htdocs/goldenPath/help/api.html index 171beef..8fbe510 100755 --- src/hg/htdocs/goldenPath/help/api.html +++ src/hg/htdocs/goldenPath/help/api.html @@ -317,33 +317,33 @@

Practical examples

Looking up the schema of a specific track

The easiest way to get the schema for a track is to use the /list/schema function. This can be used on both file tracks and table tracks:

-Request schema for the hg38 CRISPR 10K Targets track - -
api.genome.ucsc.edu/list/schema?genome=hg38;track=crispr10KTargets

+Request schema for the hg38 CRISPR Targets track - +
api.genome.ucsc.edu/list/schema?genome=hg38;track=crisprAllTargets

There is a second indirect way to get the schema which may be preferable in certain cases. When querying track data with the /getData/track function, the jsonOutputArrays can be used in conjunction to see the track schema. This includes a description of each field present in the track. The data will also be returned in JSON array type.

Request data from hg38 gold track in array type -
api.genome.ucsc.edu/getData/track?genome=hg38;track=gold;chrom=chrM;jsonOutputArrays=1

Hide track container information with trackLeavesOnly parameter