Changes between Initial Version and Version 1 of Ticket #2606
- Timestamp:
- Jun 1, 2022, 9:23:24 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2606 – Description
initial v1 1 2 1 {{{ 3 2 ``gridOrder`` - specify the grid order of axes defined by the coverage CRS. 3 If not specified, wcst_import will try to automatically derive the gridOrder 4 according to the documentation below. That may fail with unusual data, in which 5 case it will be necessary to set this setting manually for each axis. 4 6 5 7 Axes of a CRS which is not part of the file CRS have gridOrder that is … … 21 23 match the dimension order of the imported variable, which can be checked 22 24 with ``ncdump -h``; e.g. a variable ``float dc(time, lat, lon)`` will have 23 gridOrder ``n`` for time, ``n+1`` for lat, and ``n+2`` for lon. 25 gridOrder ``n`` for time, ``n+1`` for lat, and ``n+2`` for lon. This will work 26 well as long as the data conforms to the `CF-conventions 27 <https://cfconventions.org/Data/cf-conventions/cf-conventions-1.7/cf-conventions.html#dimensions>`, 28 and may otherwise need adjustments if the spatial dimensions are not in Y/X 29 order. 24 30 }}}