-
Notifications
You must be signed in to change notification settings - Fork 372
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
Clipping issue with Geostationary/NearsidePerspective #1144
Comments
Probably related to #1081. |
Nope, the problem in #1081 was fixed by matplotlib >=2.2.3. The problem here persists for me with current master and latest matplotlib release (currently 3.0.2). |
So there are a few things going on here. First, Geostationary != NearSidePerspective@equator. Geostationary uses h*scan_angle for the projection coordinates, while Near Side Perspective (NSP) uses x/y distances on a plane tangent to the Earth right below the perspective point. This implies that the shape of the boundary for NSP should be a circle, but we're using a slightly incorrect formula (PR incoming). I should also note that Proj's For Geostationary, the shape of the boundary is more complicated than a circle. This is why we see points outside our boundary; our boundary should extend out further--more of a heavily rounded square I think. For the life of me, though, I can't manage to generate a sane formula, probably because it involves some horrific math on a sphere. In practice, it's not really a big deal, since the only data that actually comes in that projection is at a height of 35e6 m, at which point a circle is a fine approximation. |
This refactors the Geostationary and NearSidePerspective projections so that they can individually set up their boundary, limits, etc. Doing so allows fixing the incorrect boundary being set for NearSidePerspective. The two projections can't share the math for the boundary because they are fundamentally different coordinate systems.
This refactors the Geostationary and NearSidePerspective projections so that they can individually set up their boundary, limits, etc. Doing so allows fixing the incorrect boundary being set for NearSidePerspective. The two projections can't share the math for the boundary because they are fundamentally different coordinate systems.
Fix up the satellite projections (Fixes #1144)
I received this report from a user who was concerned by the points outside the circle of the globe:
produces these images for me.

NearsidePerspective:
Geostationary:

I'm a little confused at the moment as to why these are so different as well.
The text was updated successfully, but these errors were encountered: