Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GeoPolygonFilter not properly handling dateline and pole crossing #9171

Closed
wants to merge 3 commits into from
Closed

GeoPolygonFilter not properly handling dateline and pole crossing #9171

wants to merge 3 commits into from

Commits on Jan 6, 2015

  1. [GEO] GeoPolygonFilter not properly handling dateline and pole crossing 

    By default GeoPolygonFilter normalizes GeoPoints to a [-180:180] lon, [-90:90] lat coordinate boundary. This requires the GeoPolygonFilter be split into east/west, north/south regions to properly return points collection that wrap the dateline and poles. To keep queries fast, this simple fix converts the GeoPoints for both the target polygon and candidate points to a [0:360] lon, [0:180] lat coordinate range. This way the user (or the filter logic) doesn't have to split the filter in two parts.

closes elastic#5968
    @nknize
    nknize committed Jan 6, 2015
    Configuration menu
    Copy the full SHA
    91dc5f4 View commit details
    Browse the repository at this point in the history

Commits on Jan 7, 2015

  1. Updating code formatting.

    @nknize
    nknize committed Jan 7, 2015
    Configuration menu
    Copy the full SHA
    b5a26b0 View commit details
    Browse the repository at this point in the history

Commits on Jan 8, 2015

  1. Updating variable assignments and adding comments to pointInPolygon.

    @nknize
    nknize committed Jan 8, 2015
    Configuration menu
    Copy the full SHA
    fa2f2b0 View commit details
    Browse the repository at this point in the history