Talk:Wikidata Query Service/Archive 1

More in Wikidata
See also suggestions at https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/suggestions

Duplicates and missing rows.
I am getting duplicates and missing rows. The duplicates seem to arise when the a value has been edited in the references. I do not know why the row is missing.

An example of a duplicate with the below SPARQL is "wd:Q21076992 * En røv bag øret" and the missing one is "wd:Q21083886 * Beton - historier fra skurvognen" from. I am also getting duplicate elements, e.g., "Ove Dahl, Ove Dahl (politi)". This seems also to be related to editing the value.

&mdash; Fnielsen (talk) 22:16, 15 October 2015 (UTC)
 * This issue has now been phabricated: https://phabricator.wikimedia.org/T116622 &mdash; Fnielsen (talk) 17:53, 26 October 2015 (UTC)

Scratch pad
A scratch pad beside the query box would be really convenient for quickly storing queries. The pgAdmin tool for managing Postgresql databases has had this feature for years (http://www.pgadmin.org/docs/1.6/images/query.png). The main use case is when people are experimenting with queries, they often need a temporary place (ends up being a text file) to store and compare variations of a query. This feature is an effective and "low-tech" alternative to providing multiple tabs for running queries.

Rename page and subpages
Should this page and subpages be titled 'Wikidata Query Service' ? John Vandenberg (talk) 02:37, 6 January 2016 (UTC)

Exceptions and timeouts using wikidata query service
Hi there,

there might be a problem with the current wikidata query service.

I try to write a tool, which can answer questions with given answer candidates. To accomplish this I match the children of a parsed entity from the question and match the found candidates with the given.

One way which is realy fast and effective is using queries like these:

But currently I am receiving timeouts or exceptions
 * This seems to be fine now. --Smalyshev (WMF) (talk) 18:43, 16 March 2016 (UTC)

"Execute" shortcut
Can we have a keyboard shortcut for the "Execute" button, please? --Magnus Manske (talk) 12:34, 9 March 2016 (UTC)

"Error:"
This one gives a blank error. Query via WDQ2SPARQL, converted from CLAIM[131:(TREE[1198][150][131])] AND CLAIM[31:(TREE[473972][][279])]. --Magnus Manske (talk) 18:39, 10 March 2016 (UTC)
 * I think that is the same as T127014 added as another example there. - Jan Zerebecki 14:32, 11 March 2016 (UTC)
 * Yes, there's something fishy there, I'm looking into it. Smalyshev (WMF) (talk) 18:43, 16 March 2016 (UTC)

Old short links are broken
Something seems to have happened recently that broke old short URLs, such as tinyurl.com/htb92er. You can see the query in the final URL, but it doesn't appear in the box, and can't be executed. Cheers, Bovlb (talk) 20:55, 22 March 2016 (UTC)
 * Which browser are you using? --Lydia Pintscher (WMDE) (talk) 15:58, 23 March 2016 (UTC)
 * That's an excellent question, so I did some testing. I observe this problem using Google Chrome Version 49.0.2623.87 (64-bit) on MacOS, and also using an unknown version of Google Chrome on Windows.  I do not observe it in Safari 8.0.7 or Firefox 35.0.1.  This used to work fine in Google Chrome, and I'm not aware that I've updated since it was working.  The expanded URL is  which also fails on Google Chrome.  I also observe the same behaviour using the new short link mechanism.  Looking in the JavaScript console, I see this error;

App.js:126 Uncaught TypeError: this._editor.registerCallback is not a function
 * UPDATE: As I did more testing, the problem disappeared, and old links started working in Chrome. Did you update the site?  Now the only console message I see is the relatively benign:

modernizr-2.8.3-respond-1.4.2.min.js:4 Mixed Content: The page at 'https://query.wikidata.org/#SELECT%20%3Fx%20%3FxLabel%20(MIN(%3Fdate)%20AS%…20%7D%0A%7D%20GROUP%20BY%20%3Fx%20%3FxLabel%20ORDER%20BY%20DESC(%3Fmindate)' was loaded over HTTPS, but requested an insecure font 'http://themes.googleusercontent.com/static/fonts/inconsolata/v5/BjAYBlHtW3CJxDcjzrnZCIbN6UDyHWBl620a-IRfuBk.woff'. This request has been blocked; the content must be served over HTTPS.
 * Cheers, Bovlb (talk) 16:16, 23 March 2016 (UTC)


 * It seems your browser cache had an old version of Editor.js which broke App.js

✅ (caching problem)

Query Logs
Hello,

would it be possible to get query logs of Wikidata (https://query.wikidata.org/)? I'd love to have them for my research project. Thanks a lot!

Fadirra (talk) 13:54, 31 March 2016 (UTC)

Missing ps/pq
It appears that the ps and pq prefixes are automatically added in the web interface, but not in https://query.wikidata.org/sparql?format=json&query= The automatic prefixes should be consistent. --Magnus Manske (talk) 20:28, 12 April 2016 (UTC)

WDQ2SPARQL query timeout
So I have a deceptively simple WDQ query: CLAIM[1435:(TREE[916475][][279])] AND CLAIM[131:(TREE[12526][][131])] which WDQ2SPARQL converts to SELECT ?item WHERE { ?item wdt:P1435 ?sub0. ?sub0 (wdt:P279)* wd:Q916475. ?item wdt:P131 ?sub1. ?sub1 (wdt:P131)* wd:Q12526 } Now, WDQ returns the ~1000 items in about 1 second. However, the SPARQL query (can't link to it, because tinyurl prevents me from saving the page) times out (still returns JSON though?). Is there anything you can do on the SPARQL engine or WDQ2SPARQL to improve this? I would like to retire WDQ sooner rather than later, but as long as auto-conversion essentially breaks functionality in downstream tools, I can't do it. --Magnus Manske (talk) 14:22, 13 April 2016 (UTC)
 * Unlimited path queries are usually the hardest for the engine in my experience. I'll look into what can be done to make it better, maybe use vertex-based search service instead... --Smalyshev (WMF) (talk) 22:19, 16 August 2016 (UTC)

Sardinia (Q1462) is not returned when I query for regions of Italy (Q16110)
This query should return 20 regions but instead only returns 19. Sardinia for some reason is missing. I checked and the relation Q16110 seems to be correctly declared for Sardinia.

This is my query

SELECT * WHERE {?resource wdt:P31 wd:Q16110.}

and this is the result

resource wd:Q1210 wd:Q1216 wd:Q1222 wd:Q1237 wd:Q1243 wd:Q1250 wd:Q1256 wd:Q1263 wd:Q1273 wd:Q1279 wd:Q1280 wd:Q1282 wd:Q1284 wd:Q1438 wd:Q1443 wd:Q1447 wd:Q1452 wd:Q1458 wd:Q1460

FrBailo (talk) 14:40, 13 April 2016 (UTC)
 * It's in wdq: http://wdq.wmflabs.org/api?q=claim[31:16110] --Magnus Manske (talk) 15:01, 13 April 2016 (UTC)
 * Returns 20 now so I assume it's ok. --Smalyshev (WMF) (talk) 22:21, 16 August 2016 (UTC)

Deleted items showing up in queries??
I've been trying to clean up self-instances (which are never logically justified) - the query is at tinyurl.com/jq5hduf - I cleaned up the ones I could, but the remaining 5 are all deleted items like Q21704990. Why is the query service returning deleted items in responses??? ArthurPSmith (talk) 16:03, 13 April 2016 (UTC)

deleted items show up repeatedly: SPARQL server with old cache/data
i have a problem on a couple of user subpages visible best here (notice all the ListeriaBot edits of size +321/-321). the 3 items Q1499520, Q1792416 and Q2560705 were deleted in April 2016, but -since May- are added and removed again and again.

Magnus explained to me that this is because one of the SPARQL servers has current data, but the other has outdated/old cache data (if i understood it correct, see in German).

Can somebody please fix this issue. Holger1959 (talk) 20:17, 4 August 2016 (UTC)
 * Smalyshev, maybe you can have a look? don't know if you noticed this. Holger1959 (talk) 15:48, 13 August 2016 (UTC)

Should be fine now, please ping me if it is still a problem. --Smalyshev (WMF) (talk) 22:08, 16 August 2016 (UTC)

Not properly synced?
SELECT ?item WHERE { ?item wdt:P131 wd:Q2107. ?item wdt:P1435 wd:Q15632117 } (can't link because tinyurl not allowed) should include Q16832586, but doesn't. I tried to purge the item, but no joy. WDQ finds it correctly. Any idea? --Magnus Manske (talk) 14:46, 28 April 2016 (UTC)

Updated data ?
Maybe I'm wrong but it seems that data are for now not updated. Results are different from those of WDQ. Is it an old version? Example: instances of sculpture (or subclass) with image WDQ results – SPARQL results. Is there somewhere a place to have live information about the service? Thanks --Shonagon (talk) 16:52, 28 April 2016 (UTC)
 * It is currently catching up and should be all good again soon. --Lydia Pintscher (WMDE) (talk) 09:37, 2 May 2016 (UTC)

Result on map : reverses lat/lon
Latitude and longitude are set in place of the other one.
 * Yeah there was a switch. Will be fixed tonight. --Lydia Pintscher (WMDE) (talk) 09:34, 2 May 2016 (UTC)

Translation
I cannot find the tool on Translatewiki. Is the UI not internationalized yet? Danmichaelo (talk) 06:53, 2 May 2016 (UTC)
 * It is not there yet. We've got the patch to make it happen but it still needs some manual work. --Lydia Pintscher (WMDE) (talk) 09:35, 2 May 2016 (UTC)

SPARQL endpoint is down?
I am rarely able to run any query for the past 18 hours or so. When I load the website, the status bar at the bottom eventually displays: "Data last updated: [unable to connect]". Is this possibly related to this task:? https://phabricator.wikimedia.org/T133566 —seav (talk) 04:12, 3 May 2016 (UTC)
 * Any idea what happened here? --Lydia Pintscher (WMDE) (talk) 08:41, 3 May 2016 (UTC)
 * Separate bug has been filed in Phabricator: https://phabricator.wikimedia.org/T134238 —seav (talk) 13:37, 3 May 2016 (UTC)

Way to get the precision of time values?
Is there a way to get the precision of time values using this service? —seav (talk) 01:58, 5 May 2016 (UTC)
 * See Wikibase/Indexing/RDF Dump Format. Matěj Suchánek (talk) 16:25, 3 October 2016 (UTC)

502 Bad Gateway
I constantly receive 502 bad gateway from spraql query service. I tried with 3 different browsers and it is still the same. Is the problem related with me or the server?
 * Seems like the server. I haven't been able to query it for some hours now. Danmichaelo (talk) 19:42, 7 May 2016 (UTC)
 * Found T134238. Danmichaelo (talk) 19:50, 7 May 2016 (UTC)

Completion, Plotting OSM relations in the results, instead of a single coordinate
It would be nice with completion on #defaultView:. Also, when doing the example query that returns rivers, it would be nice if there was an option in the Display drop-down that would show their associated OSM relations. Like with. On Wikipedia, clicking the inline map on that page will show the whole route. --Ysangkok (talk) 01:49, 13 May 2016 (UTC)

Blank error and search does not complete
I tried running the following query: PREFIX wdt: 

SELECT ?compound ?name ?smiles WHERE {

?compound wdt:P31 wd:Q11173 ;

rdfs:label ?name.

OPTIONAL {?item wdt:P233 ?smiles}

}

and the query runs, but after a few seconds the text ERROR: appears, but no message is displayed. The query doesn't display a time out and appears to continue running for minutes until I close the browser window. Without the OPTIONAL statement the query will return 156546 results in 8138 ms. I get the same error if I use the OPTIONAL statement looking for other properties eg P234 (inchi). Any ideas on what the error is? Is it my query or a bug? Ideally I would like to get InChIs and SMILES data where they exist for a compound. Thanks --The chemistds (talk) 10:18, 2 June 2016 (UTC)

Handling properties with variable unit types
[Disclaimer: My knowledge of SPARQL and other query languages is almost zero.]

I'm trying to see how well I can generate lists of geographical entities (mountains, lakes, rivers, etc.) sorted by a particular measured physical property: elevation, area, volume, depth, length, width, etc. Here's an example Wikidata Query that actually works (after a fashion):

Once I got to this point I discovered that a lot of the lakes showing up at the top of my list of largest lakes were actually mid-sized lakes in Sweden. After some digging I discovered that some lake volume figures are given in cubic meters and others in cubic kilometers. Clearly these can be converted, so long as I can identify which unit of measurement is being used for each and adjust it as needed. How would I do that? (I tried a lot of times and failed.) This seems to be a pretty broadly applicable requirement as there are lots of properties here that accept values with various types of units.

Also, some items show up more than once. For example, the shows up twice because it is an instance of both an  and a, both of which are subclasses of lake. Is there a way I can rewrite the query so that I don't get duplicate items? Rupert Clayton (talk) 22:59, 7 June 2016 (UTC)

Queries are down at this time: (6th of July 2016 : 7:16 UTC).

Is the number of arguments in a query limited?
Hi, I just wonder whether there is some limitation as to the length of a query. Here is the query: tinyurl.com/zdn4lfl

When I add more fields, the server returns "ERROR: Could not contact server" Is this a feature or a bug? Is it documented somewhere? -- Beat Estermann (talk) 22:13, 16 July 2016 (UTC)

Why don't URIs work in queries?
This works: This doesn't:


 * You need to use different URL for property, wdt: prefix is http://www.wikidata.org/prop/direct/ so full URL is http://www.wikidata.org/prop/direct/P828. See: https://www.mediawiki.org/wiki/Wikibase/Indexing/RDF_Dump_Format#Full_list_of_prefixes --Smalyshev (WMF) (talk) 22:11, 16 August 2016 (UTC)

Add WDQ to SPARQL conversion?
Many of Magnus's tools (eg PetScan) now have a wonderful WDQ2SPARQL feature which can take a standard WDQ query (eg claim[31:5]) and convert it into the correct SPARQL form. Given how relatively easy WDQ is to remember for simple queries, and that this conversion tool works so neatly on PetScan, could it be added as a feature on the Wikidata query service as well? Andrew Gray (talk) 19:44, 2 August 2016 (UTC)

Add support for bds: to SPARQL endpoint?
Blazegraph supports full text search which can be executed in SPARQL with bsd: predicates. Would it be possible to add support for bsd:?

For example:

This currently results to the following error message:


 * Well, this is because free text index has not been enabled :) We are working on integrating WDQS with our own full-text index solution that is indexing wikidata, see T141813. --Smalyshev (WMF) (talk) 22:13, 16 August 2016 (UTC)

Suggestion: Query formatting function
Hi, Just have to say I love the SPARQL interface. Slick and with very useful functionality!

The only little thing I wish sometimes, is ability to automatically format the query, with nesting, spacing etc.

This is useful sometimes when pasting queries copied from oneliners (such as when they have been embedded in URLs) etc.

Links in query results should be https, not http
The Wikidata query service delivers http links (without TLS encryption) in the query results. Could you please switch to https, or at least use protocol-relative links? Example: go to the query service, select the very first example (“Cats”), and look at the links in the “item” column. Thanks! —MisterSynergy (talk) 10:48, 2 September 2016 (UTC)
 * These are entity identifiers, not links. They need to be fixed and unique for an item, and traditionally most linked data ontologies use http in their URI schemes, almost nobody uses https. This does not mean if you want to use this URI to access the data you have to use http. BTW, what is the problem with identifiers using http URIs? --Smalyshev (WMF) (talk) 19:31, 7 September 2016 (UTC)


 * Thanks for response. The entity identifiers are used as links here, but not fully displayed as such in the GUI (they are listed as "wd:Qxxxx"). I am often using public unencrypted wireless networks and try to hide as much traffic as possible with https, and I am also not sure whether anything sensible such as cookies are sent unencrypted if I click on unencrypted links. It would suffice if I could activate https links as an option in the WDQS GUI, in those situations where I am not primarily interested in entity identifiers. --MisterSynergy (talk) 19:42, 7 September 2016 (UTC)

RGB
Do RGB color values only work when they are upper case? Example: --Tobias1984 (talk) 13:09, 3 September 2016 (UTC)

Getting started
I'm unable to find documentation on Wikidata query service that is complete enough to actually write queries. Everything I've found is hit or miss.

As an example, I started out with a query, which is found at Wikidata Property talk:P569 (search for "Wrong calendar and click on "Violations query")

My intent was to add a new requirement, in addition to the date-related requirement, that the item have the property "Country of citizenship" and the value of that property be "Kingdom of Great Britain". So I modified the query by adding this line:

?item p:P27 wd:Q161885.

on a separate line just above the right curly brace.

This query didn't return any results. I couldn't find any documentation that one could read from the point of view of "this is what I want to do, how do I do it?" Any suggestions? Jc3s5h (talk) 23:35, 30 September 2016 (UTC)


 * Jens on my team is currently working on better documentation. Hope to have something to show in a week. --Lydia Pintscher (WMDE) (talk) 11:07, 2 October 2016 (UTC)

Missing data in query
I'm trying to query cities. Algiers (Q3561) is an instance of capital (Q5119) and city (Q515). But when I make the following query, information about city is lost and result consists only of one entity.

SELECT * {wd:Q3561 wdt:P31 ?class}

https://query.wikidata.org/#SELECT%20%2a%20%7Bwd%3AQ3561%20wdt%3AP31%20%3Fclass%7D

I get the following result: wd:Q5119, but I expect it to be wd:Q515 and wd:Q5119

Is it a bug, or am I doing something wrong? --176.14.69.93 19:38, 1 October 2016 (UTC)


 * See for instance T125558. Matěj Suchánek (talk) 16:21, 3 October 2016 (UTC)

Label service button
Could we have a button that adds the "label service" magic incantation? Maybe before the last "}", or just append otherwise? We can move it around as needed, just copying that thing all the time gets annoying... --Magnus Manske (talk) 13:19, 13 October 2016 (UTC)

New visitors do not see the "Run" button because my query is very long.
When I send lay people to my shiny query, all they see is a wall of text, and nothing to click on. That's because my query has many lines, even though I have compacted the code a lot.

SOLUTION: Make the query area scrollable if the query is more than 20 lines.

What do you think about it? Thanks! Syced (talk) 13:23, 14 October 2016 (UTC)