I would lean towards b.) but that does not mean to omit a.)
On Tue, Aug 6, 2013 at 12:42 PM, Ying Jiang <[email protected]> wrote: > Hi, Marco > > The current indexing strategy requires both the followings: > 1) the predicates to be geo:lat and geo:long; > 2) the datatypes of objects are: XSDfloat, XSDdecimal, XSDdouble, > XSDinteger > > For b) you mentioned. Jena will regard no datatypes of the objects. > Shall we remove the requirements of 2), or make it compatible with b)? Are > the datatype restrictions on the objects necessary for indexing? > > Best regards, > Ying Jiang > > On Wed, Aug 7, 2013 at 12:17 AM, Marco Neumann <[email protected] > >wrote: > > > the current project requires the spatial data for points to come typed as > > xsd:float. otherwise data is ignored during indexing. > > > > example: > > > > a.) {will be indexed} > > airports:EGBB rdf:type airports_sc:LargeAirport ; > > geo:lat "52.4539"^^xsd:float ; > > geo:long "-1.74803"^^xsd:float ; > > rdfs:label "Birmingham International Airport" > > > > b.) {will not be indexed} > > airports:EGBB rdf:type airports_sc:LargeAirport ; > > geo:lat "52.4539"; > > geo:long "-1.74803"; > > rdfs:label "Birmingham International Airport" > > > > By default jena should accept geo:lat and geo:long as decimal degrees. > > > > > > > > > > On Tue, Aug 6, 2013 at 12:04 PM, Ying Jiang <[email protected]> > wrote: > > > > > Hi, > > > > > > I'm with the dev list. Any problems with your tests? > > > > > > Best regards, > > > Ying Jiang > > > > > > On Tue, Aug 6, 2013 at 9:58 PM, Marco Neumann <[email protected] > > > >wrote: > > > > > > > Andy, > > > > > > > > is Ying Jiang a member of the dev list? > > > > > > > > Marco > > > > > > > > > > > > > > > > On Mon, Aug 5, 2013 at 5:16 PM, Marco Neumann < > [email protected] > > > > >wrote: > > > > > > > > > ok so I have the project now in the correct setup and the code > > compiles > > > > > fine but with 1677 warnings as mention by you > > > > > > > > > > I am going to test the code with larger rdf data sets in the coming > > > days. > > > > > > > > > > > > > > > > > > > > On Mon, Aug 5, 2013 at 10:16 AM, Andy Seaborne <[email protected]> > > > wrote: > > > > > > > > > >> On 05/08/13 14:48, Marco Neumann wrote: > > > > >> > > > > >>> On Mon, Aug 5, 2013 at 9:41 AM, Andy Seaborne <[email protected]> > > > wrote: > > > > >>> > > > > >>> On 05/08/13 14:25, Marco Neumann wrote: > > > > >>>> > > > > >>>> 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. > > > > >>>>> > > > > >>>>> > > > > >>>> Great - thanks. > > > > >>>> > > > > >>>> Could we have the discussions on-list please? > > > > >>>> > > > > >>>> > > > > >>>> 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. > > > > >>>>> > > > > >>>>> > > > > >>>> Such as? (I didn't have any issues with the versions in the > POM) > > > > >>>> > > > > >>>> > > > > >>> it's a configuration option in eclipse (Kepler)+m2eclipse with > > > > >>> apache+lucene + apache+lucene+spatial I need to replicate. > > > > >>> > > > > >>> how do you compile the POM and missing dependencies? do you just > > > > create a > > > > >>> local copy of the specific jena snapshot + jars? > > > > >>> > > > > >>> > > > > >> "kepler+maven nature" works for me. I haven't tried mvn > > > eclipse:eclipse > > > > >> > > > > >> or you can build with: > > > > >> > > > > >> mvn clean test > > > > >> > > > > >> Dependencies work with "mvn dependency:resolve" and with > > > > >> Eclipse: "maven->Update Project" > > > > >> > > > > >> Andy > > > > >> > > > > >> > > > > >> > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > > --- > > > > > Marco Neumann > > > > > KONA > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > --- > > > > Marco Neumann > > > > KONA > > > > > > > > > > > > > > > -- > > > > > > --- > > Marco Neumann > > KONA > > > -- --- Marco Neumann KONA
