Schema for RNA-seq HME - Burge Lab RNA-seq 32mer Reads from HME (Human Mammary Epithelial) Cell Line

Database: hg19 Primary Table: burgeRnaSeqGemMapperAlignHME Row Count: 12,349,558
Format description: Browser extensible data

field	example	SQL type	description
`bin`	585	`smallint(5) unsigned`	Indexing field to speed chromosome range queries.
`chrom`	chr1	`varchar(255)`	Reference sequence chromosome or scaffold
`chromStart`	14924	`int(10) unsigned`	Start position in chromosome
`chromEnd`	14956	`int(10) unsigned`	End position in chromosome
`name`	GSM325485_HCT205_HME__13620...	`varchar(255)`	Name of item
`score`	1000	`int(10) unsigned`	Score from 0-1000
`strand`	-	`char(1)`	+ or -
`thickStart`	0	`int(10) unsigned`	Start of where display should be thick (start codon)
`thickEnd`	0	`int(10) unsigned`	End of where display should be thick (stop codon)
`reserved`	0	`int(10) unsigned`	Used as itemRgb as of 2004-11-22
`blockCount`	1	`int(10) unsigned`	Number of blocks
`blockSizes`	32,	`longblob`	Comma separated list of block sizes
`chromStarts`	0,	`longblob`	Start positions relative to chromStart

bin	chrom	chromStart	chromEnd	name	score	strand	blockCount	blockSizes	chromStarts
585	chr1	14924	14956	GSM325485_HCT205_HME__13620073_chr1_14925_14956	1000	-	1	32,	0,
585	chr1	16777	16809	GSM325485_HCT205_HME__15045000_chr1_16778_16809	1000	-	1	32,	0,
585	chr1	16781	16813	GSM325485_HCT205_HME__5509824_chr1_16782_16813	1000	+	1	32,	0,
585	chr1	16790	16822	GSM325485_HCT205_HME__15957773_chr1_16791_16822	1000	-	1	32,	0,
585	chr1	16792	16824	GSM325485_HCT205_HME__3189291_chr1_16793_16824	1000	-	1	32,	0,
585	chr1	17480	17512	GSM325485_HCT205_HME__1339949_chr1_17481_17512	1000	+	1	32,	0,
585	chr1	17480	17512	GSM325485_HCT205_HME__8246878_chr1_17481_17512	1000	+	1	32,	0,
585	chr1	17481	17513	GSM325485_HCT205_HME__17638186_chr1_17482_17513	1000	+	1	32,	0,
585	chr1	17484	17516	GSM325485_HCT205_HME__8798422_chr1_17485_17516	1000	+	1	32,	0,
585	chr1	17485	17517	GSM325485_HCT205_HME__12841045_chr1_17486_17517	1000	+	1	32,	0,

Note: all start coordinates in our database are 0-based, not 1-based. See explanation here.