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.4399843277123131 50.87752735093097, -0.4385017633685777 50.87510096744644, -0.4354956933714783 50.87148600831566, -0.4389336678531076 50.871531985342074, -0.4364313537673645 50.85498362004295, -0.4338549507089319 50.85457503204964, -0.4303672799550238 50.85520091613874, -0.4291146220010424 50.85412918935936, -0.4269937241387584 50.85466991966622, -0.4270906077458018 50.85588709325365, -0.4242978257001166 50.856925940700094, -0.4242045374640439 50.85505591224224, -0.4219934326167306 50.850939593449866, -0.4229049167453159 50.84868113113274, -0.4221928451853761 50.84645920211848, -0.4222997362434529 50.84067713831776, -0.4250156986358839 50.83986751507773, -0.4321916809975508 50.83972479304682, -0.4367819756743198 50.840580339236084, -0.4407964537799508 50.84056282179714, -0.4460070802169787 50.83985417888948, -0.4433717541935164 50.83731095926134, -0.4465318283784237 50.83632589710017, -0.4529193955892231 50.837073322912644, -0.45283828695235 50.83905436371893, -0.4509004042969959 50.84181839518961, -0.4500857601432965 50.84411438228925, -0.4506284203751208 50.84660100308104, -0.4496872772179678 50.84949605772967, -0.4502544723407361 50.850471240783584, -0.4499649709707134 50.85346305788368, -0.448565368367655 50.857109252493125, -0.4477855446860921 50.86249663119524, -0.4468614722716528 50.86606005308607, -0.4445340448700165 50.87032064409696, -0.4442282837031709 50.873315788387906, -0.4461672926326987 50.87454667432428, -0.446681243970701 50.878414293702, -0.4479341558575335 50.87972417379272, -0.446852794599729 50.88048141875889, -0.4399843277123131 50.87752735093097)))
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');