[
https://issues.apache.org/jira/browse/LUCENE-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238261#comment-15238261
]
Nicholas Knize commented on LUCENE-7202:
----------------------------------------
bq. If i want to do some cool shit with data from mars, its not clear to me how
to use geo3d to do that.
Well this is the nice part. Planetary systems still operate lat/lon. But the
reference constants are different. At the end of the day (like most existing
projection packages) it should be using the same phi theta rho to XYZ
reprojection code.
If y'all want to settle on a name sooner than later I certainly won't hold it
up. I'm just in favor of a simple API that can handle reference systems and
raster order without creating a separate field class for all of them. That'll
just get out of hand and need to change again down the road.
> Come up with a comprehensive proposal for naming spatial modules and
> technologies
> ---------------------------------------------------------------------------------
>
> Key: LUCENE-7202
> URL: https://issues.apache.org/jira/browse/LUCENE-7202
> Project: Lucene - Core
> Issue Type: Task
> Components: modules/sandbox, modules/spatial, modules/spatial3d
> Affects Versions: master
> Reporter: Karl Wright
>
> There are three different spatial implementations circulating at the moment,
> and nobody seems happy with the naming of them. For each implementation
> strategy, we need both a module name and a descriptive technology name that
> we can use to distinguish one from the other. I would expect the following
> people to have an interest in this process: [~rcmuir], [~dsmiley],
> [~mikemccand], etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
