[
https://issues.apache.org/jira/browse/LUCENENET-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Itamar Syn-Hershko updated LUCENENET-489:
-----------------------------------------
Issue Type: Improvement (was: Bug)
> New spatial module
> ------------------
>
> Key: LUCENENET-489
> URL: https://issues.apache.org/jira/browse/LUCENENET-489
> Project: Lucene.Net
> Issue Type: Improvement
> Components: Lucene.Net Contrib
> Affects Versions: Lucene.Net 3.0.3, Lucene.Net 3.5, Lucene.Net 4.0
> Reporter: Itamar Syn-Hershko
>
> Since the current spatial implementation sucks, I ported the new Lucene
> spatial module, which is based on spatial4j.
> For that end, I ported spatial4j to .NET:
> https://github.com/synhershko/Spatial4n
> And the spatial-lucene module into contrib:
> https://github.com/synhershko/lucene.net/tree/spatial2trunk
> All tests pass, but there aren't many so I encourage you guys to throw as
> many tests as you can on it. We are already using it with RavenDB and it
> looks good.
> To get this to work I ported some pieces from newest Lucene (FunctionQuery,
> Bits, FixedBitSet), and when the time comes you can probably just take those
> from there.
> The Spatial4n project is under the ASL but should stay external to the
> Lucene.Net project, just like spatial4j is external to Lucene.
> I worked off git, and probably the easiest way to merge this in is using
> git-svn: http://learn.github.com/p/git-svn.html . I will also be sending a
> pull-request through github, will see what happens.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
