[
https://issues.apache.org/jira/browse/LUCENE-7202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236589#comment-15236589
]
Robert Muir commented on LUCENE-7202:
-------------------------------------
Another way to see it: imagine there are 3 public classes:
* GeoPoint: 1 dimension with morton z encoding
* LatLonPoint: 2 dimensions
* Geo3dPoint: 3 dimensions
What better names can these classes have? I think this is a better place to
start than worrying about modules. And i do honestly feel we can just have
these 3 classes (and only these 3) public. I also know for a fact the 3d causes
confusion with elevation, yes, practically if you want to do that, just index
an integer field totally unrelated with any of these and people will be happy.
But we should eliminate confusion.
> 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]
