Hello David, Thanks for your response. I'm working deeply in this and it's fully decided that solr 4.1 + JTS is going to be supporting the map navigation for a 'public facing' GIS solution, i.e. will deliver the objects return by a bounding box intersection. Initially decided to index EVERYTHING and it worked fine. But this is in dev because I'm thinking, for production environment, I'll index only points and the (polygons and/or lines) pre-calculated bounds. I can live with the error of intersecting the bounds of an object that is not going to be showing in the map.
Besides the navigation, I'm also querying back solr with points in polygon intersection for thematic mapping, heatmaps, clustering, etc. but for that I don't need the polygon index. On the other hand, If I later want to do some polygon on polygon intersection it might be handy to have a different field for indexing the polygon ... Can you give me a bit more detail on your idea of (...) writing such a Qparser should be pretty easy for your own needs (...) Thanks Guilehrme -----Original Message----- From: Smiley, David W. [mailto:dsmi...@mitre.org] Sent: quarta-feira, 27 de Fevereiro de 2013 8:26 To: solr-user@lucene.apache.org Subject: Re: solr 4.1 spatial with JTS - spatial query withitin a WKT polygon contained within another query ... Hi Guilherme, That's a neat idea for a feature. It'd be nice if there was a proper Solr "Qparser" for these fields because that would then make a nice extension point to further dereference the shape reference from the index itself. There is a JIRA issue for that. At least writing such a Qparser should be pretty easy for your own needs. In my spatial app, the polygons aren't in the index so I wouldn't use it but we do have an ongoing problem of constantly re-sending large polygons that repeatedly need to get re-parsed. ~ David Smiley On 2/15/13 1:22 PM, "Pires, Guilherme" <guilherme.pi...@cgi.com> wrote: >Hello, > >Thanks for the suggestion. > >I actually solved the issue using POST and xmhttp.send(query). However I >think the most important question is do I really need to query an object >to obtain its wkt polygon and then send that polygon again to enquiry >solr geographically? Wouldn't be perfect if I could ... >Geo:intersects(anonject.polygon) ? > >Thanks >Guilherme >________________________________________ >De: Erick Erickson [erickerick...@gmail.com] >Enviado: sexta-feira, 15 de Fevereiro de 2013 13:20 >Para: solr-user@lucene.apache.org >Assunto: Re: solr 4.1 spatial with JTS - spatial query withitin a WKT >polygon contained within another query ... > >I've seen references to upping the packet limit that your servlet >container >allows, but >I don't have the details offhand. It's possible that you're never even >getting to Solr, >looking at the solr log and seeing if anything gets there when you issue >that request >should help. > >Best >Erick > > >On Thu, Feb 14, 2013 at 6:12 AM, Pires, Guilherme ><guilherme.pi...@cgi.com>wrote: > >> Hello Everyone, >> >> I've been integrating Solr 4.1 into a Web GIS solution and it's working >> great. >> I have implemented JTS within Solr 4.1 and indexed thousands of WKT >> polygons provided by XML document genereated by a GE's GIS Core system. >> Everything seems to working out great. >> >> Now I have a feature where I want to query solr with >> geo:intersects((POLYGON(... with a polygon too big to send via xmlhttp >> object. I'm getting a http 505 error. >> >> 1. Is there any other way of sending this huge string back to solr? >> (I've tried GET and POST) >> 2. This polygon was the result of a previous query so, is there a >> way of query inside a query? Something like ,... >> fq=geo:intersects(<another query.spatialfield_with_the_wkt_polygon) ? >> Thanks >> Guilherme >> >> >> >>
