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 MULTIPOLYGON (((0.2561311060557991 51.17859146466059, 0.2588715254806646 51.17745847435599, 0.2541401816092715 51.17418078947495, 0.2526169001312717 51.171988753958196, 0.2531662105206852 51.17090256136398, 0.2462439593311047 51.169880031067876, 0.2467466050786974 51.167743434900984, 0.2422043202606513 51.16496258999317, 0.2384357276341361 51.16013065784262, 0.236758107525907 51.1592454217792, 0.2309292139480102 51.16032623024803, 0.2259263287715097 51.15994309249237, 0.2203607817516496 51.15767012120394, 0.2162499939999341 51.16067272994199, 0.2136275168480321 51.160805127847944, 0.2085781805157053 51.159058730559494, 0.2054417952714218 51.158820227388766, 0.2054610497354389 51.16087215432116, 0.2031464123248191 51.16173237230834, 0.2014745500455663 51.16014414190394, 0.1990120621995034 51.161745416940626, 0.1957119028901176 51.1649865713928, 0.1906406106319822 51.16796224125737, 0.1909713500400468 51.171378048553706, 0.1947799323218143 51.17382480231972, 0.1979984104826285 51.17513675777652, 0.1995507533856617 51.173183884336865, 0.2024050100270073 51.17243588427684, 0.2051642551388836 51.17245674412467, 0.2073803866052286 51.1753629808268, 0.2118546293663665 51.17540076693413, 0.2180922288207763 51.177509432160505, 0.2163032173134366 51.17913878475735, 0.2192687879007716 51.1799908959145, 0.2269615470820676 51.184154341639385, 0.2296806484406148 51.18291360339267, 0.2312820136075549 51.18510805091219, 0.2344866992895052 51.18491377390997, 0.2392993795984103 51.182674106230074, 0.2404577936373211 51.18145130413985, 0.2436030685769718 51.182043044848115, 0.2469184395315335 51.18130580407103, 0.2541756205702055 51.17877664976011, 0.2561311060557991 51.17859146466059)))
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');