[
https://issues.apache.org/jira/browse/SOLR-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781172#action_12781172
]
Chris A. Mattmann commented on SOLR-1586:
-----------------------------------------
For reference, I'm going to put up a patch (or series of them) on this issue
that implements Ryan McKinley's suggestion (from SOLR-773):
bq. It would be great if the schema field type could define everything needed
to index and search. There are (at least) three approaches to indexing points
that each have their advantages (and disadvantages) - we should be able to
support any of these options.
* GeoPointField (abstract? the standard stuff about dealing with points)
** GeoPointFieldHash (represented as a GeoHash, fast bounds query (with
limited accuracy))
** GeoPointFieldTiers (highly scalable, fast, complex)
*** GeoPointFieldTrie (...)
* GeoLineField...
* GeoPolygonField...
bq. I think it makes sense to try to follow the georss format to represent
geometry:
{code}
<georss:point>45.256 -71.92</georss:point>
<georss:line>45.256 -110.45 46.46 -109.48 43.84 -109.86</georss:line>
<georss:polygon>
45.256 -110.45 46.46 -109.48 43.84 -109.86 45.256 -110.45
</georss:polygon>
<georss:box>42.943 -71.032 43.039 -69.856</georss:box>
{code}
> Create Spatial Point FieldTypes
> -------------------------------
>
> Key: SOLR-1586
> URL: https://issues.apache.org/jira/browse/SOLR-1586
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 1.5
>
>
> Per SOLR-773, create field types that hid the details of creating tiers,
> geohash and lat/lon fields.
> Fields should take in lat/lon points in a single form, as in:
> <field name="foo">lat lon</field>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
