@rmendels said
> I have no idea what for example Panoply does, the Coastwatch tools, Thredds,
> Seadas, and some others I can think of, and we should be very careful we
> don't needlessly break things.
Panoply uses the netCDF-Java library to read datasets. When dealing with
projected grids,
> I think that writing down the mapping is a necessary piece of evidence in
> deciding about that and would therefore be a useful first step.
Here are some examples of the WKT version for the CF grid_mappings for the
conversions:
I would recommend adding the `direction` to the axis order as well.
For example `NORTH_POLE_EASTING_SOUTH_NORTHING_SOUTH` or
`SOUTH_POLE_EASTING_NORTH_NORTHING_NORTH`:
See axis maps here:
https://pyproj4.github.io/pyproj/latest/_modules/pyproj/crs/coordinate_system.html
--
You are receiving
Fine by me, I'll merge this as soon as the sample file is uploaded or on
2020-01-27 at latest.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@erget pushed 1 commit.
c73544ef080c8ed7a3c91471322b6e97120f0d6a Clarify deprecation of standard names
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
davidhassell commented on this pull request.
> @@ -79,17 +79,30 @@ __Map parameters:__::
* **`sweep_angle_axis`**
* **`fixed_angle_axis`**
-__Map coordinates:__:: The x (abscissa) and y (ordinate) rectangular
coordinates are identified by the **`standard_name`** attribute values
Excuse me that I did not provide a file. I will add a file until end of this
week.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/212#issuecomment-576712516
This list
JimBiardCics commented on this pull request.
> @@ -79,17 +79,30 @@ __Map parameters:__::
* **`sweep_angle_axis`**
* **`fixed_angle_axis`**
-__Map coordinates:__:: The x (abscissa) and y (ordinate) rectangular
coordinates are identified by the **`standard_name`** attribute values
I've just been reviewing all of the issues in advance of 1.8, and whilst I said
"already merged" issues will be included
(https://github.com/cf-convention/discuss/issues/26), I should have said
"merged by 31st January 2020". It looks like this should have passed the 3 week
timer by then. The
Closed #228.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/228#event-2965665881
This list forwards relevant notifications from Github. It is distinct from
Merged #229 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/pull/229#event-2965664835
This list forwards relevant notifications from Github. It is distinct from
davidhassell commented on this pull request.
> @@ -79,17 +79,30 @@ __Map parameters:__::
* **`sweep_angle_axis`**
* **`fixed_angle_axis`**
-__Map coordinates:__:: The x (abscissa) and y (ordinate) rectangular
coordinates are identified by the **`standard_name`** attribute values
I'm just catching up on this, and I also support the proposal as it stands.
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/cf-convention/cf-conventions/issues/230#issuecomment-576581870
This list forwards relevant
13 matches
Mail list logo
