Hi Jonathan,
I would argue against them being different quantities because there
exist transformations between these various heights. Is that not enough
to indicate they are the same quantity?
Ethan
Jonathan Gregory wrote:
Dear Jon
- height relative to the ellipsoid
- height relative
collection point of view, maybe, but stops there. Most of us use
center of interval as default, particularly since our semantics are not
good enough to detect accumulation (which is the only case where end of
interval is natural).
Benno
On Thu, Oct 22, 2009 at 6:08 PM, Ethan Davis eda
Conformal (2SP) not 9802).
Ethan
--
Ethan Davis UCAR Unidata Program
eda...@unidata.ucar.eduhttp://www.unidata.ucar.edu
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http
-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
--
Ethan Davis UCAR Unidata Program
eda...@unidata.ucar.eduhttp://www.unidata.ucar.edu
://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
--
Ethan Davis UCAR Unidata Program
eda
://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata
--
Ethan Davis UCAR Unidata Program
eda...@unidata.ucar.eduhttp://www.unidata.ucar.edu
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
http
alias terms.
... Just found this in the About the CF Standard Name Table page:
The use of an alias for the standard_name attribute when
writing new data is not recommended.
Perhaps some discussion of standard name aliases should be added to
Section 3.3 Standard Name?
Ethan
--
Ethan Davis
with CRS and is more
recently trying to include concepts to cover dimensionless vertical
coordinates (sorry, not finding that specification).
Hope that's helpful,
Ethan
[1] http://www.opengeospatial.org/standards/netcdf
[2] https://portal.opengeospatial.org/files/?artifact_id=51908
--
Ethan Davis
.gov/trac/ticket/80
> ,
> which will be in CF 1.7, as will http://cf-trac.llnl.gov/trac/ticket/69,
> which
> allows WKT to be stored in a CF attribute. CF and OGC CRS have different
> views
> of the data space, so I don't think we can expect to make them look the
> same,
>
weather data. These conventions will work for polar orbiting
> satellite level 1b space weather data also. Level 2 space weather products
> ill require additional constructs,
>
> Business has been lousy. Otherwise, I would love to come !
>
>
> very respectfully,
>
>
).
>
> - Steve
>
>
>
>
> On 3/27/2016 9:24 PM, Ethan Davis wrote:
>
> Hi all,
>
> As some of you have heard, we are holding a meeting to discuss current and
> future netCDF-CF efforts and directions. The m
he bills. *
>
> Thanks !
>
> randy
>
>
>
> _
>
> Randy C Horne (rho...@excaliburlabs.com)
> Principal Engineer, Excalibur Laboratories Inc.
> voice & fax: (321) 952.5100
> cell: (321) 693.1074
> url: http://www.excaliburlabs.
Hi all,
Just a reminder for anyone attending EGU in Vienna this week.
Please join us for a splinter meeting to discuss netCDF-CF (session SMP32
[1]). The meeting will be in room 2.96 on 21 April 2016 (Thursday),
15:30-17:00.
Hope to see you there.
Ethan
[1]
[2]. The abstract submission deadline is the 3rd of
August, 11:59 P.M. EDT.
Thank you,
Ethan Davis
Stefano Nativi
Lesley Wyborn
Ben Domenico
[1] http://fallmeeting.agu.org/2016/
[2] https://agu.confex.com/agu/fm16/preliminaryview.cgi/Session13459
___
CF
Hi Chris,
> I'm going to venture a guess that the netcdf Java libs can [handle the
> "T"] (anyone know for sure?)
Yes, the netCDF-Java library can parse date/time strings with the "T".
Ethan
On Fri, Sep 23, 2016 at 1:26 PM, Chris Barker wrote:
> On Thu, Sep 22, 2016
I totally agree. Don't deprecate anything but definitely encourage ISO
8601:2004(E) with the caveat of requiring an offset-from-Z indicator.
Cheers,
Ethan
On Fri, Sep 23, 2016 at 9:38 AM, Bob Simons - NOAA Federal <
bob.sim...@noaa.gov> wrote:
> Seth McGinnis said:
> "I hesitate to support
Hi all,
Just a quick note on Chris' CF 2 question (until I have a bit more time to
think more fully on this discussion) ...
The EC netCDF-CF project that Ben mentioned is working on a number of CF
extension efforts that are looking to use features of the netCDF enhanced
data model. Those
Hi all,
We just posted the agenda for the workshop [1]. There will be some minor
tweaks to the schedule coming. Please take a look and let us know if you
have any suggestions for changes to the content or schedule.
We will have a session for a series of short lightning talks. There is a
spot to
re for Atmospheric Science
> Department of Meteorology
> School of Mathematical, Physical and Computational Sciences
> University of Reading (UK)
> http://antonio.cofino.es
>
> On 26/07/17 18:10, Ethan Davis wrote:
>
> Hi all,
>
> As many of you know, we are holding an "A
Hi all,
As many of you know, we are holding an "Advancing netCDF-CF" workshop [1]
on 6-8 September 2017 at UCAR in Boulder, CO USA. This workshop will focus
on efforts to advance the Climate and Forecast (CF) metadata conventions
for netCDF (netCDF-CF). The meeting is being hosted by the
Hi all,
We will be holding an "Advancing netCDF-CF" workshop on 6-8 September 2017
at UCAR in Boulder, CO USA.
Please save the date. More information will be coming soon.
Thanks,
The Workshop Organizing Team
___
CF-metadata mailing list
Hi Heiko and David,
Its been awhile since I looked at this but I don't think the Trac ticket
covers the order of the dimensions. Here's the PR I put together in
February for the missing string length dimension issue. It adds definitions
for dimensions but does nothing regarding dimension order.
Forgot to mention ...
There will be WebEx for remote participation. Connection and dial-in
details will be posted on the workshop web page once available.
On Fri, Jun 1, 2018 at 3:07 PM, Ethan Davis wrote:
> Hi all,
>
> Just a reminder that the 2018 netCDF-CF Workshop [1] will be
Hi all,
Just a reminder that the 2018 netCDF-CF Workshop [1] will be on 19-20 June
2018 at the University of Reading in the UK.
The agenda, as it currently stands, is available on the workshop web page
[1] (or directly here [2]). Suggestions are still welcome.
If you plan to attend, please be
Hi all,
As many of you know, the 2018 netCDF-CF Workshop [1] will be on 19-20 June
2018 at the University of Reading in the UK. This workshop will focus on
efforts to advance the Climate and Forecast (CF) metadata conventions for
netCDF (netCDF-CF). The meeting is being hosted by the National
Hi all,
The last sentence at the end of the first paragraph in Section 6.1 "Labels"
[1] says:
Example H.1, "Point data" illustrates another application for labels.
However, that example doesn't have any labels. Section 6.1 was rewritten
when the DSG chapter was added. Looking at the last draft
Hi Jim, all,
I'm a bit confused by the "clockwise" and "anticlockwise". You mention the
orientation of the observer but not the location/orientation of the clock.
My assumptions (not sure why) for the clock: for roll, the observer (who is
facing forward) would be facing the clock; for pitch, the
r as pointing forward and the Z axis unit vector as pointing down.
>
> Thoughts?
>
> Grace and peace,
>
> Jim
>
> On 8/29/18 1:32 PM, John Helly wrote:
>
> Perhaps one should refer to the discipline of hydrostatics for help with
> this? This paper, pulled from a q
nal and in use, it would
> be major rework for GOES-R to use a yet to be defined standard name (such
> as projection_x_angilar_coordinate and projection_y_angular_coordinate).
>
>
> Not sure what to d about this ….
>
>
>
> v/r
>
> randy
>
>
>
> On Apr 9
meters (not radians).
> > >
> > > The GOES-R designers (specifically me) inadvertently used these two
> > > standard names, not realizing they should NOT have used them because a
> > > standard name can not have two different canonical units.
>
Hi all,
The "Geostationary projection" section of Appendix F "Grid Mappings" says
The x (abscissa) and y (ordinate) rectangular coordinates are identified by
the standard_name attribute values projection_x_coordinate and
projection_y_coordinate respectively. In the case of this projection, the
define a new
>
> > standard name and change App F.
>
> > >
>
> > > However, I realise that you need some workrounds to use during the
>
> > > (possibly
>
> > > infinite) time before this change is thoroughly implemented, and for
>
> > &
Hi all,
Please save the date for the 2018 netCDF-CF Workshop, it will be on 19-20
June 2018 at the University of Reading in the UK.
More information will be coming soon.
Thanks,
The Workshop Organizing Committee
___
CF-metadata mailing list
Hi all,
We will hold a 2019 CF Workshop during the week of 15 July 2019. It will be
held as a series of sessions within the ESIP Summer Meeting [1] in Tacoma,
WA (about 40 miles south of Seattle). We are looking at a day long meeting
(probably spread across two half days) but don’t have the exact
Hi all,
The CF Workshop to be held in Tacoma, WA (south of Seattle) in July will
start in the late afternoon on 16 July (Tuesday) and continue most of the
day of 17 July (Wednesday). Here's the session schedule (Seattle time - US
Pacific) and the current rough plan for the agenda:
Tuesday, 16
Hi all,
Remote participation information is in the individual session pages:
Session 1 (in about 3 hours)
-
https://2019esipsummermeeting.sched.com/event/PtPD/netcdf-cf-workshop-part-i
Ethan
___
CF-metadata mailing list
CF-metadata@cgd.ucar.edu
36 matches
Mail list logo