[ 
https://issues.apache.org/jira/browse/LUCENE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Smiley resolved LUCENE-7280.
----------------------------------
    Resolution: Won't Fix

GeoPointField was removed from lucene/spatial module for 7.x.  LatLonPoint and 
related fields in the lucene/sandbox module have effectively supplanted it.  So 
we could file a new issue similar to this one, however I'm not sure if there 
are committer/PMC members that may object to lucene/spatial-extras depending on 
lucene/sandbox.  I don't for this case since lucene/spatial-extras has more 
broad dependencies already (it's essentially the only module with an external 
dependency).  [~jpountz] I think you may have last expressed comments on 
sandbox inward dependencies?

I think everyone agrees that the current placement of LatLonPoint in 
lucene/sandbox is poor but there is disagreement on wether it move to 
lucene/core or lucene/spatial -- LUCENE-7314.  The situation vexes me.

> SpatialStrategy impl for GeoPointField
> --------------------------------------
>
>                 Key: LUCENE-7280
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7280
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: modules/spatial-extras
>            Reporter: David Smiley
>              Labels: newdev
>
> It would be cool if were a SpatialStrategy (an abstraction in spatial-extras 
> module) implementation for GeoPointField (in "spatial" module).  In this way 
> code that uses the SpatialStrategy abstraction could leverage this 
> implementation with no code changes, aside from the construction part.  
> Perhaps the biggest part of doing this is creating implementations of the 
> Spatial4j abstractions to, ultimately, create Shape impls that are basic 
> POJOs to hold the basic data but otherwise do no calculations (throw 
> exceptions from relate(), etc.).  Then, SpatialStrategy.createQuery can cast 
> the Shape to see what sort of shape it is before calling, e.g. 
> GeoPointInPolygonQuery.  Those Spatial4j abstractions might be used for other 
> future SpatialStrategy wrappers, like for Geo3DPoint, or LatLonPoint.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to