You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'm working on a project where i'm utilising the gene2transcripts_v2 API to generate a BED file of GRCh38 MANE transcript exon coordinates for a list of genes.
I'm able to use the genomic_start and genomic_end coordinates within the exon structure results to achieve this, however, it would be good to have the ability to exclude UTR's and non-coding exons.
Describe the solution you'd like
Having coding sequence (cds) genomic start/end positions for each exon (where applicable) in the output, in addition to the existing genomic_start and genomic_end. (Equivalent to the CDS and exon values in refseq GTF file).
Describe alternatives you've considered
I'm able to retrieve this cds information from the NCBI refseq GTF file using a custom script but it would be nice to have in VariantValidator.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I'm working on a project where i'm utilising the gene2transcripts_v2 API to generate a BED file of GRCh38 MANE transcript exon coordinates for a list of genes.
I'm able to use the genomic_start and genomic_end coordinates within the exon structure results to achieve this, however, it would be good to have the ability to exclude UTR's and non-coding exons.
Describe the solution you'd like
Having coding sequence (cds) genomic start/end positions for each exon (where applicable) in the output, in addition to the existing genomic_start and genomic_end. (Equivalent to the CDS and exon values in refseq GTF file).
Describe alternatives you've considered
I'm able to retrieve this cds information from the NCBI refseq GTF file using a custom script but it would be nice to have in VariantValidator.
Additional context
The text was updated successfully, but these errors were encountered: