hopefully someone is using the lucene spatial toolkit aka LSP aka spatial4j, and can answer this question
we are using this spatial tool for doing searches. overall, it seems to work very well. however, finding documentation is difficult. I have a couple of questions: 1. I have a geohash field in my solr schema that contains indexed geographic polygon data. I want to find all docs where that polygon intersects a given lat/long. I was experimenting with returning distance in the resultset and with sorting by distance and found that the following query works. However, I dont know what distance means in the query. i.e. is it distance from point to the polygon centroid, to the closest outer edge of the polygon, its a useless random value, etc. Does anyone know?? http://solrserver:solrport/solr/core0/select?q=*:*&fq={!v=$geoq%20cache=false}&geoq=wkt_search:%22Intersects(Circle(-97.057%2047.924%20d=0.000001))%22&sort=query($geoq)+asc&fl=catchment_wkt1_trimmed,school_name,latitude,longitude,dist:query($geoq,-1),loc_city,loc_state 2. some of the polygons, being geographic representations, are very big (ie state/province polygons). when solr starts processing a spatial query (like the one above), I can see ("INFO: Building Cache [xxxxxx]") it fills in some sort of memory cache (org.apache.lucene.spatial.strategy.util.ShapeFieldCache) of the indexed polygon data. We are encountering Java OOM issues when this occurs (even when we booested the mem to 7GB). I know that some of the polygons can have more than 2300 points, but heavy trimming isn't really an option due to level of detail issues. Can we control this caching, or the indexing of the polygons, in any way to reduce the memory requirements?? -- View this message in context: http://lucene.472066.n3.nabble.com/question-s-re-lucene-spatial-toolkit-aka-LSP-aka-spatial4j-tp3997757.html Sent from the Solr - User mailing list archive at Nabble.com.
