Skip to content
This repository has been archived by the owner on May 10, 2021. It is now read-only.

Commit

Permalink
Added more results
Browse files Browse the repository at this point in the history
  • Loading branch information
@ghobona
ghobona committed Feb 22, 2021
1 parent 11d96e7 commit 83d1f5b
Show file tree
Hide file tree
Showing 6 changed files with 56 additions and 25 deletions.
15 changes: 14 additions & 1 deletion report/7-results.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,25 @@ The code sprint included multiple software libraries, OWS implementations, OGC A
.A screenshot of OpenSphere displaying a DGGS
image::images/openshere-dggs.png[width=600,align="center"]

<<img_miramon>> shows a screenshot of the UAB-CREAF MiraMon application accessing resources through OGC API - Tiles and OGC API- Maps interfaces. The client application is shown retrieving content from Ecere and CubeWerx servers.

[#img_miramon,reftext='{figure-caption} {counter:figure-num}']
.A screenshot of the UAB-CREAF MiraMon application accessing resources through OGC API - Tiles and OGC API- Maps interfaces
image::images/miramon.png[width=600,align="center"]

<<img_geoserver_styles>> shows a screenshot of the collections offered by a GeoServer implementation of OGC API - Styles. The screenshot shows a series of styles belonging to one of the collections. This organization of styles makes it possible to have different styles for different contexts (e.g. light, day, outdoor and so forth).

[#img_geoserver_styles,reftext='{figure-caption} {counter:figure-num}']
.A screenshot of the collections offered by a GeoServer implementation of OGC API - Styles
image::images/geoserver-ogcapi-styles.png[width=600,align="center"]


<<img_hexagon_processes>> shows two screenshots, one above the other. The upper screenshot shows the Swagger user interface (UI) of a prototype implementation of OGC API - Processes by Hexagon Geospatial. The lower screenshot shows a series of in-progress and completed jobs as monitored by the implementation.

[#img_hexagon_processes,reftext='{figure-caption} {counter:figure-num}']
.A screenshot of the Swagger UI of a prototype Hexagon implementation of OGC API - Processes
image::images/hexagon.png[width=600,align="center"]

<<img_pygeoapi_dggs>> shows a screenshot of pygeoapi displaying part of the https://eng.uber.com/h3/[Uber H3] Hexagonal Hierarchical Geospatial Indexing System. H3 supports hierarchical tessellation of regular polygons at increasingly fine resolutions up to an areal size of square meters cite:[Bondaruk2019].

[#img_pygeoapi_dggs,reftext='{figure-caption} {counter:figure-num}']
Expand Down Expand Up @@ -63,7 +76,7 @@ image::images/mapml-geoserver-grid.png[width=600,align="center"]
.A screenshot of the landing page of an ldproxy instance accessed using a web browser (left) and postman (right)
image::images/ldproxy.png[width=600,align="center"]

<<img_cubewerx>> shows a screenshot of the CubeWerx Ship Detection processes running on Sentinel data in the Amazon Web Services Cloud. Available input datasets are listed on the left-hand side of the figure, whereas currently running and completed processes are listed on the right-hand side of the figure.
<<img_cubewerx>> shows a screenshot of the CubeWerx Ship Detection processes running on Sentinel data in the Amazon Web Services Cloud. Available input datasets are listed on the left-hand side of the figure, whereas in-progress and completed jobs are listed on the right-hand side of the figure.

[#img_cubewerx,reftext='{figure-caption} {counter:figure-num}']
.A screenshot of the CubeWerx processes management tool
Expand Down
66 changes: 42 additions & 24 deletions report/er.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2091,112 +2091,130 @@ <h2 id="Results"><a class="anchor" href="#Results"></a>8. Results</h2>
<div class="title">Figure 2. A screenshot of OpenSphere displaying a DGGS</div>
</div>
<div class="paragraph">
<p><a href="#img_geoserver_styles">Figure 3</a> shows a screenshot of the collections offered by a GeoServer implementation of OGC API - Styles. The screenshot shows a series of styles belonging to one of the collections. This organization of styles makes it possible to have different styles for different contexts (e.g. light, day, outdoor and so forth).</p>
<p><a href="#img_miramon">Figure 3</a> shows a screenshot of the UAB-CREAF MiraMon application accessing resources through OGC API - Tiles and OGC API- Maps interfaces. The client application is shown retrieving content from Ecere and CubeWerx servers.</p>
</div>
<div id="img_miramon" class="imageblock text-center">
<div class="content">
<img src="images/miramon.png" alt="miramon" width="600">
</div>
<div class="title">Figure 3. A screenshot of the UAB-CREAF MiraMon application accessing resources through OGC API - Tiles and OGC API- Maps interfaces</div>
</div>
<div class="paragraph">
<p><a href="#img_geoserver_styles">Figure 4</a> shows a screenshot of the collections offered by a GeoServer implementation of OGC API - Styles. The screenshot shows a series of styles belonging to one of the collections. This organization of styles makes it possible to have different styles for different contexts (e.g. light, day, outdoor and so forth).</p>
</div>
<div id="img_geoserver_styles" class="imageblock text-center">
<div class="content">
<img src="images/geoserver-ogcapi-styles.png" alt="geoserver ogcapi styles" width="600">
</div>
<div class="title">Figure 3. A screenshot of the collections offered by a GeoServer implementation of OGC API - Styles</div>
<div class="title">Figure 4. A screenshot of the collections offered by a GeoServer implementation of OGC API - Styles</div>
</div>
<div class="paragraph">
<p><a href="#img_hexagon_processes">Figure 5</a> shows two screenshots, one above the other. The upper screenshot shows the Swagger user interface (UI) of a prototype implementation of OGC API - Processes by Hexagon Geospatial. The lower screenshot shows a series of in-progress and completed jobs as monitored by the implementation.</p>
</div>
<div id="img_hexagon_processes" class="imageblock text-center">
<div class="content">
<img src="images/hexagon.png" alt="hexagon" width="600">
</div>
<div class="title">Figure 5. A screenshot of the Swagger UI of a prototype Hexagon implementation of OGC API - Processes</div>
</div>
<div class="paragraph">
<p><a href="#img_pygeoapi_dggs">Figure 4</a> shows a screenshot of pygeoapi displaying part of the <a href="https://eng.uber.com/h3/">Uber H3</a> Hexagonal Hierarchical Geospatial Indexing System. H3 supports hierarchical tessellation of regular polygons at increasingly fine resolutions up to an areal size of square meters [<a href="#Bondaruk2019">3</a>].</p>
<p><a href="#img_pygeoapi_dggs">Figure 6</a> shows a screenshot of pygeoapi displaying part of the <a href="https://eng.uber.com/h3/">Uber H3</a> Hexagonal Hierarchical Geospatial Indexing System. H3 supports hierarchical tessellation of regular polygons at increasingly fine resolutions up to an areal size of square meters [<a href="#Bondaruk2019">3</a>].</p>
</div>
<div id="img_pygeoapi_dggs" class="imageblock text-center">
<div class="content">
<img src="images/pygeoapi-dggs.png" alt="pygeoapi dggs" width="600">
</div>
<div class="title">Figure 4. A screenshot of pygeoapi displaying a DGGS</div>
<div class="title">Figure 6. A screenshot of pygeoapi displaying a DGGS</div>
</div>
<div class="paragraph">
<p><a href="#img_geoserver_maps">Figure 5</a> shows a screenshot of a map created from <a href="https://www.ordnancesurvey.co.uk/business-government/products/open-zoomstack">OS Open Zoomstack</a> using a GeoServer instance that supports OGC API - Maps. OS Open Zoomstack offers comprehensive basemap of Great Britain showing coverage from national level right down to street detail.</p>
<p><a href="#img_geoserver_maps">Figure 7</a> shows a screenshot of a map created from <a href="https://www.ordnancesurvey.co.uk/business-government/products/open-zoomstack">OS Open Zoomstack</a> using a GeoServer instance that supports OGC API - Maps. OS Open Zoomstack offers comprehensive basemap of Great Britain showing coverage from national level right down to street detail.</p>
</div>
<div id="img_geoserver_maps" class="imageblock text-center">
<div class="content">
<img src="images/geoserver-ogcapi-maps.png" alt="geoserver ogcapi maps" width="600">
</div>
<div class="title">Figure 5. A screenshot of a map created from OS Open Zoomstack using a GeoServer and OGC API - Maps (Contains OS data © Crown Copyright and database right 2020)</div>
<div class="title">Figure 7. A screenshot of a map created from OS Open Zoomstack using a GeoServer and OGC API - Maps (Contains OS data © Crown Copyright and database right 2020)</div>
</div>
<div class="paragraph">
<p><a href="#img_geoapi">Figure 6</a> shows a screenshot of the NetBeans IDE running GeoAPI, Apache SIS and the UCAR netCDF library. The use of these three libraries demonstrated support for both the <a href="https://www.ogc.org/standards/geoapi">OGC GeoAPI</a> standard and the <a href="https://www.ogc.org/standards/netcdf">OGC netCDF</a> standard.</p>
<p><a href="#img_geoapi">Figure 8</a> shows a screenshot of the NetBeans IDE running GeoAPI, Apache SIS and the UCAR netCDF library. The use of these three libraries demonstrated support for both the <a href="https://www.ogc.org/standards/geoapi">OGC GeoAPI</a> standard and the <a href="https://www.ogc.org/standards/netcdf">OGC netCDF</a> standard.</p>
</div>
<div id="img_geoapi" class="imageblock text-center">
<div class="content">
<img src="images/geoapi.png" alt="geoapi" width="600">
</div>
<div class="title">Figure 6. A screenshot of the NetBeans IDE running GeoAPI, Apache SIS and the UCAR netCDF library</div>
<div class="title">Figure 8. A screenshot of the NetBeans IDE running GeoAPI, Apache SIS and the UCAR netCDF library</div>
</div>
<div class="paragraph">
<p><a href="#img_pygeoapi1">Figure 7</a> shows a screenshot of pygeoapi displaying a sample metadata record from the Dutch National GeoRegister.</p>
<p><a href="#img_pygeoapi1">Figure 9</a> shows a screenshot of pygeoapi displaying a sample metadata record from the Dutch National GeoRegister.</p>
</div>
<div id="img_pygeoapi1" class="imageblock text-center">
<div class="content">
<img src="images/pygeoapi1.png" alt="pygeoapi1" width="600">
</div>
<div class="title">Figure 7. A screenshot of pygeoapi displaying a sample metadata record</div>
<div class="title">Figure 9. A screenshot of pygeoapi displaying a sample metadata record</div>
</div>
<div class="paragraph">
<p><a href="#img_geonetwork">Figure 8</a> shows a screenshot of GeoNetwork and the download buttons (right-hand side of the screen) for different supported formats. As shown on the screenshot the formats included HTML, XML, JSON, RSS and JSON-LD structured according to the schema.org specification.</p>
<p><a href="#img_geonetwork">Figure 10</a> shows a screenshot of GeoNetwork and the download buttons (right-hand side of the screen) for different supported formats. As shown on the screenshot the formats included HTML, XML, JSON, RSS and JSON-LD structured according to the schema.org specification.</p>
</div>
<div id="img_geonetwork" class="imageblock text-center">
<div class="content">
<img src="images/geonetwork.png" alt="geonetwork" width="600">
</div>
<div class="title">Figure 8. A screenshot of the GeoNetwork user interface</div>
<div class="title">Figure 10. A screenshot of the GeoNetwork user interface</div>
</div>
<div class="paragraph">
<p><a href="#img_mapml">Figure 9</a> shows a screenshot of the MapML viewer built for GeoServer. The screenshot shows two separate layers in the same view, one showing part of the United States and the other showing Canada. The screenshot also shows a pop-up window triggered by a mouse click and revealing attributes about the clicked feature.</p>
<p><a href="#img_mapml">Figure 11</a> shows a screenshot of the MapML viewer built for GeoServer. The screenshot shows two separate layers in the same view, one showing part of the United States and the other showing Canada. The screenshot also shows a pop-up window triggered by a mouse click and revealing attributes about the clicked feature.</p>
</div>
<div id="img_mapml" class="imageblock text-center">
<div class="content">
<img src="images/mapml-geoserver.png" alt="mapml geoserver" width="600">
</div>
<div class="title">Figure 9. A screenshot of the MapML viewer in GeoServer</div>
<div class="title">Figure 11. A screenshot of the MapML viewer in GeoServer</div>
</div>
<div class="paragraph">
<p><a href="#img_mapml_grid">Figure 10</a> shows an additional screenshot of the MapML viewer, with a grid placed above the map layers.</p>
<p><a href="#img_mapml_grid">Figure 12</a> shows an additional screenshot of the MapML viewer, with a grid placed above the map layers.</p>
</div>
<div id="img_mapml_grid" class="imageblock text-center">
<div class="content">
<img src="images/mapml-geoserver-grid.png" alt="mapml geoserver grid" width="600">
</div>
<div class="title">Figure 10. A gridded screenshot of the MapML viewer built for GeoServer</div>
<div class="title">Figure 12. A gridded screenshot of the MapML viewer built for GeoServer</div>
</div>
<div class="paragraph">
<p><a href="#img_ldproxy">Figure 11</a> shows a screenshot of the landing page of an ldproxy instance that publishes data from the National Mapping Agency of the Federal Republic of Germany. The screenshot demonstrates the content negotiation capabilities supported by OGC APIs that enable a client application such as a web browser to request a resource in HTML and a different client application such as a developer utility (e.g. <a href="https://www.postman.com">postman</a>) to request the same resource in JSON.</p>
<p><a href="#img_ldproxy">Figure 13</a> shows a screenshot of the landing page of an ldproxy instance that publishes data from the National Mapping Agency of the Federal Republic of Germany. The screenshot demonstrates the content negotiation capabilities supported by OGC APIs that enable a client application such as a web browser to request a resource in HTML and a different client application such as a developer utility (e.g. <a href="https://www.postman.com">postman</a>) to request the same resource in JSON.</p>
</div>
<div id="img_ldproxy" class="imageblock text-center">
<div class="content">
<img src="images/ldproxy.png" alt="ldproxy" width="600">
</div>
<div class="title">Figure 11. A screenshot of the landing page of an ldproxy instance accessed using a web browser (left) and postman (right)</div>
<div class="title">Figure 13. A screenshot of the landing page of an ldproxy instance accessed using a web browser (left) and postman (right)</div>
</div>
<div class="paragraph">
<p><a href="#img_cubewerx">Figure 12</a> shows a screenshot of the CubeWerx Ship Detection processes running on Sentinel data in the Amazon Web Services Cloud. Available input datasets are listed on the left-hand side of the figure, whereas currently running and completed processes are listed on the right-hand side of the figure.</p>
<p><a href="#img_cubewerx">Figure 14</a> shows a screenshot of the CubeWerx Ship Detection processes running on Sentinel data in the Amazon Web Services Cloud. Available input datasets are listed on the left-hand side of the figure, whereas in-progress and completed jobs are listed on the right-hand side of the figure.</p>
</div>
<div id="img_cubewerx" class="imageblock text-center">
<div class="content">
<img src="images/cubewerx.png" alt="cubewerx" width="600">
</div>
<div class="title">Figure 12. A screenshot of the CubeWerx processes management tool</div>
<div class="title">Figure 14. A screenshot of the CubeWerx processes management tool</div>
</div>
<div class="paragraph">
<p><a href="#img_cubewerx2">Figure 13</a> presents example output from the CubeWerx Ship Detection processes. The positions of detected ships are shown by the red markers.</p>
<p><a href="#img_cubewerx2">Figure 15</a> presents example output from the CubeWerx Ship Detection processes. The positions of detected ships are shown by the red markers.</p>
</div>
<div id="img_cubewerx2" class="imageblock text-center">
<div class="content">
<img src="images/cubewerx2.png" alt="cubewerx2" width="600">
</div>
<div class="title">Figure 13. Example output from the CubeWerx Ship Detection processes</div>
<div class="title">Figure 15. Example output from the CubeWerx Ship Detection processes</div>
</div>
<div class="paragraph">
<p><a href="#img_pygeoapi_xarray">Figure 14</a> shows a screenshot of an x-array supported pygeoapi displaying a coverage. The coverage is accessed through an OGC API - Coverages interface and has been styled for portrayal purposes. The demonstration showed how OGC API - Tiles could be implemented alongside OGC API - Coverages to enable access to tiled coverage data.</p>
<p><a href="#img_pygeoapi_xarray">Figure 16</a> shows a screenshot of an x-array supported pygeoapi displaying a coverage. The coverage is accessed through an OGC API - Coverages interface and has been styled for portrayal purposes. The demonstration showed how OGC API - Tiles could be implemented alongside OGC API - Coverages to enable access to tiled coverage data.</p>
</div>
<div id="img_pygeoapi_xarray" class="imageblock text-center">
<div class="content">
<img src="images/pygeoapi-xarray.png" alt="pygeoapi xarray" width="600">
</div>
<div class="title">Figure 14. A screenshot of an x-array supported pygeoapi displaying a coverage</div>
<div class="title">Figure 16. A screenshot of an x-array supported pygeoapi displaying a coverage</div>
</div>
</div>
</div>
Expand Down
Binary file modified report/er.pdf
View file
Binary file not shown.
Binary file added report/images/hexagon.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added report/images/miramon.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added report/images/miramon2.png
View file
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 83d1f5b

Please sign in to comment.