[
https://issues.apache.org/jira/browse/SOLR-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549286#comment-15549286
]
David Smiley commented on SOLR-1906:
------------------------------------
bq. What would the URP do (using the latest available geo fields)? We could
create an enhancement newdev JIRA for this.
Quite simply use GeoHashUtils to parse it to get a lat-lon, and then spit that
out as "lat, lon". I think I like this better than the spatial field type
itself accepting a geohash. Any way, I'm a little skeptical how much people
would care about this feature. If nobody further responds to this issue
wanting this capability within a month, I suggest taking no further action and
closing the issue. Either way, I'm not signing up to do the issue, only to
review & commit a suitable patch.
I filed SOLR-9606 to remove GeoHashField
> Posibility to store actual geohash values in the geohash field type
> -------------------------------------------------------------------
>
> Key: SOLR-1906
> URL: https://issues.apache.org/jira/browse/SOLR-1906
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.5
> Environment: NA
> Reporter: Stian Berger
> Priority: Trivial
> Labels: geohash, spatialsearch
>
> Tried to index some data, containing already encoded geohashes, into a
> geohash field type.
> To my surprise I could not make it work...
> A sneak peak at the source, revealed to me that this field type takes a
> lat/lng pair as it's value, not a geohash...
> Could this be fixed, so the field type also can take actual geohashes?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
