Strange latitude axis - Stereographic Equal-Angle projection (-JS)
|Target version:||Candidate for next bugfix release|
I'm getting a strange latitude axis in some cases when plotting with -JS.
In bad.bat I'm giving the grid to the -R-argument giving a strange latitude axis.
In good.bat I'm giving the region explicitly (-R-180/180/64/90) which gives good latitude axis.
In dummy.bat I'm creating a grid with just a constant value. Then, giving the grid to the -R-argument works just fine.
Happens with all MAP_FRAME_TYPEs
I'm using Version 5.2.1 (r15220)
#1 Updated by Paul over 2 years ago
- Status changed from New to In Progress
- Assignee set to Paul
So this happens because there is a check for global grids, i.e., that west-east ~ 360. However, your grid is a bit sloppy:
x:actual_range = -180.000000000033, 179.999999999966 ;
so e-w = 359.999999999998977
and that fails our quite strict test for 360. We will see where we can add in the relaxation. The noise probably comes from Arc doing math in float or something.
#10 Updated by Andreas about 2 years ago
It's simply too time consuming; I've tried before, and after reading your comment - I just tried again just now without luck. I have too little experience with this kind of stuff (I was able to compile GMT 4.5.n due to the great parameter generator and the install script - super simple). I followed the instructions (http://gmt.soest.hawaii.edu/projects/gmt/wiki/BuildingGMT), but I cant even get past the build dependencies section - the system cannot find nmake (which should be included in the SDK?!). I would love to be able to build it myself! So any tips is greatly appreciated.
#11 Updated by Joaquim about 2 years ago
Ah right, you are on Windows. So you are the perfect Guinea Pig for me
Download all the dependencies from here and edit (minor edition) the ConfigUser.cmake included
Regarding the nmake issue, not sure. I use a full VS installation and than only have to open a command shell where the needed VS variables are pre-set.
Well what I really do is to call the batch that sets those env vars. Like:
call "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" amd64
or (for VS2015)
call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
#14 Updated by Andreas almost 2 years ago
- File bad_09042017.png added
Sure looks a lot better now, Paul. The annotations plotted at the pole in the upper middle figure is a bit awkward, but this is maybe more related to a non-optimal -B, than the issue itself.
bad_09042017.png made from running bad.bat with 5.3.3.