Merge pull request #476 from sadielbartholomew/batch-update-http-prot…

…ocol

Convert all referenced URLs with HTTP protocol to HTTPS

.github/ISSUE_TEMPLATE/defect-issue.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: http://cfconventions.org/rules.html
+Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: https://cfconventions.org/rules.html
 
 Change proposals should include the following information as applicable.
 If important to the issue, the problem text should be pasted in the body of the issue and proposed fix included.

.github/ISSUE_TEMPLATE/enhancement-issue.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: http://cfconventions.org/rules.html
+Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: https://cfconventions.org/rules.html
 
 If the modification is straightforward and non-controversial, feel free to open a pull request simultaneously with the proposed changes.
 

.github/ISSUE_TEMPLATE/github-usage-issue.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-Before submitting an issue be sure you have read and understand the GitHub contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: http://cfconventions.org/rules.html
+Before submitting an issue be sure you have read and understand the GitHub contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: https://cfconventions.org/rules.html
 
 # Associated pull request
 Link to associated pull request, if present.

.github/ISSUE_TEMPLATE/question-issue.md

@@ -7,4 +7,4 @@ assignees: ''
 
 ---
 
-Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: http://cfconventions.org/rules.html
+Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: https://cfconventions.org/rules.html

.github/ISSUE_TEMPLATE/style-issue.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: http://cfconventions.org/rules.html
+Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: https://cfconventions.org/rules.html
 
 # Associated pull request
 Link to associated pull request, if present.

.github/ISSUE_TEMPLATE/typo-issue.md

@@ -7,7 +7,7 @@ assignees: ''
 
 ---
 
-Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: http://cfconventions.org/rules.html
+Before submitting an issue be sure you have read and understand the github contributing guidelines: https://github.com/cf-convention/cf-conventions/blob/main/CONTRIBUTING.md and the rules for CF changes: https://cfconventions.org/rules.html
 
 # Associated pull request
 Link to associated pull request, if present.

CODE_OF_CONDUCT.md

@@ -11,4 +11,4 @@ Project maintainers who do not follow the Code of Conduct may be removed from th
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.
 
-This Code of Conduct is adapted from the Contributor Covenant (http:contributor-covenant.org), version 1.0.0, available at http://contributor-covenant.org/version/1/0/0/.
+This Code of Conduct is adapted from the Contributor Covenant (http:contributor-covenant.org), version 1.0.0, available at https://contributor-covenant.org/version/1/0/0/.

CONTRIBUTING.md

@@ -2,11 +2,11 @@
 
 Dear CF community member,
 
-Thank you for taking the time to consider making a contribution to the [cf-conventions](http://cfconventions.org/).
+Thank you for taking the time to consider making a contribution to the [cf-conventions](https://cfconventions.org/).
 The netCDF Climate and Forecasting conventions are a product by and for a broad community and your contribution is the key to their usefulness.
 
 This set of guidelines provides a brief overview of the practices and procedures that should be used in fixing, updating, or adding to the conventions.
-It builds on the [rules for CF Convention changes.](http://cfconventions.org/rules.html)
+It builds on the [rules for CF Convention changes.](https://cfconventions.org/rules.html)
 
 As a prerequisite to this guide, please review the community's code of [conduct](https://github.com/cf-convention/cf-conventions/blob/main/CODE_OF_CONDUCT.md).
 The CF community takes great pride in respectful and collegial discourse.
@@ -32,7 +32,7 @@ Currently this is achieved by using an appropriate issue template when creating
 1. **Comments in pull requests.** These should be avoided, unless discussing changes to the wording of a proposal that do not impact on the agreed meaning.
 This is so that the scientific development of the proposal is easily found in one place, i.e. the GitHub issue.
 2. **Role of the issue moderator.** Each issue should have a moderator who guides the discussion through the change process and summarises it occasionally.
-This is described in greater detail in the [CF Conventions Rules](http://cfconventions.org/rules.html).
+This is described in greater detail in the [CF Conventions Rules](https://cfconventions.org/rules.html).
 
 ## Issues and pull requests
 Note that it takes a minimum of three weeks for a change to the content of the CF Conventions to be merged into the Convention's next version.
@@ -54,7 +54,7 @@ A maintainer (who might be the moderator!) merges the issue at earliest on the a
 
 ## Merging of pull requests, and closing and reopening of issues
 
-When an issue and accompanying pull request concludes with an agreed change to the conventions, the pull request is merged into the main branch according to the [Rules for CF Convention Changes](http://cfconventions.org/rules.html).
+When an issue and accompanying pull request concludes with an agreed change to the conventions, the pull request is merged into the main branch according to the [Rules for CF Convention Changes](https://cfconventions.org/rules.html).
 
 The pull request is merged by a member of the Governance Panel or the CF Conventions and Standard Names Committee.
 The person who merges the pull request also closes the issue.

README.md

@@ -1,23 +1,23 @@
-[![Build Status](https://secure.travis-ci.org/cf-convention/cf-conventions.png)](http://travis-ci.org/cf-convention/cf-conventions)
+[![Build Status](https://secure.travis-ci.org/cf-convention/cf-conventions.png)](https://travis-ci.org/cf-convention/cf-conventions)
 
 This repository contains the official source of the CF metadata conventions.
 The source files are built into HTML automatically when changes are merged into this repository.
-The latest build of the specification is held in the `gh-pages` branch and can be seen [here](http://cfconventions.org/cf-conventions/cf-conventions.html).
+The latest build of the specification is held in the `gh-pages` branch and can be seen [here](https://cfconventions.org/cf-conventions/cf-conventions.html).
 
-For the official web site please visit: http://cfconventions.org and the [corresponding GitHub organisation](https://github.com/cf-convention).
+For the official web site please visit: https://cfconventions.org and the [corresponding GitHub organisation](https://github.com/cf-convention).
 
 # Contributing to the CF Conventions
 
 The CF Conventions are changed by changing the source files in this repository.
-The rules for doing this are set forth on the [CF website](http://cfconventions.org/rules.html).
+The rules for doing this are set forth on the [CF website](https://cfconventions.org/rules.html).
 Their implementation in GitHub is described in this repository's [CONTRIBUTING.md file](https://github.com/cf-convention/cf-conventions/blob/master/CONTRIBUTING.md).
 
 # Building the HTML
 
 To convert the AsciiDoc files into the resulting HTML file:
 
 1. Ensure you have [Ruby](https://www.ruby-lang.org/) installed (e.g. `sudo apt-get install ruby`)
-2. Ensure you have a recent version of [Asciidoctor](http://asciidoctor.org/) installed (e.g. `gem install asciidoctor`)
+2. Ensure you have a recent version of [Asciidoctor](https://asciidoctor.org/) installed (e.g. `gem install asciidoctor`)
 3. Get hold of the AsciiDoc files in this repo (e.g. `git clone [email protected]:cf-metadata/cf-conventions.git`)
 4. Build the HTML: `asciidoctor cf-conventions.adoc`
 
@@ -27,9 +27,9 @@ See the [GitHub help](https://help.github.com/) pages and plethora of other git/
 
 Whenever a [pull request](https://github.com/cf-convention/cf-conventions/pulls) is merged, a [travis-ci build](https://travis-ci.org/github/cf-convention/cf-conventions) generates the latest specification draft and adds it to the [gh-pages branch here](https://github.com/cf-convention/cf-conventions/tree/gh-pages).
 The gh-pages branch is deployed to github pages at the following documents:
-- http://cfconventions.org/cf-conventions/cf-conventions.html
-- http://cfconventions.org/cf-conventions/cf-conventions.pdf
-- http://cfconventions.org/cf-conventions/conformance.html
-- http://cfconventions.org/cf-conventions/conformance.pdf
+- https://cfconventions.org/cf-conventions/cf-conventions.html
+- https://cfconventions.org/cf-conventions/cf-conventions.pdf
+- https://cfconventions.org/cf-conventions/conformance.html
+- https://cfconventions.org/cf-conventions/conformance.pdf
 
-These documents are linked in the cf-conventions web site. [source here](https://github.com/cf-convention/cf-convention.github.io) which is published to: http://cfconventions.org/. The latest spec documents are linked from those web pages here: http://cfconventions.org/latest.html.
+These documents are linked in the cf-conventions web site. [source here](https://github.com/cf-convention/cf-convention.github.io) which is published to: https://cfconventions.org/. The latest spec documents are linked from those web pages here: https://cfconventions.org/latest.html.

appa.adoc

@@ -31,7 +31,7 @@ Attribute
 | **`add_offset`**
 | N
 | C, D
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<packed-data>>
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<packed-data>>
 | If present for a variable, this number is to be added to the data after it is read by an application.
 If both **`scale_factor`** and **`add_offset`** attributes are present, the data are first scaled before the offset is added.
 In cases where there is a strong constraint on dataset size, it is allowed to pack the coordinate variables (using add_offset and/or scale_factor), but this is not recommended in general.
@@ -105,7 +105,7 @@ In cases where there is a strong constraint on dataset size, it is allowed to pa
 | **`Conventions`**
 | S
 | G
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
 | Name of the conventions followed by the dataset.
 
 | **`coordinate_interpolation`**
@@ -136,7 +136,7 @@ In cases where there is a strong constraint on dataset size, it is allowed to pa
 | **`_FillValue`**
 | D
 | C, D
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<missing-data>>, and <<ch9-missing-data>>.
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<missing-data>>, and <<ch9-missing-data>>.
 | A value used to represent missing or undefined data.
 Allowed for auxiliary coordinate variables but not allowed for coordinate variables.
 
@@ -193,7 +193,7 @@ Use in conjunction with **`flag_meanings`**.
 | **`history`**
 | S
 | G, Gr
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
 | List of the applications that have modified the original data.
 
 | **`instance_dimension`**
@@ -243,7 +243,7 @@ It is assumed that all years that differ from this year by a multiple of four ar
 | **`long_name`**
 | S
 | C, D, Do
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<long-name>>
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<long-name>>
 | A descriptive name that indicates a variable's content.
 This name is not standardized.
 
@@ -312,7 +312,7 @@ The count variable indicates that the contiguous ragged array representation is
 | **`scale_factor`**
 | N
 | C, D
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<packed-data>>
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<packed-data>>
 | If present for a variable, the data are to be multiplied by this factor after the data are read by an application.
 See also the **`add_offset`** attribute.
 In cases where there is a strong constraint on dataset size, it is allowed to pack the coordinate variables (using add_offset and/or scale_factor), but this is not recommended in general.
@@ -338,31 +338,31 @@ In cases where there is a strong constraint on dataset size, it is allowed to pa
 | **`title`**
 | S
 | G, Gr
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
 | Short description of the file contents.
 
 | **`units`**
 | S
 | C, D
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<units>>
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"], and <<units>>
 | Units of a variable"s content.
 
 | **`valid_max`**
 | N
 | C, D
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
 | Largest valid value of a variable.
 
 | **`valid_min`**
 | N
 | C, D
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
 | Smallest valid value of a variable.
 
 | **`valid_range`**
 | N
 | C, D
-| link:$$http://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
+| link:$$https://www.unidata.ucar.edu/software/netcdf/docs/attribute_conventions.html$$[NUG Appendix A, "Attribute Conventions"]
 | Smallest and largest valid values of a variable.
 |===============
 

appb.adoc

@@ -19,7 +19,7 @@ Next is the **`standard_name_table`** itself, which is bracketed by the tags **`
 
 ----
 <standard_name_table
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="CFStandardNameTable.xsd">
 ----
 

appf.adoc

@@ -64,7 +64,7 @@ __Map coordinates:__:: The x (abscissa) and y (ordinate) rectangular coordinates
 __Notes:__:: Notes on using the **`PROJ`** software package for computing the mapping may be found at
 link:$$http://geotiff.maptools.org/proj_list/azimuthal_equidistant.html$$[http://geotiff.maptools.org/proj_list/azimuthal_equidistant.html]
 and
-link:$$https://proj.org/operations/projections/aeqd.html$$[https://proj.org/operations/projections/aeqd.html].
+link:$$http://proj.org/operations/projections/aeqd.html$$[https://proj.org/operations/projections/aeqd.html].
 
 === Geostationary projection
 
@@ -96,11 +96,11 @@ This means that a given viewing angle described using this model is the result o
 The two axes are conventionally called the sweep-angle and fixed-angle axes; we adhere to this terminology, although some find these terms confusing, for the sake of interoperability with existing implementations.
 
 +
-The algorithm for computing the mapping may be found at link:$$http://www.cgms-info.org/documents/pdf_cgms_03.pdf$$[http://www.cgms-info.org/documents/pdf_cgms_03.pdf].
+The algorithm for computing the mapping may be found at link:$$https://www.cgms-info.org/documents/pdf_cgms_03.pdf$$[https://www.cgms-info.org/documents/pdf_cgms_03.pdf].
 This document assumes the point of observation is directly over the equator, and that the **`sweep_angle_axis`** is y.
 
 +
-Explanatory diagrams for the projection may be found link:$$http://proj.org/operations/projections/geos.html$$[on the PROJ website], as well as notes on using the PROJ software for computing the mapping.
+Explanatory diagrams for the projection may be found link:$$https://proj.org/operations/projections/geos.html$$[on the PROJ website], as well as notes on using the PROJ software for computing the mapping.
 
 +
 The **`perspective_point_height`** is the distance to the surface of the ellipsoid.