Skip to content

bug longitude matrices in files for standard latitude/longitude domains when force_coordinate_rotation = True #937

@SiTucker

Description

@SiTucker

When attempting to convert some RCM output that has been run over a non rotated domain over Africa with force_coordinate_rotation = True , the real (rather than rotated) longitude matrices have incorrect values (I think out be out by 180 degrees).

I thought that fixing the issues might be as simple as changing
560 rotated_cs = RotatedGeogCS(90., 0., ellipsoid=cs)
to
560 rotated_cs = RotatedGeogCS(90., 180., ellipsoid=cs)

in mip_convert//mip_convert/new_variable.py . Off line testing showed that the correct latitude longitude matrices get produced, however if I try to run get cdds_convert, it crashes with something about an error in cmor.write.

Note I do not have an urgent need for this to be fixed, just reporting in the hope that it can get picked up at some point.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions