[ 
https://issues.apache.org/jira/browse/LUCENE-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049866#comment-17049866
 ] 

ASF subversion and git services commented on LUCENE-9150:
---------------------------------------------------------

Commit ab6fb77c63df5a8d347c0d67335e8919df683f64 in lucene-solr's branch 
refs/heads/branch_8x from Nicholas Knize
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ab6fb77 ]

LUCENE-9150: Restore support for dynamic PlanetModel in spatial3d


> Restore support for dynamic PlanetModel in Geo3D
> ------------------------------------------------
>
>                 Key: LUCENE-9150
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9150
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Nick Knize
>            Priority: Major
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> LUCENE-7072 removed dynamic planet model support in Geo3D. This was logical 
> at the time (given the state of Lucene and spatial projections and coordinate 
> reference systems). Since then, however, there have been a lot of new 
> developments within the OGC community around [Coordinate Reference 
> Systems|https://docs.opengeospatial.org/as/18-005r4/18-005r4.html], [Dynamic 
> Coordinate Reference 
> Systems|http://docs.opengeospatial.org/DRAFTS/18-058.html], and [Updated ISO 
> Standards|https://www.iso.org/obp/ui/#iso:std:iso:19111:ed-3:v1:en].
> It would be useful for Geo3D (and eventually LatLon*) to support different 
> geographic datums to make lucene a viable option for indexing/searching in 
> different spatial reference systems (e.g., more accurately computing query 
> shape relations to BKD's internal nodes using datum consistent with the 
> spatial projection). This would also provide an alternative to other 
> limitations of the {{LatLon*/XY*}} implementation (e.g., pole/dateline 
> crossing, quantization of small polygons). 
> I'd like to propose keeping the current WGS84 static datum as the default for 
> Geo3D but adding back the constructors to accept custom planet models. 
> Perhaps this could be listed as an "expert" API feature?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to