[
https://issues.apache.org/jira/browse/SOLR-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549038#comment-15549038
]
David Smiley commented on SOLR-1906:
------------------------------------
Regarding accepting a geohash as input as an alternative to a lat,lon or WKT...
I don't know... I guess so? Patches welcome :-) One could always write an
UpdateRequestProcessor to do such things.
BTW I think GeoHashField should be removed from Solr 7.0; it's dated and I
can't think of any reason why someone would use it.
> 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]
