[ https://issues.apache.org/jira/browse/SOLR-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-13467: -------------------------------- Description: Here I'm adding a dependency on [Google S2 Geometry|http://s2geometry.io] (121KB) so that we can use {{prefixTree="s2"}} on a spatial field type that is using Geo3D. Lucene spatial-extras already has this dependency, albeit it is optional. I enhanced tests to exercise it. Additionally, I document here a strictness Geo3D has in which the polygon points must be provided in a particular order or else the interpretation of the shape is inverted. This so-called "right hand rule" order is somewhat standard but some libs (like JTS) don't care. was:There's a limitation/gotcha on Geo3D in which the polygon points must be provided in a particular order or else the interpretation of the same is inverted. In addition, lets add a reference to {{prefixTree="s2"}} and possibly a test for the same. Component/s: spatial Summary: Spatial: Add S2 lib for more efficient Geo3D indexes (was: Ref guide: spatial: document Geo3D better) Originally this was just going to be about documenting the point order in the ref guide but then I added a test, then added S2, then realized -- oh yeah, S2 isn't in Solr, so.... scope creep. It'd be nice to have S2 be the default when Geo3D is used, but that's best done in Lucene and thus a separate issue. This would require knowledge of the Version since it affects the index. Any way I don't have time for that now. > Spatial: Add S2 lib for more efficient Geo3D indexes > ---------------------------------------------------- > > Key: SOLR-13467 > URL: https://issues.apache.org/jira/browse/SOLR-13467 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation, spatial > Reporter: David Smiley > Assignee: David Smiley > Priority: Major > > Here I'm adding a dependency on [Google S2 Geometry|http://s2geometry.io] > (121KB) so that we can use {{prefixTree="s2"}} on a spatial field type that > is using Geo3D. Lucene spatial-extras already has this dependency, albeit it > is optional. I enhanced tests to exercise it. > Additionally, I document here a strictness Geo3D has in which the polygon > points must be provided in a particular order or else the interpretation of > the shape is inverted. This so-called "right hand rule" order is somewhat > standard but some libs (like JTS) don't care. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org