Expose cell method parsing.

[rhattersley]

No description provided.

[pelson]

👍 in principle.

[rhattersley]

👍 in principle.

But not in practice? 😉 I've fixed the problem with the copyright period.

@bjlittle - thoughts welcome on the choice of location, etc.

[pelson]

I've fixed the problem with the copyright period.

Then also in practice 😄

@bjlittle - over to you to merge when happy.

[rhattersley]

rhattersley modified the milestone: v1.10, v1.9 just now

It's a new API, so it goes in the next minor release.

[rhattersley]

Go on then @bjlittle ... I dare you! Merge! Merge! Merge! 😛

[pp-mo]

I suppose it's all ok, but I wonder if it wants a bit more quality now it's going public ?

The interface seems a bit odd because the 'cf_var_name' appears redundant -- which it actually is, except for being used to construct a warning message. Maybe you can just document that.

I'm also wishing there was some type of statement about the operational scope, as it's possibly a bit obscure . Do we support "everything" ??
Maybe a simple usage example is helpful, like

>>> parse_cell_methods('varname', 'x: sum(interval:1 hr)')
(CellMethod(method='sum', coord_names=('x',), intervals=('1 hr',), comments=()),)
>>> 

[rhattersley]

I've raised a related question on the xarray PR.

[DPeterK]

This functionality has been added through the now-merged #2039, so I'm going to close this PR.