Bio DAS Example Requests

For the DAS workshop this year and for general use we decided it would be a good idea to have a glossary/command summary showing examples of working commands that could be used on DAS servers and the registry. Before creating an all singing all dancing html page with this info I need a rough draft. I may as well make this available as i write it so people may find it useful. This is meant as an easy/quick reference summary only but for further details on the requests and responses that can be made please refer to Further examples can be found from you can filter on commands by choosing from the dropdown capability menu at the top, lights next to each datasource represent the validity of each command or capability as determined by the Das Registry. Click on a light to see the request and response for that server in your browser.

Section 1) The DAS Registry commands:

The DAS registry responds to a few commands:

sources, coordinatesystem, knownCapabilities, lastModified, validate

Note: that das/ can usually be replaced by das1/ and you will get the same results.

Note: also recently it is now possible to use ; as a parameter seperator as well as the & I’m not sure what the behaviour is if you mix these so i’d recommend using one seperator or the other in commands sent to the registry

sources commands (get DAS sources that have been registered with the registry):
* Get the sources document for a single DAS source with the registry id DS-111 held in the registry

* keywords parameter to sources cmds e.g.

* typeskeywords returns sources that have a type from their types command that matches the typeskeyword

* rows capability for the sources cmd Note: start, end attributes are added to the response if rows have been specified.
* request support for sources document for 1.6E compliant sources as apposed to 1.5 sources

* serverUrl filter option to the sources web service so for example you can now do in order to get the first 10 in the list of sources from the ensembl servers

* filter on coordinate system using organism and or authority, version etc

*filter on capability stated by the registrant, the response will tell you if the registry considers it a valid response or not using for example <PROP name=”stylesheet” value=”probably_valid”/>  (don’t use the das1: prefix)

*sort by the following parameters: id, nickname or title, status (ie. uses leasedate), registerdate, leasedate, url, adminemail, description, capabilities (user/server specified), validcapabilities (sorts on valid capabilities determined by the registry not user/server selected), coordinatesystem (sorts by the number of coordinate systems a source specifies).
* reverse=true parameter reverses the order of the above sorts.;reverse=true;rows=1-100

coordinatesystem commands (get coordinate systems that have been registered with the registry):

* get all coordinate systems known to the DAS registry

* capability of getting single coordinate system from coordinatesystem url e.g.

* keywords parameter to coordinatesystem command
* added total, start, end attributes to coordinatesystem request response if rows specified

knownCapaiblities (responds with the DAS capabilities that the registry is aware of and supports):


lastModified command (tells a client when the data on DAS sources was last updated and thus whether a client needs to make a new call to the registry):


validate command can be used to validate a server using the das registry and get back an xml sources response containing extra properties pertaining to the validity of specific capabilities:


Section 2) 1.6 Specification Server Commands:

sources command:

Request all sources from this server

Request a source from this server with the id ens_zfish7_array (functionality as of 1.6 specification)

entry_points command:

Get a list of the entry points for this reference DAS server (reference means it must return sequence for the entry points):

Due to the possibly large number of entry points for some servers as of 1.6 the rows parameter can be used to restrict this list to the first 10 rows (rows 1-10) currently as of writing I can’t find many servers that support this:

sequence command:

Get the sequence for segment P00280

Get the sequence for chromosome 33 from start=3000001 to stop=3100000,3100000

And the same for a genomic reference source:,50595866

Note that the UCSC uses different organism identifiers than the EBI/Sanger and also uses the old style dna command so to get sequence from the UCSC you would use:,50595866

types command:

Show the feature types that this data source contains

we should be able to filter these types based on a specific segment or range like,2000000 but many servers do not seem to support this? As of 1.6 they should.,15000 gives the number of types within the types element as 5 <TYPE id=”clone_genomic_insert” method=”smalt”>5</TYPE> restults in a type element like this with 5109 features of this type as it’s not restricted to a segment range <TYPE id=”clone_genomic_insert” method=”smalt”>5109</TYPE>

features command:

As this is probably the most commonly used command we will put the optional parameter string as stated by the specification:


and now for some examples:,29895696;,29895696;type=contig,29895696;segment=21:30000000,30030000;type=supercontig,29895696;maxbins=1000,29895696;segment=21:30000000,30030000;type=supercontig;feature_id=HSCHR21_CTG1_1


  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: