add cart choropleth column cross cube error file folder geo help home lock obs poi rdf remove search slice spreadsheet success table unlock warning

[this is a icon-] developer tool

SPARQL 1.1 Query: Results

Edit query
Query results
s p_blank o_blank geosparql: Geometry geosparql: asWKT POLYGON ((-2.575215009366567 56.5749496374702, -2.573696074946829 56.57845611249796, -2.572446109831029 56.57845701682417, -2.572865298078146 56.57734930882541, -2.570219000169452 56.577226185874785, -2.57161013390209 56.57586365263239, -2.573463371081905 56.57599842944548, -2.573752271894374 56.5750119993043, -2.572507683103046 56.574885778397544, -2.572569214302848 56.572828337880814, -2.568487227368738 56.57224603322171, -2.569443970089611 56.570504551288415, -2.5676503570339 56.57195316954488, -2.558883871549975 56.565254209542886, -2.564774684783516 56.56418542784911, -2.563181381563581 56.563626668561945, -2.564354142672801 56.56326198351149, -2.56374399346806 56.56271672963038, -2.56985534739037 56.56111363110354, -2.570751258083385 56.561973928591904, -2.568609287783829 56.56229824592614, -2.567967873508556 56.5629336444424, -2.57032101668378 56.56217639123337, -2.570546232369759 56.56245343578623, -2.573949735860428 56.56189739645007, -2.575140815508344 56.56211649037664, -2.57242314311848 56.563162202977445, -2.574213254252108 56.56384605382744, -2.574769567316337 56.56338495367549, -2.576164390661284 56.56522920694421, -2.577767977291124 56.56581470828186, -2.580394541259219 56.565191558928326, -2.579735879901621 56.564682543864954, -2.580562780732918 56.56449001772611, -2.580959539290651 56.56541361182675, -2.579469899331524 56.56611631679318, -2.579462384838715 56.56669925996674, -2.580196322586171 56.56712405194092, -2.580265141714722 56.56658216616437, -2.581102238611734 56.567215901513826, -2.578259259841125 56.56921736844114, -2.579128714647961 56.569671508637725, -2.577128151451932 56.57188190055541, -2.576443553850496 56.571813200459516, -2.575215009366567 56.5749496374702))
SPARQL API: The Basics

The most flexible way to access the data is by using SPARQL, a query language, analagous to SQL for relational databases, for retrieving and manipulating data from graph databases like ours. We support SPARQL 1.1 query syntax. Many online tutorials are available.

To submit a SPARQL query from your code, you issue an HTTP GET or POST to our endpoint:, with the query itself as a url-encoded parameter called query.

For example, to run the following simple SPARQL query and get the results as JSON:

SELECT * WHERE {?s ?p ?o} LIMIT 10

Option 1: POST (recommended)

Issue a POST to the endpoint, with the query in the body, and an Accept header of sparql-results+json:

Accept: application/sparql-results+json
Content-Type: application/x-www-form-urlencoded


Option 2: GET

Issue a GET to the following URL (note the .json extension - see the formats section for more detail on this):


Scroll down to the end of this page for examples of both of these methods in a few different languages.

Results formats

As with other aspects of our API, to get the data in different formats, you can use either (a) a format extension or (b) an HTTP Accept header. Available result formats depend on the type of SPARQL query. There are four main forms:

SELECT queries return tabular results, and the formats available reflect this:

Format Extensions Accept Headers
XML .xml application/xml,
JSON .json application/json,
Text .txt, .text text/plain
CSV .csv text/csv

CONSTRUCT and DESCRIBE queries return graph data, so the results are available in the same formats as our resource APIs:

Format Extensions Accept Headers
RDF/XML .rdf application/rdf+xml
N-triples .nt, .txt, .text application/n-triples,
Turtle .ttl text/turtle
JSON-LD .json application/ld+json,

ASK queries return a boolean result:

Format Extensions Accept Headers
XML .xml application/xml,
JSON .json application/json,
Text .txt, .text text/plain
Results pagination

We accept page and per_page parameters for paginating the results of SELECT queries (we automatically modify your query to apply LIMIT and OFFSET clauses). For other query types (i.e. DESCRIBE, CONSTRUCT, ASK), pagination like this doesn’t make so much sense, so these parameters are ignored.

For requests made through the website (i.e. HTML format), the page size is defaulted to 20. For requests to our sparql endpoint for data formats (i.e. non-HTML), there will be no defaults for these parameters (i.e. results are unlimited. For performance reasons we generally advise LIMITing your query if possible).

Parameter Substitution

You can parameterise your SPARQL by including %{tokens} in your queries, and providing values for the tokens in the request parameters.

Note that the following tokens are reserved and cannot be used as parameters for substitution:

  • controller
  • action
  • page
  • per_page
  • id
  • commit
  • utf8
  • query
Cross Origin Resource Sharing

Our servers are configured to allow access from all domains. This means that if you’re writing JavaScript to request data from our server in to a web page hosted on another domain, your browser should check this header and allow it.

If you need to support very old browsers, you can additionally pass a callback parameter and the results will be wrapped in that function. For example:

This help topic on the jQuery website has more details.


Using cURL

Here’s a couple of examples running a query using the widely available cURL command line program.

Request the results as XML, using a POST:

curl -X POST -H "Accept: application/sparql-results+xml" -d "query=SELECT%20*%20WHERE%20%7B%3Fs%20%3Fp%20%3Fo%7D%20LIMIT%2010"

Request the results as JSON, using a GET:

curl -X GET -H "Accept: application/sparql-results+json"*%20WHERE%20%7B%3Fs%20%3Fp%20%3Fo%7D%20LIMIT%2010

Using JavaScript

This example HTML page uses jQuery to issue a POST to our SPARQL endpoint, requesting the results as JSON.

<!DOCTYPE html>
	<script src=''></script>
<script type='text/javascript'>

	var query = 'SELECT * WHERE {?s ?p ?o} LIMIT 10';
	var url = '';
		method: 'POST',
		dataType: 'json',
		url: url,
		data: {query: query},
		success: function(data) {
			alert('success: ' + data.results.bindings.length + ' results');