diff --git a/guides/linked/Earth_Engine_asset_from_cloud_geotiff.ipynb b/guides/linked/Earth_Engine_asset_from_cloud_geotiff.ipynb index 23e5b9a9a..79046e8bf 100644 --- a/guides/linked/Earth_Engine_asset_from_cloud_geotiff.ipynb +++ b/guides/linked/Earth_Engine_asset_from_cloud_geotiff.ipynb @@ -45,11 +45,11 @@ "id": "aV1xZ1CPi3Nw" }, "source": [ - "
\n", - "\n", - " Run in Google Colab\n", - "\n", - " View source on GitHub
" + "\u003ctable class=\"ee-notebook-buttons\" align=\"left\"\u003e\u003ctd\u003e\n", + "\u003ca target=\"_blank\" href=\"http://colab.research.google.com/github/google/earthengine-community/blob/master/guides/linked/Earth_Engine_asset_from_cloud_geotiff.ipynb\"\u003e\n", + " \u003cimg src=\"https://www.tensorflow.org/images/colab_logo_32px.png\" /\u003e Run in Google Colab\u003c/a\u003e\n", + "\u003c/td\u003e\u003ctd\u003e\n", + "\u003ca target=\"_blank\" href=\"https://github.com/google/earthengine-community/blob/master/guides/linked/Earth_Engine_asset_from_cloud_geotiff.ipynb\"\u003e\u003cimg width=32px src=\"https://www.tensorflow.org/images/GitHub-Mark-32px.png\" /\u003e View source on GitHub\u003c/a\u003e\u003c/td\u003e\u003c/table\u003e" ] }, { @@ -62,7 +62,7 @@ "\n", "***Note:*** *The REST API contains new and advanced features that may not be suitable for all users. If you are new to Earth Engine, please get started with the [JavaScript guide](https://developers.google.com/earth-engine/guides/getstarted).*\n", "\n", - "Earth Engine can load images from Cloud Optimized GeoTiffs (COGs) in Google Cloud Storage ([learn more](https://developers.google.com/earth-engine/guides/image_overview#images-from-cloud-geotiffs)). This notebook demonstrates how to create Earth Engine assets backed by COGs. An advantage of COG-backed assets is that the spatial and metadata fields of the image will be indexed at asset creation time, making the image more performant in collections. (In contrast, an image created through `ee.Image.loadGeoTIFF` and put into a collection will require a read of the GeoTiff for filtering operations on the collection.) A disadvantage of COG-backed assets is that they may be slower in some circumstances than standard assets when used in computations.\n", + "Earth Engine can load images from Cloud Optimized GeoTiffs (COGs) in Google Cloud Storage ([learn more](https://developers.google.com/earth-engine/guides/image_overview#images-from-cloud-geotiffs)). This notebook demonstrates how to create Earth Engine assets backed by COGs. An advantage of COG-backed assets is that the spatial and metadata fields of the image will be indexed at asset creation time, making the image more performant in collections. (In contrast, an image created through `ee.Image.loadGeoTIFF` and put into a collection will require a read of the GeoTiff for filtering operations on the collection.) The performance of COG-backed assets is comparable to that of ingested assets in typical use cases.\n", "\n", "To create a COG-backed asset, make a `POST` request to the Earth Engine [`ImportExternalImage` endpoint](https://developers.google.com/earth-engine/reference/rest/v1alpha/projects.assets/create). As shown in the following, this request must be authorized to create an asset in your user folder." ] @@ -270,4 +270,4 @@ ] } ] -} \ No newline at end of file +}