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.

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

Polar polygon support #540

Open
wallw-teal opened this issue May 9, 2019 · 0 comments · May be fixed by #585
Open

Polar polygon support #540

wallw-teal opened this issue May 9, 2019 · 0 comments · May be fixed by #585
Assignees

Comments

@wallw-teal
Copy link
Contributor

Our support for polar polygons leaves a lot to be desired. Drawing or loading a polygon near (but not necessarily containing) the pole can result in unexpected behavior.

3D (note artifacts):
Screen Shot 2019-05-09 at 9 28 09 AM

The artifacts come from how the polygon is represented in 2D, which is visualized like so:
Screen Shot 2019-05-09 at 9 30 10 AM

Even more regular polygons which do not produce artifacts
Screen Shot 2019-05-09 at 9 26 59 AM

still have issues with their 2D representation:
Screen Shot 2019-05-09 at 9 27 32 AM

These polygons should have both the correct 2D representation (to be properly queried against the spatial index and against remote servers) and the correct 3D display.

@wallw-teal wallw-teal self-assigned this May 9, 2019
wallw-teal added a commit to wallw-teal/opensphere that referenced this issue May 31, 2019
Adds support for polar polygons by splitting them by the meridian

plane for display/query in 2D. Additionally, queries for OGC servers

such as GeoServer are now split over the antimeridian in the event

that the remote server does not allow coordinates outside of the

longitudes [-180, 180].

resolves ngageoint#540, ngageoint#579
@wallw-teal wallw-teal linked a pull request May 31, 2019 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant