A common concern prospective API users have raised is that we do well interchanging low level data, but most times an application won't make use of it. A very common case is returning binned counts of elements over a genomic region. Some visualizers will make counts of elements themselves at the client-side, however, because of network transfer costs oftentimes one might just want the counts and not the data themselves.
These coverage bins provide a data model for read depth, variation density, or genomic feature density. With the addition of this endpoint, existing genomic data can be rendered in visualizers much more effectively. Thanks @akmorrow13!
Remove info from bin
Add more comments
Renamed width to bin_width in CoverageRequest
A common concern prospective API users have raised is that we do well interchanging low level data, but most times an application won't make use of it. A very common case is returning binned counts of elements over a genomic region. Some visualizers will make counts of elements themselves at the client-side, however, because of network transfer costs oftentimes one might just want the counts and not the data themselves.
These coverage bins provide a data model for read depth, variation density, or genomic feature density. With the addition of this endpoint, existing genomic data can be rendered in visualizers much more effectively. Thanks @akmorrow13!
Remove info from bin Add more comments Renamed width to bin_width in CoverageRequest