Return-Path: X-Original-To: apmail-incubator-jena-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-jena-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C416087AB for ; Tue, 13 Sep 2011 14:53:27 +0000 (UTC) Received: (qmail 58335 invoked by uid 500); 13 Sep 2011 14:53:27 -0000 Delivered-To: apmail-incubator-jena-dev-archive@incubator.apache.org Received: (qmail 58315 invoked by uid 500); 13 Sep 2011 14:53:27 -0000 Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jena-dev@incubator.apache.org Delivered-To: mailing list jena-dev@incubator.apache.org Received: (qmail 58307 invoked by uid 99); 13 Sep 2011 14:53:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2011 14:53:27 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of castagna.lists@googlemail.com designates 74.125.82.43 as permitted sender) Received: from [74.125.82.43] (HELO mail-ww0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Sep 2011 14:53:21 +0000 Received: by wwf27 with SMTP id 27so815327wwf.0 for ; Tue, 13 Sep 2011 07:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=H1oeV4H/XKAktJ2LH8vKf/KUisl8slr2CVVF3GWuIcU=; b=OghQAQx4yipltoe6hnSSPgU5VG6nizVkDFI9Vsh8UyV/vIw4H3ekABJRG52BCETTs8 pE+My/xQvDNa/Qr40X8sros/fQQbyyb8/4MyqaciXBUfYNe3gS4SPjdxIb4JJ0Ouxeg/ YJyiGBCPI+jOyzrt81zxr/nNTOKihkt4seTmw= Received: by 10.216.172.198 with SMTP id t48mr997370wel.79.1315925579871; Tue, 13 Sep 2011 07:52:59 -0700 (PDT) Received: from [192.168.10.120] ([212.36.55.94]) by mx.google.com with ESMTPS id i11sm649137wbn.25.2011.09.13.07.52.58 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Sep 2011 07:52:59 -0700 (PDT) Message-ID: <4E6F6E49.50502@googlemail.com> Date: Tue, 13 Sep 2011 15:52:57 +0100 From: Paolo Castagna User-Agent: Thunderbird 2.0.0.24 (X11/20101027) MIME-Version: 1.0 To: jena-dev@incubator.apache.org Subject: Re: Jena and PostGIS =?UTF-8?B?KMOgIGxhIExBUlEp?= References: <4E6F41B8.8050600@oucs.ox.ac.uk> In-Reply-To: <4E6F41B8.8050600@oucs.ox.ac.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Alex Alexander Dutton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > We've currently got a lot of (simple) geospatial data in > (served behind the scenes by Fuseki). > > We'd like to do some geospatial indexing magic, and were wondering > about writing something a bit like LARQ that will pull out things like > geo:Points and WKT literals, place them in a PostGIS-flavoured DB, and > then implements something like GeoSPARQL (). Which kind of queries you would like/need to run? The use cases I've seen (on the job) are often quite simple, since users are not GIS expert. The vast majority of them can be reduced to: - searching near by a point (often sorting results by distance) - searching within a bounded box Ideally, it would be good to have something pure Java which keeps things very simple to install. Ideally, zero installation cost: download, unzip, load data, run (as it is for Fuseki). What would be the best way to integrate|use such extensions into Fuseki? Ideally, with 0 changes to Fuseki code base... is that currently possible? Also, I have not been following the progress around GeoSPARQL: http://www.opengeospatial.org/projects/groups/geosparqlswg ... is there anything interesting/relevant there? Code? :-) Finally, things to think about are: - how to you initially build your geo indexes? - how you keep those indexes up-to-date as you add/remove triples|quads? - how do we plug-in|use|integrate this from|into ARQ (or TDB or Fuseki)? Currently, I am not completely satisfied by how we|I do this with LARQ (via assemblers), but maybe it's just because I am not an Jena's assembler guru. Ideally, I'd like to have a way to add property functions to ARQ (and use them with TDB datasets or Fuseki) without changing ARQ or TDB nor Fuseki source code. You drop a jar in your class path and the property function as well as keeping indexes up-to-date is there. Paolo > > Has anyone started doing this or something similar? I'm happy to give > it a go and I'm sure my employer would be happy to contribute it back > to Jena and the ASF. My plan was to go through the LARQ codebase to > work out how it hooks itself in, and use that as a model. > > Yours, > > Alex > > - -- > Alexander Dutton > Metamorphoses Project Developer, Claros > Oxford University Computing Services, ℡ 01865 (6)13483 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk5vQbgACgkQS0pRIabRbjC9QACfTZtTcFIhDXjWPR+MpEWunKkt > 38oAnR5n+oi1nuTZAfRdOrF2mcOac2Ck > =r1dj > -----END PGP SIGNATURE----- >