Update some links to https

content/_index.md

@@ -73,13 +73,13 @@ However a [command-line tool](command-line.html) and a [JavaFX application](java
 are also provided for allowing users to experiment some SIS functionalities before writing code.
 
 
-[geoapi]:    http://www.geoapi.org/
+[geoapi]:    https://www.geoapi.org/
 [GML]:       https://www.ogc.org/standards/gml
 [SF_SQL]:    https://www.ogc.org/standards/sfs
 [filter]:    https://www.ogc.org/standards/filter
 [geoTIFF]:   https://www.ogc.org/standards/geotiff
 [netCDF]:    https://www.ogc.org/standards/netcdf
-[netCDF_MF]: http://docs.opengeospatial.org/bp/16-114r3/16-114r3.html
-[MF_CSV]:    http://docs.opengeospatial.org/is/14-084r2/14-084r2.html
+[netCDF_MF]: https://docs.opengeospatial.org/bp/16-114r3/16-114r3.html
+[MF_CSV]:    https://docs.opengeospatial.org/is/14-084r2/14-084r2.html
 [JSR_363]:   https://jcp.org/en/jsr/detail?id=363
 [seshat]:    https://unitsofmeasurement.github.io/seshat/

content/coding-conventions.md

@@ -195,7 +195,7 @@ Internet Explorer users need to [install a plugin][mathml-plugin-ie].
 Firefox users can optionally install the [fonts for Mozilla's MathML engine][mathml-fonts] for better results.
 Note that a [JavaScript display engine][mathml-mathjax] is available for all browsers, but not yet used by SIS.
 
-[srcheaders]:       http://www.apache.org/legal/src-headers.html
+[srcheaders]:       https://www.apache.org/legal/src-headers.html
 [JLS-order]:        https://docs.oracle.com/javase/specs/jls/se8/html/jls-8.html#jls-8.1.1
 [mathml-W3C]:       https://www.w3.org/Math/
 [mathml-wolfram]:   https://reference.wolfram.com/language/XML/tutorial/MathML.html

content/developer-guide/annexes/geoapi/ConceptualModels.html

@@ -38,7 +38,7 @@ <h3 id="ConceptualModels">Sources of conceptual models used by Apache SIS</h3>
       <p>
         Most standards used by Apache <abbr>SIS</abbr> have been devised by the <a href="https://www.ogc.org/">Open Geospatial Consortium</a> (<abbr>OGC</abbr>),
         sometimes in collaboration with the <a href="https://www.iso.org/">International Organization for Standardization</a> (<abbr>ISO</abbr>).
-        Some <abbr>ISO</abbr> standards themselves become European standards via the <a href="http://inspire.jrc.ec.europa.eu">INSPIRE Directive</a>.
+        Some <abbr>ISO</abbr> standards themselves become European standards via the <a href="https://inspire.jrc.ec.europa.eu">INSPIRE Directive</a>.
         These standards offer two key features:
       </p>
       <ul>
@@ -53,7 +53,7 @@ <h3 id="ConceptualModels">Sources of conceptual models used by Apache SIS</h3>
       <p>
         These standards are made available to the international community for free,
         as <a href="https://www.ogc.org/standards/is">specifications (<abbr title="Portable Document Format">PDF</abbr> files)</a> or
-        as <a href="http://schemas.opengis.net/gml/3.3/">schemas (<abbr title="XML Schema Definition">XSD</abbr> files)</a>.
+        as <a href="https://schemas.opengis.net/gml/3.3/">schemas (<abbr title="XML Schema Definition">XSD</abbr> files)</a>.
         Standardization organizations do not create software; to obtain an implementation of these specifications,
         users must choose one of the compliant products available on the market, or develop their own solutions.
         Such voluntary compliance with these specifications allow independent communities to more easily exchange geographic information.
@@ -144,8 +144,8 @@ <h3 id="OGC-RFC">Procedure for the submission of proposals for modification</h3>
         Coordinates Reference System (<abbr>CRS</abbr>) among <a href="../../tables/CoordinateReferenceSystems.html">several thousand</a>.
         This database is offered by petroleum companies that have an interest in ensuring their explorations are conducted in the correct place,
         even when using map produced by another party.
-        Other examples of <i>de facto</i> standards include <a href="http://geotiff.osgeo.org">GeoTIFF</a> for data distributed on a grid (such as images),
-        and <a href="http://en.wikipedia.org/wiki/Shapefile">Shapefile</a> for vector data (such as geometric shapes).
+        Other examples of <i>de facto</i> standards include <a href="https://geotiff.osgeo.org">GeoTIFF</a> for data distributed on a grid (such as images),
+        and <a href="https://en.wikipedia.org/wiki/Shapefile">Shapefile</a> for vector data (such as geometric shapes).
       </p><p>
         <abbr>OGC</abbr> standards are specified in several dozen documents.
         Each document outlines a service — for example, the transformation of coordinates.

content/developer-guide/annexes/geoapi/DefinitionProcess.html

@@ -40,9 +40,9 @@ <h3 id="SpecificationToInterfaces">From <abbr>OGC</abbr> specifications to Java
         GeoAPI interfaces are sometimes generated from other files provided by <abbr>OGC</abbr>, like <abbr>XSD</abbr> files.
         But there is always a manual revision, and often modifications compared to automatically generated Java files.
         It would have been possible to automatically generate Java interfaces from <abbr>OGC</abbr> standards using existing tools.
-        For example one of the most commonly-used approaches is to transform <a href="http://schemas.opengis.net/gml/3.3/"><abbr>XSD</abbr> schemas</a>
+        For example one of the most commonly-used approaches is to transform <a href="https://schemas.opengis.net/gml/3.3/"><abbr>XSD</abbr> schemas</a>
         into Java interfaces using command line utility <code>xjc</code>.
-        As this utility is included in most Java distributions (it is one of the <a href="http://jaxb.java.net"><abbr>JAXB</abbr></a> tools),
+        As this utility is included in most Java distributions (it is one of the <a href="https://jaxb.java.net"><abbr>JAXB</abbr></a> tools),
         this approach is favoured by many projects found on the Internet.
         Other approaches use tools integrated into the Eclipse Development Environment,
         which is based on <abbr>UML</abbr> schemas rather than <abbr>XSD</abbr> ones.
@@ -141,7 +141,7 @@ <h3 id="SpecificationToInterfaces">From <abbr>OGC</abbr> specifications to Java
       </ul>
       <p>
         Deviations from the standards are documented in each affected class and method.
-        Each mention of a deviation is also collected on a <a href="http://www.geoapi.org/3.0/javadoc/departures.html">single page</a> in order to provide an overview.
+        Each mention of a deviation is also collected on a <a href="https://www.geoapi.org/3.0/javadoc/departures.html">single page</a> in order to provide an overview.
         Since these deviations blur the relationships between the standards and certain Java interfaces,
         the correspondence between these languages is explained by <code>@UML</code> annotations and property files described in the following section.
       </p>

content/developer-guide/annexes/geoapi/GeoAPI.html

@@ -36,7 +36,7 @@
         <h3 id="GeoAPI">From conceptual models to Java interfaces: GeoAPI</h3>
       </header>
       <p>
-        The <a href="http://www.geoapi.org">GeoAPI</a> project offers a set of Java interfaces for geospatial applications.
+        The <a href="https://www.geoapi.org">GeoAPI</a> project offers a set of Java interfaces for geospatial applications.
         In a series of <code>org.opengis.*</code> packages, GeoAPI defines structures representing metadata,
         coordinate reference systems and operations that perform cartographic projections.
         In a part that is not yet standardized — called <i>pending</i> — GeoAPI defines structures that represent geo-referenced images,
@@ -51,9 +51,9 @@ <h3 id="GeoAPI">From conceptual models to Java interfaces: GeoAPI</h3>
           (due to the many publications related to <abbr>OGC</abbr> standards), as well as increased interoperability.
           Interoperability is facilitated by a better separation between applications that <em>call</em> GeoAPI functions,
           and libraries that <em>implement</em> GeoAPI.
-          The separation is similar to that offered by the <a href="http://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/"><abbr>JDBC</abbr></a> (<i>Java Database Connectivity</i>) interfaces of standard Java.
+          The separation is similar to that offered by the <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/jdbc/"><abbr>JDBC</abbr></a> (<i>Java Database Connectivity</i>) interfaces of standard Java.
           Using the interfaces’ <abbr>API</abbr>, developers can ignore the underlying implementation.
-          For example, they can perform cartographic projections with the help of the <a href="http://www.geoapi.org/geoapi-proj4/index.html">Proj.4</a> library, or the Apache <abbr>SIS</abbr> library,
+          For example, they can perform cartographic projections with the help of the <a href="https://www.geoapi.org/geoapi-proj4/index.html">Proj.4</a> library, or the Apache <abbr>SIS</abbr> library,
           without having to change their programs when they change libraries.
         </p></li>
         <li><p>
@@ -81,33 +81,33 @@ <h2>GeoAPI project history</h2>
             At this time, the wave of web services had not yet eclipsed classical programming interfaces.
             The interfaces of the <abbr>OGC</abbr> did anticipate a networked world,
             but invested rather — in the case of Java — in <abbr>RMI</abbr> (<i>Remote Method Invocation</i>) technology.
-            As the GeoAPI project did not yet exist, we retroactively designate these historical interfaces “<a href="http://www.geoapi.org/0.1/index.html">GeoAPI 0.1</a>”.
+            As the GeoAPI project did not yet exist, we retroactively designate these historical interfaces “<a href="https://www.geoapi.org/0.1/index.html">GeoAPI 0.1</a>”.
             These interfaces already used the package name <code>org.opengis</code>, which would be adopted by GeoAPI.
           </p><p>
             In 2002, developers of free projects launched a
-            <a href="http://web.archive.org/web/20030509104308/http://digitalearth.org/story/2002/10/10/55046/206">call for the creation of a geospatial <abbr>API</abbr></a>.
+            <a href="https://web.archive.org/web/20030509104308/http://digitalearth.org/story/2002/10/10/55046/206">call for the creation of a geospatial <abbr>API</abbr></a>.
             The initial proposal attracted the interest of at least five free projects.
-            The project was created using <a href="http://sourceforge.net/projects/geoapi/">SourceForge</a>,
-            which has since hosted the source code in a <a href="http://www.geoapi.org/source-repository.html">Subversion repository</a>.
+            The project was created using <a href="https://sourceforge.net/projects/geoapi/">SourceForge</a>,
+            which has since hosted the source code in a <a href="https://www.geoapi.org/source-repository.html">Subversion repository</a>.
             It was then that the project assumed the name “GeoAPI”, and used the interfaces of the <abbr>OGC</abbr> specification 01-009 as a starting point.
           </p><p>
             A few months later, the <abbr>OGC</abbr> launched the <a href="https://www.ogc.org/standards/go"><abbr>GO</abbr>-1: <i>Geographic Objects</i></a> project,
             which pursued goals similar to those of GeoAPI.
             In the meantime, the <abbr>OGC</abbr> abandonned some of their specifications in favor of <abbr>ISO</abbr> standards.
             GeoAPI and <abbr>GO-1</abbr> worked jointly to rework the GeoAPI interfaces and base them on the new <abbr>ISO</abbr> norms.
-            Their first interation, <a href="http://www.geoapi.org/1.0/index.html">GeoAPI 1.0</a>,
+            Their first interation, <a href="https://www.geoapi.org/1.0/index.html">GeoAPI 1.0</a>,
             served as a starting point for the first draft of the <abbr>OGC</abbr> specification 03-064 by the <abbr>GO</abbr>-1 working group.
             The final version of this specification became an <abbr>OGC</abbr> standard in 2005,
-            and <a href="http://www.geoapi.org/2.0/index.html">GeoAPI 2.0</a> was published at that time.
+            and <a href="https://www.geoapi.org/2.0/index.html">GeoAPI 2.0</a> was published at that time.
           </p><p>
             The <abbr>GO</abbr>-1 project was largely supported by a company called <i>Polexis</i>.
             Its acquisition by <i>Sys Technology</i>, and the change in priorities under the new owners,
             brought a halt to the <abbr>GO</abbr>-1 project, which in turn slowed development on GeoAPI.
             In order to resume development, a new working group entitled “GeoAPI 3.0” was created at the <abbr>OGC</abbr>.
             This group took a narrower focus compared to GeoAPI 2.0, concentrating on the most stable interfaces, and putting the others
-            — such as geometries — in a module entitled “<a href="http://www.geoapi.org/geoapi-pending/index.html">pending</a>”, for future consideration.
-            <a href="http://www.geoapi.org/3.0/index.html">GeoAPI 3.0</a> became an <a href="https://www.ogc.org/standards/geoapi"><abbr>OGC</abbr> standard</a> in 2011.
-            This version was the first to be deployed in the <a href="http://search.maven.org/#search|ga|1|geoapi">Maven central repository</a>.
+            — such as geometries — in a module entitled “<a href="https://www.geoapi.org/geoapi-pending/index.html">pending</a>”, for future consideration.
+            <a href="https://www.geoapi.org/3.0/index.html">GeoAPI 3.0</a> became an <a href="https://www.ogc.org/standards/geoapi"><abbr>OGC</abbr> standard</a> in 2011.
+            This version was the first to be deployed in the <a href="https://search.maven.org/#search|ga|1|geoapi">Maven central repository</a>.
           </p>
         </article>
       </details>

content/developer-guide/annexes/geoapi/ReduceDependency.html

@@ -184,7 +184,7 @@ <h5 id="GeoAPI-simple">Defining custom implementations</h5>
       <p id="GeoAPI-examples">
         The <code>geoapi-examples</code> module provides examples of simple implementations.
         Many of these classes implement more than one interface at a time in order to provide a simpler conceptual model.
-        The <a href="http://www.geoapi.org/geoapi-examples/apidocs/overview-summary.html">javadoc for this module</a>
+        The <a href="https://www.geoapi.org/geoapi-examples/apidocs/overview-summary.html">javadoc for this module</a>
         lists key packages and classes along with the combinations performed.
         This module illustrates not only how GeoAPI might be implemented,
         but also how the implementation might be tested using <code>geoapi-conformance</code>.

content/developer-guide/coverage/SampleDimension.html

@@ -40,7 +40,7 @@ <h2 id="SampleDimension">Sample dimensions</h2>
         In Apache <abbr>SIS</abbr>, the distinction between ranges of numerical values and range of any types of values is represented by
         <code>Number­Range</code> and <code>Range</code> classes respectively.
         The <code>Number­Range</code> is used more often, and is also the one that most closely approaches the
-        <a href="http://en.wikipedia.org/wiki/Interval_%28mathematics%29">the common mathematical concept of an interval</a>.
+        <a href="https://en.wikipedia.org/wiki/Interval_%28mathematics%29">the common mathematical concept of an interval</a>.
         This textual representation approaches the specifications of <abbr>ISO</abbr> 31-11 standard,
         except that the comma is replaced by the character “…” as the separator of minimal and maximal values.
         For example, “[0 … 256)” represents the range of values from 0 inclusive to 256 exclusive.

content/developer-guide/introduction/index.html

@@ -44,13 +44,13 @@ <h1 id="Introduction">Introduction</h1>
         the Open Geospatial Consortium (<abbr>OGC</abbr>) and the International Organization for Standardization (<abbr>ISO</abbr>).
         The <a href="#Annexes">annex</a> provides more context about international standards.
       </p><p>
-        The library is an implementation of <abbr title="Open Geospatial Consortium">OGC</abbr> <a href="http://www.geoapi.org">GeoAPI</a> interfaces.
+        The library is an implementation of <abbr title="Open Geospatial Consortium">OGC</abbr> <a href="https://www.geoapi.org">GeoAPI</a> interfaces.
         In a series of <code>org.opengis.*</code> packages, GeoAPI offers a set of implementation-neutral Java interfaces for geospatial applications.
         These interfaces closely follow the specifications of the <abbr>OGC</abbr>, while interpreting and adapting them
         to meet the needs of Java developers — for example, conforming with Java naming conventions.
         The conceptual model of GeoAPI will be explained in detail in the chapters describing Apache <abbr>SIS</abbr> implementation.
         However, we can get an overview of its content by consulting the page listing the mapping between
-        <a href="http://www.geoapi.org/3.0/javadoc/content.html">GeoAPI methods and the standards where they come from</a>.
+        <a href="https://www.geoapi.org/3.0/javadoc/content.html">GeoAPI methods and the standards where they come from</a>.
         The <a href="#GeoAPI">annex</a> provides more details about GeoAPI history and how to use it.
       </p><p>
         While Apache <abbr>SIS</abbr> is primarily a library for helping developers to create their own applications,

content/downloads.md

@@ -126,12 +126,12 @@ For better flexibility and performance, it is also possible to use an uncompress
 and writable Derby database, or to install the EPSG dataset on HSQL or PostgreSQL.
 See [How to use EPSG geodetic dataset](epsg.html) page for more information.
 
-[maven]:    http://maven.apache.org/
+[maven]:    https://maven.apache.org/
 [keys]:     https://www.apache.org/dist/sis/KEYS
-[license]:  http://www.apache.org/licenses/LICENSE-2.0
-[src]:      http://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-src.zip
-[doc]:      http://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-doc.zip
-[bin]:      http://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-bin.zip
+[license]:  https://www.apache.org/licenses/LICENSE-2.0
+[src]:      https://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-src.zip
+[doc]:      https://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-doc.zip
+[bin]:      https://www.apache.org/dyn/closer.cgi/sis/{{% version %}}/apache-sis-{{% version %}}-bin.zip
 [src-PGP]:  https://www.apache.org/dist/sis/{{% version %}}/apache-sis-{{% version %}}-src.zip.asc
 [doc-PGP]:  https://www.apache.org/dist/sis/{{% version %}}/apache-sis-{{% version %}}-doc.zip.asc
 [bin-PGP]:  https://www.apache.org/dist/sis/{{% version %}}/apache-sis-{{% version %}}-bin.zip.asc

content/epsg.md

@@ -257,4 +257,4 @@ fetching the data source from the `context.xml` file.
 [IOGP]:     https://www.iogp.org/
 [EPSG]:     https://epsg.org/
 [EPSG-ToU]: https://epsg.org/terms-of-use.html
-[Derby]:    http://db.apache.org/derby/derby_downloads.html
+[Derby]:    https://db.apache.org/derby/derby_downloads.html