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 <wouter.cla...@vlaanderen.be>
wrote:

> Hi,
>
> This is the original polygon:
>
> {
>    "crs":{
>       "type":"name",
>       "properties":{
>          "name":"urn:ogc:def:crs:EPSG::31370"
>       }
>    },
>    "type":"MultiPolygon",
>    "coordinates":[
>       [
>          [
>             [
>                171044.231002,
>                175818.094268
>             ],
>             [
>                170996.799514,
>                175850.678652
>             ],
>             [
>                170957.441562,
>                175877.716668
>             ],
>             [
>                170946.243418,
>                175861.052668
>             ],
>             [
>                170935.531674,
>                175845.112572
>             ],
>             [
>                170923.57865,
>                175827.325308
>             ],
>             [
>                170906.675354,
>                175802.171388
>             ],
>             [
>                170886.642266,
>                175772.360124
>             ],
>             [
>                170886.478554,
>                175772.116476
>             ],
>             [
>                170951.311002,
>                175727.607548
>             ],
>             [
>                171026.378266,
>                175676.072188
>             ],
>             [
>                171098.875162,
>                175780.555004
>             ],
>             [
>                171090.729754,
>                175786.150716
>             ],
>             [
>                171044.231002,
>                175818.094268
>             ]
>          ]
>       ]
>    ]
> }
>
> Thanks!
>
> ________________________________
> Van: Ignacio Vera Sequeiros <iv...@apache.org>
> Verzonden: donderdag 4 juni 2020 12:24
> Aan: java-user@lucene.apache.org <java-user@lucene.apache.org>
> Onderwerp: Re: Tessellate exception in Elasticsearch
>
> 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 <wouter.cla...@vlaanderen.be
> >
> wrote:
>
> > 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: Unable to Tessellate shape
> > [[9.32134799999767, -3.200485999986995] [-17.716668000008212,
> > -42.5584380000073] [-1.0526679999893531, -53.7565820000018]
> > [14.887427999987267, -64.46832600000198] [32.674692000000505,
> > -76.42134999998962] [57.82861200001207, -93.32464599999366]
> > [87.6398760000011, -113.35773399999016] [87.8835240000044,
> > -113.52144599999883] [47.60754799999995, -48.68899799999781]
> > [-3.9278120000089984, 26.378266000014264] [79.44499600000563,
> > 98.87516200001119] [73.84928399999626, 90.72975399999996]
> > [41.90573200001381, 44.23100199998589] [9.32134799999767,
> > -3.200485999986995] ]. Possible malformed shape detected.
> >         at
> > org.apache.lucene.geo.Tessellator.tessellate(Tessellator.java:114)
> > ~[lucene-sandbox-7.7.3.jar:7.7.3
> 1a0d2a901dfec93676b0fe8be425101ceb754b85 -
> > noble - 2020-04-21 10:31:55]
> >         at
> >
> org.apache.lucene.document.LatLonShape.createIndexableFields(LatLonShape.java:73)
> > ~[lucene-sandbox-7.7.3.jar:7.7.3
> 1a0d2a901dfec93676b0fe8be425101ceb754b85 -
> > noble - 2020-04-21 10:31:55]
> >         at
> >
> org.elasticsearch.index.mapper.GeoShapeFieldMapper.indexShape(GeoShapeFieldMapper.java:146)
> > ~[elasticsearch-6.8.9.jar:6.8.9]
> >
> > This is a very basic geometry. Could someone please explain why this
> shape
> > is invalid?
> >
> >
> >
> >
> > Thanks in advance,
> >
> > Wouter Claeys
> >
>

Reply via email to