==
CALL FOR PAPERS
The 14th Workshop on
Java Technologies for Real-Time and Embedded Systems
JTRES 2016
Part of the
Hi,
I do not fully understand your requirements, but analyzers-kuromoji
(one of extended package for Japanese morphological analysis) has some
custom token attributes.
http://lucene.apache.org/core/6_0_1/analyzers-kuromoji/index.html?org/apache/lucene/analysis/ja/tokenattributes/package-summary.ht
Hi Randy,
Robert already replied to your previous email ... maybe you missed it?
Mike McCandless
http://blog.mikemccandless.com
On Sat, Jun 11, 2016 at 4:05 PM, Randy Tidd wrote:
> Thanks for the help you’ve already given me on getting search with
> LatLonPoint working, the basics are working
Thanks for the help you’ve already given me on getting search with LatLonPoint
working, the basics are working great and with great performance.
I did some testing on some edge cases and discovered that indexing and
searching for points at the minimum and maximum latitude and longitude are not
See this part of the documentation:
https://github.com/apache/lucene-solr/blob/master/lucene/core/src/java/org/apache/lucene/geo/Polygon.java#L30
APIs take newPolygonQuery(Polygon...) which is treated efficiently as
a "multipolygon".
This is also what many standards (e.g. geojson) recommend, othe
Thanks for the help you’ve already given me on getting search with LatLonPoint
working, the basics are working great and with great performance.
I did some testing on some edge cases and discovered that indexing and
searching for points at the minimum and maximum latitude and longitude are not
On Wed, Jun 8, 2016 at 10:54 AM, Randall Tidd wrote:
> >> I see that it still depends on JTS.
> >
> > Correction: LatLonPoint most definitely does NOT depend on JTS
>
> I’m sorry this is my mistake, I was using
> org.locationtech.spatial4j.context.jts.JtsSpatialContext in my example
> which depe
