Hi Mitchell, Seems like there's a bug based on what you've shown. * Can you please try RptWithGeometrySpatialField instead of SpatialRecursivePrefixTreeFieldType to see if the problem goes away? This could point to a precision issue; though still what you've seen is suspicious. * Can you try one other query syntax e.g. bbox query parser to see if the problem goes away? I doubt this is it but you seem to point to the syntax being related.
~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Mon, Mar 18, 2019 at 12:24 AM Mitchell Bösecke < mitchell.bose...@forcorp.com> wrote: > Hi everyone, > > I'm trying to index geodetic polygons and then query them out using an > arbitrary rectangle. When using the Geo3D spatial context factory, the data > indexes just fine but using a range query (as per the solr documentation) > does not seem to filter the results appropriately (I get all documents > back). > > When I switch it to JTS, everything works as expected. However, it > significantly slowed down the initial indexing time. A sample size of 3000 > documents took 3 seconds with Geo3D and 50 seconds with JTS. > > I've documented my journey in detail on stack overflow: > https://stackoverflow.com/q/55212622/1017571 > > 1. Can I not use the range query syntax with Geo3D? I.e. am I > misreading the documentation? > 2. Is it expected that using JTS will *significantly* slow down the > indexing time? > > Thanks for any insight. > > -- > Mitchell Bosecke, B.Sc. > Senior Application Developer > > FORCORP > Suite 200, 15015 - 123 Ave NW, > Edmonton, AB, T5V 1J7 > www.forcorp.com > (d) 780.733.0494 > (o) 780.452.5878 ext. 263 > (f) 780.453.3986 >
