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.906514596752043 56.000024266385175, -3.9054698971619413 55.99970401757962, -3.906873407308009 55.99926128580407, -3.908962397132009 55.998380703593845, -3.9099138285487016 55.99773442682261, -3.911289210364054 55.99748020391764, -3.9121753085804785 55.99776060907282, -3.9137240751320106 55.997142175822, -3.912997732731283 55.996682797597224, -3.91425586814409 55.99614927903227, -3.913423515987715 55.99573080294186, -3.9178874486875923 55.99466505902362, -3.918824281983895 55.99534665908618, -3.9195844792447034 55.99546793161887, -3.9220585570915873 55.99459362526501, -3.9213286265255984 55.994101757180516, -3.9223081671858586 55.993807900378606, -3.923505256450975 55.99235207272144, -3.9247885432031184 55.99275752696217, -3.9263172489836484 55.992172126796454, -3.927057252457202 55.991660006107956, -3.928381006882285 55.991484364309265, -3.9287598244052258 55.9922886951015, -3.926820612058949 55.99303215659933, -3.9271822440121555 55.99333404182455, -3.9286561422794213 55.99287982903007, -3.9313854691868895 55.992254121616014, -3.931680364393419 55.99269193748623, -3.9306944249047637 55.99285005662963, -3.928472007630983 55.993524595435126, -3.923622304280277 55.99602987333984, -3.922596267836163 55.995429096785294, -3.9190102709487626 55.99658402697652, -3.9175737385686347 55.99691482917099, -3.919340612225499 55.99798796850273, -3.9181152423831724 55.99850130355857, -3.9168360202141104 55.99825160582823, -3.9153463314937236 55.998883233128694, -3.914829473405058 55.998099843952026, -3.913779339827593 55.99780368995159, -3.912217977837196 55.997961839054916, -3.910656978644726 55.99879687448691, -3.9094934676824367 55.99899617130973, -3.906514596752043 56.000024266385175))
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');