You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
The artifacts come from how the polygon is represented in 2D, which is visualized like so:
Even more regular polygons which do not produce artifacts
still have issues with their 2D representation:
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.
The text was updated successfully, but these errors were encountered:
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].
resolvesngageoint#540, ngageoint#579
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):
The artifacts come from how the polygon is represented in 2D, which is visualized like so:
Even more regular polygons which do not produce artifacts
still have issues with their 2D representation:
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.
The text was updated successfully, but these errors were encountered: