Merge pull request #310 from RichardScottOZ/patch-1

Update how-to-create-stac-catalogs.ipynb

Author: lossyrob

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

@@ -1080,7 +1080,7 @@
    "source": [
     "#### Add Ground Sample Distance to common metadata\n",
     "\n",
-    "We'll add the Ground Sample Distance that is defined as part of the Item [Common Metadata](https://github.com/radiantearth/stac-spec/blob/v1.0.0-beta.2/item-spec/common-metadata.md). We define this on the Item leve as 30 meters, which is the GSD for most of the bands of Landsat 8. However, there are some bands that have a different resolution; we will account for this by setting the GSD explicitly for each of those bands below."
+    "We'll add the Ground Sample Distance that is defined as part of the Item [Common Metadata](https://github.com/radiantearth/stac-spec/blob/v1.0.0-beta.2/item-spec/common-metadata.md). We define this on the Item level as 30 meters, which is the GSD for most of the bands of Landsat 8. However, there are some bands that have a different resolution; we will account for this by setting the GSD explicitly for each of those bands below."
    ]
   },
   {
@@ -1361,7 +1361,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Here we see the tumbnail asset, which does not include the band information for the `eo` extension as it does not represent any of the Item's bands:"
+    "Here we see the thumbnail asset, which does not include the band information for the `eo` extension as it does not represent any of the Item's bands:"
    ]
   },
   {
@@ -1888,7 +1888,7 @@
    "source": [
     "### Write the catalog locally\n",
     "\n",
-    "Now that we have our complete, validated STAC in memory, let's write it out. This is a simple as calling `save` on the Collection. We need to specify the type of catalog in order to property write out links - these types are described again in the STAC [Best Practices](https://github.com/radiantearth/stac-spec/blob/master/best-practices.md#use-of-links) documentation.\n",
+    "Now that we have our complete, validated STAC in memory, let's write it out. This is as simple as calling `save` on the Collection. We need to specify the type of catalog in order to property write out links - these types are described again in the STAC [Best Practices](https://github.com/radiantearth/stac-spec/blob/master/best-practices.md#use-of-links) documentation.\n",
     "\n",
     "We'll use the \"self contained\" type, which uses relative paths and does not specify absolute \"self\" links to any object. This makes the catalog more portable, as it remains valid even if you copy the STAC to new locations."
    ]
@@ -2242,7 +2242,7 @@
    "source": [
     "### Acknowledgements\n",
     "\n",
-    "Credit to [sat-stac-landsat](https://github.com/sat-utils/sat-stac-landsat) off of which a lot of this code was based."
+    "Credit to [sat-stac-landsat](https://github.com/sat-utils/sat-stac-landsat) from which a lot of this code was based."
    ]
   }
  ],

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

@@ -295,7 +295,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Using [rasterio](https://rasterio.readthedocs.io/en/stable/), we can pull out the bounding box of the image to use for the image metadata. If the image contained a NoData border, we would ideally pull out the footprint and save it as the geometry; in this case, we're working with a small chip the most likely has no NoData values."
+    "Using [rasterio](https://rasterio.readthedocs.io/en/stable/), we can pull out the bounding box of the image to use for the image metadata. If the image contained a NoData border, we would ideally pull out the footprint and save it as the geometry; in this case, we're working with a small chip that most likely has no NoData values."
    ]
   },
   {

pystac/catalog.py

@@ -36,7 +36,7 @@ def __str__(self) -> str:
 
     SELF_CONTAINED = "SELF_CONTAINED"
     """A 'self-contained catalog' is one that is designed for portability.
-    Users may want to download a catalog from online and be able to use it on their
+    Users may want to download an online catalog from and be able to use it on their
     local computer, so all links need to be relative.
 
     See:
@@ -378,7 +378,7 @@ def get_items(self) -> Iterable["Item_Type"]:
         """Return all items of this catalog.
 
         Return:
-            Iterable[Item]: Generator of items who's parent is this catalog.
+            Iterable[Item]: Generator of items whose parent is this catalog.
         """
         return map(lambda x: cast(pystac.Item, x), self.get_stac_objects("item"))
 

pystac/item.py

@@ -482,7 +482,7 @@ def get_created(self, asset: Optional[Asset] = None) -> Optional[Datetime]:
         Note:
             ``created`` and ``updated`` have different meaning depending on where they
             are used. If those fields are available in the Item `properties`, it's
-            referencing to the creation and update times of the metadata. Having those
+            referencing the creation and update times of the metadata. Having those
             fields in the Item `assets` refers to the creation and update times of the
             actual data linked to in the Asset Object.
 
@@ -525,11 +525,10 @@ def updated(self) -> Optional[Datetime]:
         Note:
             ``created`` and ``updated`` have different meaning depending on where they
             are used. If those fields are available in the Item `properties`, it's
-            referencing to the creation and update times of the metadata. Having those
+            referencing the creation and update times of the metadata. Having those
             fields in the Item `assets` refers to the creation and update times of the
             actual data linked to in the Asset Object.
 
-
         Returns:
             datetime: Date and time that the metadata file was most recently
                 updated
@@ -549,7 +548,7 @@ def get_updated(self, asset: Optional[Asset] = None) -> Optional[Datetime]:
         Note:
             ``created`` and ``updated`` have different meaning depending on where they
             are used. If those fields are available in the Item `properties`, it's
-            referencing to the creation and update times of the metadata. Having those
+            referencing the creation and update times of the metadata. Having those
             fields in the Item `assets` refers to the creation and update times of the
             actual data linked to in the Asset Object.