Re: [CF-metadata] [cf-convention/cf-conventions] Introduce the value "surface" for the global attribute featureType (#299)

2020-09-16 Thread Øystein Godøy
I agree with @roy-lowry on having NULL attributes. Given the input by @roy-lowry and @JonathanGregory above I am not sure whether this should be included or not. If included, another keyword than surface should be used, but neither coverage (which is used in many other contexts) is appropriate

Re: [CF-metadata] [cf-convention/cf-conventions] Dead links to GRIB tables at end of section 3.3 (#261)

2020-04-24 Thread Øystein Godøy
> Now, however (twenty years later), standard names are well-established in > their own right, I would say, and the mapping between different metadata > standards belongs better outside the standard, in neutral territory. I fully agree with this and the activities of ENVO are better suited for

Re: [CF-metadata] [cf-convention/cf-conventions] Update geostationary projection to allow clean description of newer generation satellites (#258)

2020-04-13 Thread Øystein Godøy
Although primarily working with polar orbiters this suggested change make sense to me. I fully acknowledge the challenge identified by Randy, but think that shouldn't prevent this update and I think the proposal as stated also acknowledge this. -- You are receiving this because you commented.

Re: [CF-metadata] [cf-convention/cf-conventions] Add new integer types to CF (#243)

2020-02-11 Thread Øystein Godøy
I support this, it will be very welcome. -- 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/243#issuecomment-584844080 This list forwards relevant notifications from

Re: [CF-metadata] [cf-convention/cf-conventions] Remove restrictions on netCDF object names (#237)

2020-01-27 Thread Øystein Godøy
I support the constraint indicated above. Especially allowing slashes and backslashes in names will be confusing. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

Re: [CF-metadata] [cf-convention/cf-conventions] Fix geostationary projection (#230)

2020-01-14 Thread Øystein Godøy
I support this proposal to achieve a consistent approach. -- 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/230#issuecomment-574175582 This list forwards relevant

Re: [cf-convention/cf-conventions] Support of groups in CF (#144)

2018-08-17 Thread Øystein Godøy
Given that, would that call for search by proximity as the only approach in section 5, Scope? Having all potential approaches complicates interpretation of the data and building services on top of them. Stating absolute or relative relations explicitly would be beneficial although I see the

Re: [cf-convention/cf-conventions] Longitude and Latitude not required for projected coordinates (#133)

2018-07-25 Thread Øystein Godøy
> A grid mapping variable is required if the given coordinate variables are > relative to a planetary latitude longitude datum, or to describe the figure > of the Earth used to define the latitude and longitude coordinates, or to > describe another coordinate reference system definition used by