-
Notifications
You must be signed in to change notification settings - Fork 90
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
feat: add polar polygon support #585
base: master
Are you sure you want to change the base?
feat: add polar polygon support #585
Conversation
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
"proj4": "+proj=stere +lat_0=90 +lat_ts=70 +lon_0=-45 +k=1 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs", | ||
"title": "NSIDC Sea Ice Polar Stereographic North" | ||
} | ||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not positive we want to include these. I hardcode the proj4
defs later on so that the polar split function can work even if they are not provided here (and they won't show up in the UI).
Ah, that test failure reminds me: JSTS, when splitting/polygonizing, does not linearly interpolate the altitude between the two points. Do we want to do that? |
…here:THIN-12559 to master * commit 'd5322dd24c94ba4d9eff16b59b2eb5438bd4c159': fix(punyparent): fixed glitchyness fix(punyparent): fixed puny parent to debounce on change
This algorithm does not work well for large polygons due to the stereographic projections. I'm considering adapting Cesium's approach of splitting the polygon by the meridian plane in 3D Cartesian space. |
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 #540, #579
Test: