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 ((-4.037566641162449 55.86763169182919, -4.035827930586409 55.868001975819304, -4.033386228070242 55.864402630478786, -4.033682590947647 55.86365181956732, -4.035852719993941 55.86389451894144, -4.033632387660801 55.86177436766555, -4.031147626536449 55.8627602167954, -4.029375410928684 55.86226705653856, -4.02732700092291 55.85975751211785, -4.019970110523878 55.855016592929005, -4.020141638972788 55.85462733888539, -4.023557559243484 55.85548786034069, -4.038358294880146 55.85467732106497, -4.036992033601458 55.85513132870006, -4.042972376332497 55.85552643763672, -4.043732232192596 55.85630466737234, -4.043433229402276 55.85669607385419, -4.043335489956528 55.85635619497406, -4.041850411590079 55.856677429561785, -4.042172748580374 55.85794823332678, -4.044531887375935 55.8573324984734, -4.044341839342955 55.85695957968669, -4.046984835284998 55.85678081754549, -4.047587781653669 55.85700444870933, -4.046958853538855 55.85780577678941, -4.048262848097723 55.85799077375505, -4.051236368488225 55.85983748120283, -4.050839717747841 55.860194587826676, -4.052109457082177 55.86124286916703, -4.054871098518514 55.86028009908645, -4.056642530144675 55.86144577285576, -4.057118417834135 55.86258815501465, -4.053437552088281 55.86339556469205, -4.052715433946757 55.86273359151382, -4.051144692133199 55.862948519048224, -4.050766500216229 55.86486905812734, -4.04791897291464 55.86451206967875, -4.046529067628834 55.86360953661283, -4.043180294287562 55.86405164549418, -4.043182446248536 55.8653097820421, -4.038975080784934 55.86612071962566, -4.039054899619604 55.866447710890654, -4.037551544017712 55.86673324615343, -4.036968740967771 55.86750678228321, -4.037566641162449 55.86763169182919))
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');