[
https://issues.apache.org/jira/browse/LUCENE-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218875#comment-15218875
]
David Smiley commented on LUCENE-7152:
--------------------------------------
-1 sorry. I've been following LUCENE-7150 and it's unclear to me why GeoUtils
should be added to core. It seems reasonable that the spatial3d module have a
dependency on the spatial module. Likewise I expect spatial-extras will depend
on the spatial module in the future too when a GeoPointSpatialStrategy gets
written. If in the future for reasons we might not forsee today we would like
to use GeoUtils in non-spatial modules (perhaps expressions?), then I could
understand putting it in core. I just think it's better organized to keep
spatial code in our spatial modules.
> Refactor lucene-spatial GeoUtils to core
> ----------------------------------------
>
> Key: LUCENE-7152
> URL: https://issues.apache.org/jira/browse/LUCENE-7152
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Nicholas Knize
>
> {{GeoUtils}} contains a lot of common spatial mathematics that can be reused
> across multiple packages. As discussed in LUCENE-7150 this issue will
> refactor GeoUtils to a new {{o.a.l.util.geo}} package in core that can be the
> home for other reusable spatial utility classes required by field and query
> implementations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
