[ensembl-dev] transcript coordinates via REST?
mag
mr6 at ebi.ac.uk
Fri Jul 31 10:38:40 BST 2015
Hi Reece,
It is currently not straightforward to link between GRCh37 and GRCh38
resources, which is why we have a dedicated GRCh37 REST server.
http://grch37.rest.ensembl.org
It is possible to map a location from GRCh37 to GRCh38 and vice-versa
via the mapping endpoint
for example:
http://rest.ensembl.org/map/human/GRCh37/X:1000000..1000100:1/GRCh38?content-type=application/json
And a similar endpoint can provide you with transcript coordinates
translated to genomic coordinates, although the reverse is not available
http://rest.ensembl.org/map/cdna/ENST00000288602/100..300?content-type=application/json
I am not sure if that covers your use case, so please don't hesitate to
give us some feedback.
The REST API is still in active development and we are always happy to
get some feature requests that allow us to prioritise future endpoints.
Regards,
Magali
On 30/07/2015 21:46, Reece Hart wrote:
> Hi-
>
> Is there a way to get transcript coordinates via the REST interface
> for both GRCh37 and 38? Or, more specifically, is there any way other
> than via the perl interface?
>
>
> I'm imaging/hope for something akin to
>
> http://rest.ensembl.org/overlap/id/ENSG00000157764?feature=transcript
>
> returning something like:
>
> {'Parent': 'ENSG00000271932',
> 'biotype': 'snRNA',
> 'feature_type': 'transcript',
> 'id': u'ENST00000605989',
> 'coordinates': {
> 'NC_000007.10' : { 'strand': -1, 'start_end':
> [[140696671,140696671], [140696671,140696671]...]},
> 'ENST00000605989' : { 'strand': 1, 'start_end': [[10,20],
> [20,30]...]},
> },
> }]
>
> Thanks,
> Reece
>
>
> _______________________________________________
> Dev mailing list Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info: http://lists.ensembl.org/mailman/listinfo/dev
> Ensembl Blog: http://www.ensembl.info/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20150731/880e1379/attachment.html>
More information about the Dev
mailing list