[02:27:28] SMalyshev, do you know why built-in bounding box function keeps timing out, but the manual lat/lon filter works great? http://tinyurl.com/ydbu2sl6 [02:28:09] could it be that wikidata always use bounding box before other filters, and since it has far fewer objects with geo point, it works ok? [10:42:33] Aleksey_WMDE: socket://172.16.66.65:9100 [14:57:18] are there any existing scripts/gadgets to make adding sitelinks easier? [15:01:01] ideally I could just press a key, paste a url and press enter... I could probably come up with something myself but I'm lazy (hence wanting it to be easier in the first place :P) [16:21:33] PROBLEM - Check systemd state on wdqs1005 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [16:57:03] RECOVERY - Check systemd state on wdqs1005 is OK: OK - running: The system is fully operational [17:01:04] PROBLEM - Check systemd state on wdqs1005 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [17:03:04] RECOVERY - Check systemd state on wdqs1005 is OK: OK - running: The system is fully operational [17:40:52] SMalyshev, do you know why built-in bounding box function keeps timing out, but the manual lat/lon filter works great? http://tinyurl.com/ydbu2sl6 [17:41:55] i remember you said something about disabling optimizations - could that be it? [17:42:38] hmm... may be too many items? There's a bug that messes with service ordering... so it may be run too early? need to check query explain to see [20:25:35] SMalyshev, the osmm:loc predicate (gps point) is set on every OSM object in that DB - so there are as many of them as wikidata items. [20:26:35] SMalyshev, take a look at the optimizer - http://88.99.164.208/bigdata/#query [20:26:57] (original query is at http://tinyurl.com/ydbu2sl6 ) [20:27:48] i suspect optimizer tries to do geo-search before all other filtering, and there is no proper geospacial index in place [20:28:29] or actually, even if there is, filtering all of the objects in USA (huge number), and then applying other filters is not efficient [20:28:39] this one works just fine: http://tinyurl.com/y9qu7wat [20:28:48] so it's not the box [20:30:28] SMalyshev, see above - the box works if its the only index used - it simply picks the first 10 matching. But the optimizer should not use that box before other filters - other filters only produce ~1000 items, so box-filtering should happen afterwards [20:30:44] yurik: the osm sparql thing doesn't work for me :( I get syntax errors in the js (which makes it unable to run any queries) [20:31:10] count takes a long time though, must be a lot of points in that box [20:31:25] nikki, ?? what query? could you post a tinyurl link [20:31:31] the one you linked above [20:31:54] yurik: there's no such thing as box-filtering. it's not a filter [20:32:14] I don't even think it reads the bindings [20:32:48] the console has "Uncaught SyntaxError: Unexpected identifier" and "Uncaught ReferenceError: CONFIG is not defined" in chromium and "SyntaxError: class is a reserved identifier" and "ReferenceError: CONFIG is not defined" in firefox [20:33:32] SMalyshev, this query times out because there are too many points in the box. I was under the impression that the service simply acts like a parametrized filter, similar to manually comparing box condition to a point [20:33:33] http://tinyurl.com/y9pvs53a [20:34:01] yurik: nope, don't think so [20:34:48] nikki, i just opened http://88.99.164.208/wikidata/ in firefox, clicked on examples, picked the first, and ran it - looks fine [20:34:53] what doesn't work for you? [20:35:06] yurik: https://wiki.blazegraph.com/wiki/index.php/GeoSpatial [20:36:46] a lot of the text appears to be missing and if I click the run button, I get taken to http://88.99.164.208/bigdata/namespace/wdq/sparql?query= (with any text I entered in the box appended) [20:37:19] if I open an embed.html url, I just see the icon forever [20:37:33] if I open a url with a query in the url after the #, the text box is still empty [20:37:36] this is very strange - what browser are you using? i just tried it with chrome and firefox (latest, on ubuntu), both worked fine [20:38:23] could it be some firewall ? [20:38:53] chromium and firefox... neither are the most recent versions, but I don't have any of these problems with the same browsers on query.wikidata.org [20:39:39] very strange... i don't have chromium readily available. It might be due to the customizations that I did to the default wdqs code [20:40:35] but then again, the code gets compiled to an older version... i will see if i can find an older chromium somewhere - please send me the versions that you use for both ff & ch [20:41:52] SMalyshev, thanks, i will look at it closer. I might have to rethink my recommendations on how to do geo-queries - i do stress that service to the limits when handling all of OSM data [20:43:29] nikki, could you leave me a comment with that info at https://wiki.openstreetmap.org/wiki/User_talk:Yurik - need to disconnect [20:43:33] thx for reporting [22:04:25] Hello all…for referencing sources in wikidata, is it intended that the source include every qualifier? e.g. if I have one source stating when an item was manufactured and another stating by whom it was manufactured…and assuming that should be entered as a "manufacturer" with qualifier "point in time"…should I put two sources on that single statement, or handle it some other way?