[
https://issues.apache.org/jira/browse/SOLR-10039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949437#comment-15949437
]
Hoss Man commented on SOLR-10039:
---------------------------------
[~dsmiley]: can you please update the ref guide with some guidance on this new
field type?
Replacing LatLonType with LatLonPointSpatialField in the list of field types is
easy, but the way the "Spatial" page is written updating it to make meaningful
comments about LatLonPointSpatialField (as compared to RPT) is a lot harder w/o
some first hand knowledge about the merits...
* https://cwiki.apache.org/confluence/display/solr/Spatial+Search
*
https://cwiki.apache.org/confluence/display/solr/Field+Types+Included+with+Solr
> LatLonPointSpatialField
> -----------------------
>
> Key: SOLR-10039
> URL: https://issues.apache.org/jira/browse/SOLR-10039
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: spatial
> Reporter: David Smiley
> Assignee: David Smiley
> Fix For: 6.5
>
> Attachments: SOLR_10039_LatLonPointSpatialField.patch,
> SOLR_10039_LatLonPointSpatialField.patch,
> SOLR_10039_LatLonPointSpatialField.patch,
> SOLR_10039_LatLonPointSpatialField.patch
>
>
> The fastest and most efficient spatial field for point data in Lucene/Solr is
> {{LatLonPoint}} in Lucene's sandbox module. I'll include
> {{LatLonDocValuesField}} with this even though it's a separate class.
> LatLonPoint is based on the Points API, using a BKD index. It's multi-valued
> capable. LatLonDocValuesField is based on sorted numeric DocValues, and thus
> is also multi-valued capable (a big deal as the existing Solr ones either
> aren't or do poorly at it). Note that this feature is limited to a
> latitude/longitude spherical world model. And furthermore the precision is
> at about a centimeter -- less precise than the other spatial fields but
> nonetheless plenty good for most applications. Last but not least, this
> capability natively supports polygons, albeit those that don't wrap the
> dateline or a pole.
> I propose a {{LatLonPointSpatialField}} which uses this. Patch & details
> forthcoming...
> This development was funded by the Harvard Center for Geographic Analysis as
> part of the HHypermap project
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
