Re: [CF-metadata] [cf-convention/cf-conventions] Add standard names for angular coordinates (#231)
I support the proposal, as erget said it is complementing: https://github.com/cf-convention/cf-conventions/issues/230. When incorpored into the convention, it will give a coherent framework for all the geostationary satellites, that will benefit the whole community -- 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/231#issuecomment-586446461 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Geostationary projection & latitude_of_projection_origin (#246)
That was really helpful, thanks @erget . -- 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/246#issuecomment-586438201 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Add unit_conversion_factor for units in coordinate axis to convert to meters (#248)
As Klaus points out, the units need to come from the Udunits list, so the correct units attribute would be `US_survey_foot`. When I use the Udunits2 linux command line tool, it gives a conversion factor of 0.304801, which is significantly less precise. The XML database that comes with the python package gives the more precise value of 1200/3937. Given that it takes some digging to get the conversion factor out of Udunits, I can see a potential case for providing space to add it explicitly. You would need, however, to indicate what the target units are, e.g. `meter_conversion_factor`. -- 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/248#issuecomment-586209060 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Geostationary projection & latitude_of_projection_origin (#246)
In practice I don't know of any geostationary data that has a non-zero `latitude_of_projection_origin`. However, this is normally a by-product of rectification. Most geostationary products are produced by satellites that are, in fact, geosynchronous - the satellite doesn't stay consistently above a single point on the Earth, as this would expend a lot of fuel, but rather "wobbles" in a figure-eight about its nominal point. This wobble can actually take the satellite several degrees above and below the 0° latitude line. Users never notice this because before products go out they are rectified, so it looks like the satellite was always over the same point, but if someone were to use a geostationary projection to provide geolocated but unrectified imagery, some of the products in a timeline might have a non-zero latitude at origin. I'm not sure what NOAA's doing but my feeling says that PROJ's interpretation is right, so it might be worthwhile to be explicit about this in the Conventions. -- 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/246#issuecomment-586203309 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
Re: [CF-metadata] [cf-convention/cf-conventions] Add unit_conversion_factor for units in coordinate axis to convert to meters (#248)
Units have to come from udunits (see [CF-1.8, 3.1](http://cfconventions.org/Data/cf-conventions/cf-conventions-1.8/cf-conventions.html#units)), which will also provide the conversion factors. In this sense, this proposal seems unnecessary. -- 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/248#issuecomment-586191970 This list forwards relevant notifications from Github. It is distinct from cf-metad...@cgd.ucar.edu, although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to cf-metadata-unsubscribe-requ...@listserv.llnl.gov.
