-
Notifications
You must be signed in to change notification settings - Fork 38
/
why-cog.html
69 lines (58 loc) · 5.06 KB
/
why-cog.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
<!DOCTYPE HTML>
<!--
Stellar by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
-->
<html>
<head>
<title>Cloud Optimized GeoTIFF in depth</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<!--[if lte IE 8]><script src="assets/js/ie/html5shiv.js"></script><![endif]-->
<link rel="stylesheet" href="assets/css/main.css" />
<!--[if lte IE 9]><link rel="stylesheet" href="assets/css/ie9.css" /><![endif]-->
<!--[if lte IE 8]><link rel="stylesheet" href="assets/css/ie8.css" /><![endif]-->
</head>
<body>
<!-- Wrapper -->
<div id="wrapper">
<!-- Header -->
<header id="header">
<h1>Why Cloud Optimized GeoTIFF's?</h1>
<p>The advantages of using COG's</p>
</header>
<!-- Main -->
<div id="main">
<!-- Content -->
<section id="content" class="main">
<h2>Overview</h2>
<p>More and more geospatial data is migrating to the cloud, and it most often is stored on cloud-based object storage like <a href="https://aws.amazon.com/s3/">S3</a> or <a href="https://cloud.google.com/storage/">Google Cloud Storage</a>. Traditional GIS file formats can easily sit on the cloud, but serving up web map tiles or doing on the fly processing of the data are difficult to do efficiently with those formats. They often have to be fully downloaded to another location and then translated to an optimized format or stored in memory.</p>
<p>Cloud Optimized GeoTIFF’s enable efficient streaming of data, with some <a href="in-depth.html">smart technology</a>, to enable fully cloud-based geospatial workflows. Online imagery platforms like the <a href="https://www.planet.com/explorer/">Planet Platform</a> and <a href="https://platform.digitalglobe.com/gbdx/">GBDX</a> use them to provide imagery that gets processed on the fly. COG-aware software can stream just the portions of data that it needs, improving access times.</p>
<p>Newer scale out geospatial software like <a href="http://geotrellis.io">GeoTrellis</a>, <a href="http://earthengine.google.com">Google Earth Engine</a> and <a href="https://gbdxdocs.digitalglobe.com/docs/idaho-course">IDAHO</a> also have potential to leverage COG’s directly in their architectures. Each processing node can stream the part of the COG that it needs to do on-the-fly geospatial processing.</p>
<p>As a part of the <a href="https://docs.ogc.org/is/21-026/21-026.html">OGC standard</a>, adoption of Cloud Optimized GeoTIFFs will increase over time as more and more software and tools adopt native support for the standard. In cases where native support for COGs is missing all kinds of legacy software are still able to read them with no additional modifications because COGs leverage the base GeoTIFF standard. They won’t tap into streaming capabilities, but can easily download the whole dataset and read it, unlike various new imagery formats.</p>
<p>Providing data in the Cloud Optimized GeoTIFF format can help decrease how much data is copied. Since online software systems can stream the data they don’t need to keep their own copy of the data for efficient access, a common pattern today. And data providers do not need to provide multiple file formats, because legacy systems can read the same GeoTIFF that the online streaming software is. Data providers can just put up one version of their data, and multiple online software can all access it at the same time, with no additional copies for download purposes.</p>
</section>
</div>
<!-- Footer -->
<footer id="footer">
<section>
<h2>Pull Requests Accepted</h2>
<p>The Cloud Optimized GeoTIFF project and website is fully community driven. If something is not right on the website, or if you want to contribute a tutorial, add your software to the implementation list or tell the world about the awesome data you are making available as COG's then please contribute on GitHub.</p>
<ul class="actions">
<li><a href="https://github.com/cholmes/www.cogeo.org" class="button">Contribute</a></li>
</ul>
</section>
<p class="copyright"><a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>. Design: <a href="https://html5up.net" target="_blank">HTML5 UP</a>.</p>
</footer>
</div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/jquery.scrollex.min.js"></script>
<script src="assets/js/jquery.scrolly.min.js"></script>
<script src="assets/js/skel.min.js"></script>
<script src="assets/js/util.js"></script>
<!--[if lte IE 8]><script src="assets/js/ie/respond.min.js"></script><![endif]-->
<script src="assets/js/main.js"></script>
</body>
</html>