Ah sorry, I misunderstood your schema and input document.
The CRS in your json is not used by ES, it just assumes WGS84. So the polygon
is plain invalid, as if you calculate it modulo 360 degrees, the polygon is
just wrong and has many overlapping lines.
I was thinking you want to test the new
Hi,
Yes. With different projections there is one issue: Elasticsearch only converts
the polygon points to wgs84. But depending on the projection, the lines between
the points may have a different shape in reality (no longer lines, but maybe
curves), but as only the line endpoints are converted
Thanks for the help! This isn't very clear in the Elasticsearch docs. Upon
converting to WGS-84 everything seems to index fine.
Van: Ignacio Vera
Verzonden: donderdag 4 juni 2020 14:01
Aan: java-user@lucene.apache.org
Onderwerp: Re: Tessellate exception in Elast
I think this is not a lucene issue. Elasticsearch geo_shape only supports
(and it assumes) polygons on the WGS-84 reference system.
On Thu, Jun 4, 2020 at 1:38 PM Claeys Wouter
wrote:
> Hi,
>
> This is the original polygon:
>
> {
>"crs":{
> "type":"name",
> "properties":{
>
Hi,
This is the original polygon:
{
"crs":{
"type":"name",
"properties":{
"name":"urn:ogc:def:crs:EPSG::31370"
}
},
"type":"MultiPolygon",
"coordinates":[
[
[
[
171044.231002,
175818.094268
Hi,
I think your polygon has intersecting edges but it is difficult to
reproduce with that output. Could you provide the original polygon you are
trying to index?
Thanks!
On Thu, Jun 4, 2020 at 11:30 AM Claeys Wouter
wrote:
> Hi,
>
> This is an error which we get in Elasticsearch when trying t
Hi,
This is an error which we get in Elasticsearch when trying to index geo_shape
fields but it seems this can be narrowed down to a problem in Lucene. We can
reproduce the problem withe ES 6.8.x and ES 7.7.x. This is the error we are
getting:
Caused by: java.lang.IllegalArgumentException: Una
