You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@doutriaux1 Could I get the original script/data from PCMDI/pcmdi_metrics#296? I have seen and solved something similar for plots of boxfill + vector. There, the bounds for boxfill data were slightly larger than the bounds for vector the vector which resulted in similar duplication of labels.
For datasets using a geographic projection, datawc
is only used to specify wrapping (translation of the origin,
for instance from 0:360 to -180:180) and flipping.
For datasets using a geographic projection, datawc
is only used to specify wrapping (translation of the origin,
for instance from 0:360 to -180:180) and flipping.
For datasets using a geographic projection, datawc
is only used to specify wrapping (translation of the origin,
for instance from 0:360 to -180:180) and flipping.
@danlipsa we need urgently to fix the datawc_x1/x2/y1/y2 issue this affects I isolated the issue (in meshfill at least which appear in: PCMDI/pcmdi_metrics#296 ) to be coming from: https://github.com/UV-CDAT/uvcdat/blob/master/Packages/vcs/Lib/vcsvtk/meshfillpipeline.py#L53
Looking at the issue above when runnig it with the EXACT same template and datawc_x1/x2 4 times but slightly different "mesh" coordinatesI get:
which leads to the ugglyness in the issues (ticks offsets, triangle on top of each others)
Another example would be:
png, far from being the requested bounds
The text was updated successfully, but these errors were encountered: