lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6566) Handle "crosses dateline" cases in BKPointInPolygonQuery
Date Tue, 29 Mar 2016 13:03:25 GMT


Robert Muir commented on LUCENE-6566:

Are you sure we should do this? In many systems, such as GeoJSON these polygons become ambiguous.
I don't think lucene should have heuristics here?

Instead we could spend our time speeding up polygon support, improving testing, supporting
multipolygon and polygon rings, etc, etc.

In it says:
In representing features that cross the antimeridian,
interoperability is improved by cutting geometries so that no single
part crosses the antimeridian. 
A rectangle extending from 40 degrees N, 170 degrees E across the
antimeridian to 50 degrees N, 170 degrees W should be cut in two and
represented as a MultiPolygon.

> Handle "crosses dateline" cases in BKPointInPolygonQuery
> --------------------------------------------------------
>                 Key: LUCENE-6566
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: master, 6.1
> Just like LUCENE-6560, but we should also handle for the polygon case, which seems harder

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message