We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Description of the problem
The issue was first reported in GenericMappingTools/pygmt#1221.
Full script that generated the error
gmt basemap -R0/360/0/1000 -JP8c -Bafg -png map
For -JP8c, the data is Cartesian polar projection. The v6.1.1 image is correct, but in v6.2.0rc1, GMT assumes the angles are longitudes.
System information
gmt --version
The text was updated successfully, but these errors were encountered:
I think this is what #5124 is all about, no? 6.1.1 made the same assumption but now there are W and E due to new modern mode formatting.
Sorry, something went wrong.
Yes, the issue should be fixed by #5124.
Fixed via #5124.
No branches or pull requests
Description of the problem
The issue was first reported in GenericMappingTools/pygmt#1221.
Full script that generated the error
For -JP8c, the data is Cartesian polar projection. The v6.1.1 image is correct, but in v6.2.0rc1, GMT assumes the angles are longitudes.
System information
gmt --version
): 6.2.0rc1The text was updated successfully, but these errors were encountered: