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.052853232299816 56.49785074439285, -3.0568267571176193 56.49770942060693, -3.056660404396833 56.496403557629506, -3.058078827014042 56.496335003269515, -3.0578384242342462 56.49507013993063, -3.05825484757122 56.495044768383075, -3.0579820000717803 56.49283040641281, -3.06157501115619 56.493086834152, -3.063662050765203 56.493328888832174, -3.063178486660683 56.49552339340955, -3.062497288036625 56.49614017347112, -3.0626837828107476 56.49696503091585, -3.06387794961412 56.49725232970067, -3.0637574244130596 56.49866330822602, -3.065397157414072 56.49865581936017, -3.0657638667607485 56.501280906210354, -3.068755819641126 56.50114179107939, -3.069546097086695 56.503303850059986, -3.068900035900903 56.504622576236855, -3.069460564793293 56.50467783046107, -3.069456102517142 56.50562198339721, -3.0674489503004168 56.505638325092555, -3.0672734250028615 56.50505243282572, -3.0661510147700866 56.50368129182536, -3.0658713063498593 56.50283974704351, -3.0640760282348283 56.502266617975565, -3.05963379156897 56.50245964577255, -3.0573947869177687 56.50263378438863, -3.054584464969592 56.502436175276884, -3.0507849425295244 56.50268988559149, -3.0467919466435296 56.503184161641876, -3.046211020701804 56.50224418093643, -3.0453275376847873 56.5001034734956, -3.0498972373257565 56.50002232923675, -3.0503933119204003 56.50148244285985, -3.0540442383998605 56.501350685505216, -3.0592286348124627 56.50072587758106, -3.060144761923412 56.50129563192758, -3.062660690982408 56.500813698191386, -3.0595441605148483 56.49917299239549, -3.0547792015143616 56.49982794495071, -3.0546702561901813 56.499144832159125, -3.0536985575877216 56.49925191957791, -3.052853232299816 56.49785074439285))
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');