Andy, yes, but I am discussing some details with Ying Jiang off-list there are some configuration questions I still have. The code itself looks OK.
What would be the schedule for a release? Will this be part of the main jena release? if so there need to be some dependencies worked out for apache-lucene and apache-lucene spatial on my end. Marco On Mon, Aug 5, 2013 at 9:04 AM, Andy Seaborne <a...@apache.org> wrote: > Macro - have you had a chance to try this out yet? > > > On 03/08/13 11:11, Ying Jiang wrote: > >> Hi Andy, >> >> Thanks for the comments! Please check my replies below. >> >> 1) Release: >> Firstly, I'd like to make a release in the Google code [1] and announce in >> the jena user mailing list for the feedbacks, marking it as >> "jena-spatial-1.0.0". It should include the current source code and a >> compiled jar. I'll also make a tag of "jena-spatial-1.0.0" in Google code >> svn. However, during coding, the version of the "jena-parent" is >> "7-SNAPSHOT", >> with "ver.jena" as "2.10.2-SNAPSHOT". Shall I change them into "6" and >> "2.10.1" respectively in the "jena-spatial-1.0.0" release tag? >> Secondly, I'm looking forward to migrating the code to Jena SVN. What >> shall >> I do exactly? Do I need an apache svn account as a committer? >> > > We (the Jena project) need to get sorted out and I won't want that to > delay a release and getting feedback. > > (I'd missed the fact that Google code no longer supports downloads as of > May this year.) > > The quickest thing to do is to send email to the users list as soon as > some documentation is ready. > > > 2) Testing: Last week, I made some unit tests for the property functions. >> I >> did find some bugs during testing. The tests are very useful. More testing >> will be delivered later. Thanks for your reminder. >> > > The tests pass for me but they generate some warnings - should I worry > about this? > > > 3) User documentation: It's not done yet. I'll create a user guide similar >> to jena-text [3]. The documentation will be provided to the users >> accompanying with the release of 1). >> > > Andy > > > >> [1] >> https://code.google.com/p/**jena-spatial/<https://code.google.com/p/jena-spatial/> >> [2] >> https://code.google.com/p/**jena-spatial/source/browse/** >> trunk/src/test/java/org/**apache/jena/query/spatial/TS_** >> Spatial_Lucene.java<https://code.google.com/p/jena-spatial/source/browse/trunk/src/test/java/org/apache/jena/query/spatial/TS_Spatial_Lucene.java> >> [3] >> http://jena.apache.org/**documentation/query/text-**query.html<http://jena.apache.org/documentation/query/text-query.html> >> >> On Mon, Jul 29, 2013 at 10:44 PM, Andy Seaborne <a...@apache.org> wrote: >> >> On 27/07/13 14:40, Ying Jiang wrote: >>> >>> Hi, >>>> >>>> The default distance units measurement is "miles". I've just committed >>>> a >>>> major change of the codes, including the following updates: >>>> >>>> 1) Support spatial indexing of WKT literal, including Point, Polygon or >>>> any >>>> other kinds of shapes. >>>> 2) New property functions of "withinCirle", "withinBox", >>>> "intersectsBox", >>>> "north", "south", "east", "west" >>>> 3) Support different distance units for "nearby", such as "miles", >>>> "kilometers", "degrees", "meters" and so on. >>>> 4) Examples are updated [1]. You can play with the new features of >>>> jena-spatial. >>>> >>>> It's almost half-way of the GSoC project. In the upcoming second half, >>>> I'll >>>> bring more visibility of code progress to the community, at least >>>> one report per week. Thanks to Andy for pointing it out! >>>> >>>> [1] >>>> https://jena-spatial.**googlec**ode.com/svn/trunk/src/**main/** >>>> java/examples/<http://googlecode.com/svn/trunk/src/**main/java/examples/> >>>> **JenaSpatialExample1.java<htt**ps://jena-spatial.googlecode.** >>>> com/svn/trunk/src/main/java/**examples/JenaSpatialExample1.**java<https://jena-spatial.googlecode.com/svn/trunk/src/main/java/examples/JenaSpatialExample1.java> >>>> > >>>> >>>> >>>> On Tue, Jul 23, 2013 at 9:37 PM, Andy Seaborne <a...@apache.org> wrote: >>>> >>>> In the example query there is: >>>> >>>>> >>>>> ?s spatial:nearby (51.3000 -2.71000 100) >>>>> >>>>> What units are the "100"? >>>>> Can the application provide different units? >>>>> >>>>> Andy >>>>> >>>>> >>>>> >>>> Things are looking very good. >>> >>> How does this fit with the original plan in terms of functionality >>> available? >>> >>> >>> As we enter the second part of the GSoC, we need to be thinking about >>> >>> * A release >>> >>> That does not mean it's complete and a release needn't be a major cost in >>> time. Having even one or two people try it out really helps in >>> understanding what people might do with spatial indexing. >>> >>> It can be a message to the users Jena mailing list announcing status of >>> the project and assuming interested people will grab the source and >>> compile >>> a jar for themselves. >>> >>> But, if you want to, we can do something more packaged - anything up to >>> and including migrating the code to Jena SVN and putting in a Jenkins job >>> to build it into Jena's snapshot maven repository that's doable. >>> >>> A couple of things go with that: >>> >>> * Testing >>> >>> src/java/test is a bit empty :-) >>> >>> * User documentation >>> >>> Enough that someone can setup and use the project - short, to the point >>> and "now" is better than long and detailed and "later". (The final phase >>> of GSoC is write-up - that's needs to cover the next developers to come >>> along.) >>> >>> What do you think about this? >>> >>> Andy >>> >>> >>> >> > -- --- Marco Neumann KONA
