coverageview.rst 4.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394
  1. .. _coverage_views:
  2. Coverage Views
  3. ==============
  4. Starting with GeoServer 2.6.0, You can define a new raster layer as a Coverage View.
  5. Coverage Views allow defining a View made of different bands originally available inside coverages (either bands of the same coverage or different coverages) of the same Coverage Store.
  6. Creating a Coverage View
  7. ------------------------
  8. In order to create a Coverage View the administrator invokes the :guilabel:`Create new layer` page.
  9. When a Coverage store is selected, the usual list of coverages available for publication appears.
  10. A link :guilabel:`Configure new Coverage view...` also appears:
  11. .. figure:: images/coverageviewnewlayer.png
  12. :align: center
  13. Selecting the :guilabel:`Configure new Coverage view...` link opens a new page where you can configure the coverage view:
  14. .. figure:: images/newcoverageview.png
  15. :align: center
  16. The upper text box allows to specify the name to be assigned to this coverage view. (In the following picture we want to create as example, a **currents** view merging together both u and v components of the currents, which are exposed as separated 1band coverages).
  17. .. figure:: images/coverageviewname.png
  18. :align: center
  19. Next step is defining the output bands to be put in the coverage view.
  20. It is possible to specify which input coverage bands need to be put on the view by selecting them from the :guilabel:`Composing coverages/bands...`.
  21. .. figure:: images/coverageviewselectbands.png
  22. :align: center
  23. Once selected, they needs to be added to the output bands of the coverage view, using the :guilabel:`add` button.
  24. .. figure:: images/coverageviewaddbands.png
  25. :align: center
  26. Optionally, is it possible to remove the newly added bands using the :guilabel:`remove` and :guilabel:`remove all` buttons.
  27. Once done, clicking on the :guilabel:`save` button will redirect to the standard Layer configuration page.
  28. .. figure:: images/coveragevieweditlayer.png
  29. :align: center
  30. Scrolling down to the end of the page, is it possible to see the bands composing the coverage (and verify they are the one previously selected).
  31. .. figure:: images/coverageviewbandsdetails.png
  32. :align: center
  33. At any moment, the Coverage View can be refined and updated by selecting the :guilabel:`Edit Coverage view...` link available before the Coverage Bands details section.
  34. .. figure:: images/coveragevieweditlink.png
  35. :align: center
  36. Once all the properties of the layer have been configured, by selecting the :guilabel:`Save` button, the coverage will be saved in the catalog and it will become visible as a new layer.
  37. .. figure:: images/coverageviewavailablelayers.png
  38. :align: center
  39. Heterogeneous coverage views
  40. ----------------------------
  41. In case the various coverages bound in the view have different resolution, the UI will present
  42. two extra controls:
  43. .. figure:: images/coverageviewhetero.png
  44. :align: center
  45. The **coverage envelope policy** defines how the bounding box of the output is calculated for metadata
  46. purposes. Having different resolutions, the coverages are unlikely to share the same bounding box. The possible values are:
  47. * **Intersect envelopes**: Use the intersection of all input coverage envelopes
  48. * **Union envelopes**: Use the union of all input coverage envelopes
  49. The **coverage resolution policy** defines which target resolution is used when generating outputs:
  50. * **Best**: Use the best resolution available among the chosen bands (e.g., in a set having 60m, 20m and 10m the 10m resolution will be chosen)
  51. * **Worst**: Use the worst resolution available among the chosen bands (e.g., in a set having 60m, 20m and 10m the 60m resolution will be chosen)
  52. The coverage resolution policy is *context sensitive*. Assume the input is a 12 bands Sentinel 2 dataset at three different
  53. resolution, 10, 20 and 30 meters, and a false color image is generated by performing a band selection in the SLD.
  54. If the policy is *best* and the SLD selects only bands at 20 and 60 meters, the output will be at 20 meters instead of
  55. 10 meters.
  56. Coverage View in action
  57. -----------------------
  58. A Layer preview of the newly created coverage view will show the rendering of the view. Note that clicking on a point on the map will result into a GetFeatureInfo call which will report
  59. the values of the bands composing the coverage view.
  60. .. figure:: images/coverageviewlayerpreview.png
  61. :align: center