This repository has been archived by the owner on Oct 28, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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