PR cf-convention/cf-conventions#335 should be good to go - just needs a review
I believe.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I just realized forgot to remove the `workflow_dispatch` event trigger (thus
the update), but now the PR should be good for review.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@lesserwhirls pushed 1 commit.
5104b45a31cbcbacc36d2b2a5b53a0e64aae0eba Extend asciidoc workflow to manage
publication of docs
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
GitHub was having issues yesterday, which held up getting this out. However, I
believe I have it all working now in PR cf-convention/cf-conventions#335.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
In addition to building the conventions and conformance docs, extend the GitHub
Action workflow to manage the publication of the docs to the `gh-pages` branch
based off the workflow of the `travis.yml` config.
# Demonstration
## Pull request against master
PR:
I believe I had volunteered to do this last year...I do apologize.
I can take a look at this first thing tomorrow. It should not be too bad
(famous last words) given that 1) the [building part is already
netCDF-C support for dates/times/calendars is limited to the `ncdump` utility,
and I believe only as a convenience (`nctime0.h` isn't installed as part of the
library). It has been extended over time to be more flexible with respect to
both UDUNITS as well as to better operate with different
> **Opportunity for improvement:**
>
> 1. First of all I find it a bit confusing to have builds on both Travis and
> GitHub Actions. If we ever get the time it might be a good idea to refactor
> this. This is especially important because the build process must be
> maintained ATM in 2 places,
This is great! I would only add that we (mostly @WardF) have been working on
breaking out the NUG from the netCDF-C/C++ documentation, and it is currently
available at:
https://www.unidata.ucar.edu/software/netcdf/documentation/NUG/
The hope is that it will be useful beyond a language agnostic
> This is great!
> Would it be possible to upload the pdf and html individually, not in an
> archive so as to facilitate easy inspection?
That would be great! Currently, the `actions/upload-artifact` github action
does not support it, but it's on their list of improvements (more info
As an example of what this will look like, see
[here](https://github.com/lesserwhirls/cf-conventions/actions/runs/58486955).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
This PR enables a github action to check that PRs do not break the asciidoc
build. If the build is successful, the pdf and html files are uploaded as
artifacts to the action, which allow for easier previews of the generated files.
You can view, comment on, or merge this pull request online at:
> @rschmunk and @lesserwhirls, could panoply and netcdf-java use the Java
> [geotools](https://github.com/geotools/geotools) library to handle [CRS
> WKT](https://docs.geotools.org/stable/userguide/library/referencing/crs.html)?
>
> Would that be straightforward or a major effort?
It would
Totally agree with @erget - I see no reason to be ashamed, and your input and
perspective is certainly appreciated! @magau - would you happen to know of an
easy to access dataset with the map coordinates in `m` instead of radians?
--
You are receiving this because you commented.
Reply to this
lesserwhirls 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
15 matches
Mail list logo
