index.rst 5.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141
  1. .. _demos:
  2. Demos
  3. =====
  4. This page contains helpful links to various information pages regarding GeoServer and its features. You do not need to be logged into GeoServer to access this page.
  5. The page contains the following options
  6. * :ref:`demos_demorequests`
  7. * :ref:`srs_list`
  8. * :ref:`demos_reprojectionconsole`
  9. * :ref:`demos_wcsrequestbuilder`
  10. .. figure:: img/demos_view.png
  11. Demos page
  12. If you have the :ref:`WPS <wps>` extension installed, you will see an additional option:
  13. * :ref:`demos_wpsrequestbuilder`
  14. .. figure:: img/demos_viewwps.png
  15. Demos page with WPS extension installed
  16. .. _demos_demorequests:
  17. Demo Requests
  18. -------------
  19. This page has example WMS, WCS, and WFS requests for GeoServer that you can use, examine, and change. Select a request from the drop down list.
  20. .. figure:: img/demos_requests.png
  21. Selecting demo requests
  22. Both :ref:`wfs` as well as :ref:`wcs` requests will display the request URL and the XML body. :ref:`wms` requests will only display the request URL.
  23. .. figure:: img/demos_requests_WFS.png
  24. WFS 1.1 DescribeFeatureType sample request (Demo Request :guilabel:`WFS_describeFeatureType-1.1.xml`)
  25. Click :guilabel:`Show Result` or :guilabel:`Show Result in New Page` to send the request to GeoServer. For WFS and WCS requests, GeoServer will automatically generate an XML response.
  26. :guilabel:`Show Result` will show GeoServer's response - both the response headers and the XML/image result - below the :guilabel:`Show Result` button.
  27. If GeoServer's response is XML and you have ticked :guilabel:`Pretty Print XML`, GeoServer's response will be shown with an easy to read styled formatting.
  28. :guilabel:`Show Result in New Page` will show GeoServer's result in a new page (your browser will render the result).
  29. .. figure:: img/demos_requests_schema.png
  30. Headers and XML response from a WFS 1.1 DescribeFeatureType sample request after pressing :guilabel:`Show Result`. (Demo Request :guilabel:`WFS_describeFeatureType-1.1.xml`)
  31. Submitting a WMS GetMap request displays an image based on the provided geographic data.
  32. .. figure:: img/demos_requests_WMS_map.png
  33. Headers and image response for a WMS GetMap request after pressing :guilabel:`Show Result`. (Demo Request :guilabel:`WMS_getMap_multilayer.url`)
  34. WMS GetFeatureInfo requests retrieve information regarding a particular feature on the map image.
  35. .. figure:: img/demos_requests_WMS_feature.png
  36. Plain text WMS GetFeatureInfo request after pressing :guilabel:`Show Result`. (Demo Request :guilabel:`WMS_featureInfo.url`)
  37. .. figure:: img/demos_requests_transaction.png
  38. WFS Transaction result after pressing :guilabel:`Show Result in New Page` (Your browser may render this differently). (Demo Request :guilabel:`WFS_transactionInsert.xml`)
  39. .. _srs_list:
  40. SRS List
  41. --------
  42. GeoServer natively supports almost 4,000 Spatial Referencing Systems (SRS), also known as **projections**, and more can be added. A spatial reference system defines an ellipsoid, a datum using that ellipsoid, and either a geocentric, geographic or projection coordinate system. This page lists all SRS info known to GeoServer.
  43. .. figure:: img/demos_SRS.png
  44. Listing of all Spatial Referencing Systems (SRS) known to GeoServer
  45. The :guilabel:`Code` column refers to the unique integer identifier defined by the author of that spatial reference system. Each code is linked to a more detailed description page, accessed by clicking on that code.
  46. .. figure:: img/demos_SRS_page.png
  47. Details for SRS EPSG:2000
  48. The title of each SRS is composed of the author name and the unique integer identifier (code) defined by the Author. In the above example, the author is the `European Petroleum Survey Group <http://www.epsg.org/>`_ (EPSG) and the Code is 2000. The fields are as follows:
  49. :guilabel:`Description`—A short text description of the SRS
  50. :guilabel:`WKT`—A string describing the SRS. WKT stands for "Well Known Text"
  51. :guilabel:`Area of Validity`—The bounding box for the SRS
  52. .. _demos_reprojectionconsole:
  53. Reprojection console
  54. --------------------
  55. The reprojection console allows you to calculate and test coordinate transformation. You can input a single coordinate or WKT geometry, and transform it from one CRS to another.
  56. For example, you can use the reprojection console to transform a bounding box (as a WKT polygon or line) between different CRSs.
  57. .. figure:: img/demos_reprojectionconsole.png
  58. Reprojection console showing a transformed bounding box
  59. Use :guilabel:`Forward transformation` to convert from source CRS to target CRS, and :guilabel:`Backward transformation` to convert from target CRS to source CRS.
  60. You can also view the underlying calculation GeoServer is using to perform the transformation.
  61. .. figure:: img/demos_reprojectionconsoledetails.png
  62. Reprojection console showing operation details
  63. Read more about :ref:`crs_handling`.
  64. .. _demos_wcsrequestbuilder:
  65. WCS Request Builder
  66. -------------------
  67. The WCS Request Builder is a tool for generating and executing WCS requests. Since WCS requests can be cumbersome to author, this tool can make working with WCS much easier.
  68. Read more about the :ref:`wcs_request_builder`.
  69. .. _demos_wpsrequestbuilder:
  70. WPS Request Builder
  71. -------------------
  72. GeoServer with the :ref:`WPS extension installed <wps_install>` includes a request builder for generating and executing WPS processes. Since WPS requests can be cumbersome to author, this tool can make working with WPS much easier.
  73. Read more about the :ref:`wps_request_builder`.