The custom line types were implemented in such a way that only one custom line was stored. So if the plot is drawn with lines -- either a PLOT, CONTOUR, or VECTOR plot with /COLOR=(r,g,b,a) -- then trying to also use custom colors in the graticule lines messed up the definition given in the plotting command.
It's a simple matter to define further lines, keeping a count of those extra lines which is cleared with each new plot. I've checked in changes to do this.
The graticule syntax allows the vertical and horizontal graticule lines to be defined separately, as well as large and small tics, so possibly up to 4 more lines could be defined. Examples of this are in the documentation and the new benchmark script bn_py_graticules.jnl
Also fixes to address the question here, where PyFerret doesn't know what direction to put some of the dimensions.
https://www.pmel.noaa.gov/maillists/tmap/ferret_users/fu_2019/msg01010.html
by taking into account that the file has 2-D coordinate variables for longitude and latitude and those give us the information to put dimensions in the X and Y directions
Also another fix to an issue Ned noted, having to do with sending coordinate information to PPLUS with enough resolution.
6/27/2022 committed code changes to address issue #112.
The custom line types were implemented in such a way that only one custom line was stored. So if the plot is drawn with lines -- either a PLOT, CONTOUR, or VECTOR plot with /COLOR=(r,g,b,a) -- then trying to also use custom colors in the graticule lines messed up the definition given in the plotting command.
It's a simple matter to define further lines, keeping a count of those extra lines which is cleared with each new plot. I've checked in changes to do this.
The graticule syntax allows the vertical and horizontal graticule lines to be defined separately, as well as large and small tics, so possibly up to 4 more lines could be defined. Examples of this are in the documentation and the new benchmark script bn_py_graticules.jnl
Also fixes to address the question here, where PyFerret doesn't know what direction to put some of the dimensions. https://www.pmel.noaa.gov/maillists/tmap/ferret_users/fu_2019/msg01010.html by taking into account that the file has 2-D coordinate variables for longitude and latitude and those give us the information to put dimensions in the X and Y directions
Also another fix to an issue Ned noted, having to do with sending coordinate information to PPLUS with enough resolution.
6/27/2022 committed code changes to address issue #112.