docs: Use HTTPS links to external sites

Avoids a redirect.

Author: l0b0

docs/conf.py

@@ -4,7 +4,7 @@
 #
 # This file does only contain a selection of the most common options. For a
 # full list see the documentation:
-# http://www.sphinx-doc.org/en/master/config
+# https://www.sphinx-doc.org/en/master/usage/configuration.html
 
 # -- Path setup --------------------------------------------------------------
 

docs/contributing.rst

@@ -57,7 +57,7 @@ PySTAC uses
 - `black <https://github.com/psf/black>`_ for Python code formatting
 - `codespell <https://github.com/codespell-project/codespell/>`_ to check code for common misspellings
 - `doc8 <https://github.com/pycqa/doc8>`__ for style checking on RST files in the docs
-- `flake8 <http://flake8.pycqa.org/en/latest/>`_ for Python style checks
+- `flake8 <https://flake8.pycqa.org/en/latest/>`_ for Python style checks
 - `mypy <http://www.mypy-lang.org/>`_ for Python type annotation checks
 
 Run all of these with ``pre-commit run --all-files`` or a single one using

docs/make.bat

@@ -21,7 +21,7 @@ if errorlevel 9009 (
 	echo.may add the Sphinx directory to PATH.
 	echo.
 	echo.If you don't have Sphinx installed, grab it from
-	echo.http://sphinx-doc.org/
+	echo.https://www.sphinx-doc.org/
 	exit /b 1
 )
 

docs/tutorials/creating-a-landsat-stac.ipynb

@@ -988,7 +988,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "This would be a good time to check our work - we can print out the GeoJSON and use [geojson.io](http://geojson.io/) to check and make sure we're using scenes that overlap our location. If this footprint is somewhere unexpected in the world, make sure the Lat/Long coordinates are correct and in the right order!"
+    "This would be a good time to check our work - we can print out the GeoJSON and use [geojson.io](https://geojson.io/) to check and make sure we're using scenes that overlap our location. If this footprint is somewhere unexpected in the world, make sure the Lat/Long coordinates are correct and in the right order!"
    ]
   },
   {

docs/tutorials/how-to-create-stac-catalogs.ipynb

@@ -126,7 +126,7 @@
     }
    ],
    "source": [
-    "url = ('http://spacenet-dataset.s3.amazonaws.com/'\n",
+    "url = ('https://spacenet-dataset.s3.amazonaws.com/'\n",
     "       'spacenet/SN5_roads/train/AOI_7_Moscow/MS/'\n",
     "       'SN5_roads_train_AOI_7_Moscow_MS_chip996.tif')\n",
     "urllib.request.urlretrieve(url, img_path)"
@@ -1435,7 +1435,7 @@
     }
    ],
    "source": [
-    "url2 = ('http://spacenet-dataset.s3.amazonaws.com/'\n",
+    "url2 = ('https://spacenet-dataset.s3.amazonaws.com/'\n",
     "       'spacenet/SN5_roads/train/AOI_7_Moscow/MS/'\n",
     "       'SN5_roads_train_AOI_7_Moscow_MS_chip997.tif')\n",
     "img_path2 = os.path.join(tmp_dir.name, 'image.tif')\n",

pystac/catalog.py

@@ -110,8 +110,8 @@ class Catalog(STACObject):
     Args:
         id : Identifier for the catalog. Must be unique within the STAC.
         description : Detailed multi-line description to fully explain the catalog.
-            `CommonMark 0.28 syntax <http://commonmark.org/>`_ MAY be used for rich text
-            representation.
+            `CommonMark 0.28 syntax <https://commonmark.org/>`_ MAY be used for rich
+            text representation.
         title : Optional short descriptive one-line title for the catalog.
         stac_extensions : Optional list of extensions the Catalog implements.
         href : Optional HREF for this catalog, which be set as the

pystac/collection.py

@@ -521,7 +521,7 @@ class Collection(Catalog):
     Args:
         id : Identifier for the collection. Must be unique within the STAC.
         description : Detailed multi-line description to fully explain the
-            collection. `CommonMark 0.28 syntax <http://commonmark.org/>`_ MAY
+            collection. `CommonMark 0.28 syntax <https://commonmark.org/>`_ MAY
             be used for rich text representation.
         extent : Spatial and temporal extents that describe the bounds of
             all items contained within this Collection.

pystac/extensions/projection.py

@@ -97,7 +97,7 @@ def epsg(self) -> Optional[int]:
 
         A Coordinate Reference System (CRS) is the data reference system (sometimes
         called a 'projection') used by the asset data, and can usually be referenced
-        using an `EPSG code <http://epsg.io/>`_.
+        using an `EPSG code <https://epsg.io/>`_.
         If the asset data does not have a CRS, such as in the case of non-rectified
         imagery with Ground Control Points, ``epsg`` should be set to ``None``.
         It should also be set to ``None`` if a CRS exists, but for which there is no
@@ -115,7 +115,7 @@ def wkt2(self) -> Optional[str]:
         that the ``proj:geometry`` and ``proj:bbox`` fields represent
 
         This value is a
-        `WKT2 string <http://docs.opengeospatial.org/is/12-063r5/12-063r5.html>`_.
+        `WKT2 string <https://docs.opengeospatial.org/is/12-063r5/12-063r5.html>`_.
         If the data does not have a CRS, such as in the case of non-rectified imagery
         with Ground Control Points, ``wkt2`` should be set to ``None``. It should also
         be set to ``None`` if a CRS exists, but for which a WKT2 string does not exist.

tests/data-files/examples/1.0.0/README.md

@@ -6,10 +6,10 @@ should successfully load in various tools. They do not follow *all* the [best pr
 due to the fact that they contrive examples to show the spec and we are hosting in GitHub. But we note below where they differ from an ideal catalog.
 
 The various fields are mostly fictional, to be able to demonstrate the various aspects of the spec as tersely as possible. To get a sense
-of real world STAC implementations we recommend exploring the [stac-examples](http://github.com/stac-utils/stac-examples) repo, which 
+of real world STAC implementations we recommend exploring the [stac-examples](https://github.com/stac-utils/stac-examples) repo, which 
 gathers in one place copies of STAC [Items](../item-spec/item-spec.md) and [Collection](../collection-spec/collection-spec.md) 
 from a number of different production catalogs that all follow good STAC practices. And you should also explore the various catalogs
-listed on [STAC Index](http://stacindex.org), to see full catalogs in production.
+listed on [STAC Index](https://stacindex.org/), to see full catalogs in production.
 
 ## Organization