[LUCENE-7056] Separate Geo3DPoint into another package from the rest of Geo3D

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 6.0
• Component/s: modules/spatial3d
• Lucene Fields: New
• Assignee: David Smiley
• Reporter: David Smiley
• Created: 29/Feb/16 17:56
• Updated: 28/Aug/22 14:50
• Resolved: 08/Mar/16 04:43

Description

The original description follows; it's greater in scope than the new title:

---

This is a proposal for the "spatial3d" module to be purely about the shape/geometry implementations it has. In Lucene 5 that's actually all it has. In Lucene 6 at the moment its ~76 files have 2 classes that I think should go elsewhere: Geo3DPoint and PointInGeo3DShapeQuery. Specifically lucene-spatial-extras (which doesn't quite exist yet so lucene-spatial) would be a suitable place due to the dependency. Eventually I see this module migrating elsewhere be it on its own or a part of something else more spatial-ish. Even if that never comes to pass, non-Lucene users who want to use this module for it's geometry annoyingly have to exclude the Lucene dependencies that are there because this module also contains these two classes.

In a comment I'll suggest some specifics.

Issue Links

• is related to: LUCENE-6607 Move geo3d to Lucene's sandbox module