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 ((-3.7603657110649 55.977071928545215, -3.7583185041301737 55.979740392720124, -3.7575008830334737 55.98355324371164, -3.758993202023382 55.984468326457545, -3.7592728508055755 55.98459019684381, -3.760376248098335 55.9856617397967, -3.752956540980189 55.989361061700976, -3.752248799130334 55.991294263711396, -3.7536707982148707 55.99522075525813, -3.7557171526457456 55.99660790419464, -3.755426248972556 56.00112042014902, -3.740827023875871 56.00837260344062, -3.737762716192197 56.00517453477273, -3.7294480727125787 56.00067970582649, -3.7177577747451687 55.99707255040581, -3.708906840897217 56.0017668754129, -3.7012147352966105 55.999960119196054, -3.693681417808087 55.99945727791192, -3.686017414904245 55.99815604847446, -3.6786195813859957 55.99891388459596, -3.677971420058854 55.99846436813125, -3.671065690120682 55.994727411845886, -3.6666071466067005 55.99328437823538, -3.6633688367332193 55.993221215150704, -3.6606949871378833 55.98934467139272, -3.6565942452355418 55.98882032571668, -3.6547657657654584 55.98553706339269, -3.6607982369529393 55.986105613882295, -3.670274872717442 55.9877676170627, -3.682593560450123 55.98885093849493, -3.6832675393201515 55.98122950214871, -3.684185293359352 55.978817717591156, -3.6917053268514683 55.98120569208274, -3.700505352396991 55.98322600713132, -3.714147122024675 55.982487049817024, -3.717755515563147 55.983361496285205, -3.724288775035983 55.98310218050912, -3.725292594387905 55.981492185819086, -3.7301510676290492 55.980276592472805, -3.7342729408525592 55.980372277982134, -3.741040819559504 55.978036591128586, -3.754528001070845 55.975815259666675, -3.7603657110649 55.977071928545215))
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');