-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Question re angle wrapping #261
Comments
It should handle longitude wrapping but out-of-bounds latitudes are not valid. I also doubt it will handle wrapping from paths which span more than 360 degrees in longitude properly. |
Not sure what you mean by out of bounds latitudes; those points all seem to be between +/- 60 in latitude. |
Yes, I was just very confused by the plot on the left, I see now what it represents. |
When you say it should handle longitude wrapping, do you intend to |
The project operation (which is called automatically) should do that for you. Could you provide the code used to generate the example? Discussing things in the abstract is rarely helpful. |
and
The problem is the branch cut: gv.Path draws connections that should not be there. Nasty piece of code that calls for a utility function... |
It misses half the path that way |
Okay, I see it now. I'll have to look into what cartopy is doing there. |
continuity of paths (contd) Consider the following example
If you leave this running long enough, you will also see points coming in from the lower left |
Don't know what happens to the coastline with proj LambertCylindrical() |
Should be fixed by #278 lon = np.linspace(90, 360+90, 100)
lat = np.linspace(-60,60, 100)
gf.coastline*gv.Path([(lon,lat)])+hv.Curve(lon)*hv.Curve(lat) |
Changed the lon/lat positioning logic:
|
With the small patch in #279 I get this: |
Should gv.Path unwrap the angles internally,
or should it be up to the user calling gv.Path?
The text was updated successfully, but these errors were encountered: