Final tweaks

Author: archaeogeek

Geoprocessing/Testing.md

@@ -7,20 +7,25 @@ It's a bit more difficult to fully test our Buffer function in a browser, but we
 We will use the QGIS WPS Plugin to Execute this process, to save trying to pass the nodes of a polygon via a URL!
 
 Go to the Applications button in the top left of your screen and go to Education\QGIS (not QGIS browser or server):
+
 ![Opening QGIS](../images/open_qgis.png)
 
 This will load QGIS 2.0, which is a little out of date but the same process should hold for later versions. Chances are, the WPS plugin is not yet installed, so click on Plugins on the top menu, and then "Manage and Install Plugins":
+
 ![Load Plugins](../images/load_plugins.png)
 
 Select "Get more from the list on the left, then in the Search bar, type WPS. In the results window you should see "WPS Client". Select it, then click on "Install plugin":
+
 ![WPS plugin](../images/wps_plugin.png) 
 
 Hopefully you will receive a message that the plugin installed successfully, then click on "Close" in the bottom right to close the plugin manager.
 
 First, load some suitable data to construct a buffer with. The OSGeo Live DVD contains plenty of spatial data for us to use. Click on "Layer/Add Vector Layer" in the QGIS menu:
+
 ![Add Vector Data](../images/add_vector.png)
 
 For the source dataset, browse to /home/user/data/vector/world_merc and click on world_merc.shp. If you can't see this, make sure that the file type dropdown list at the bottom of the browser window shows "ESRI Shapefiles [OGR]":
+
 ![ESRI Shape Files](../images/esri_shp.png)
 
 Then click "Open", and "Open" in the "add vector layer" dialog box to load the shapefile in the main window.
@@ -44,6 +49,7 @@ In the URL box type the path to the zoo_loader.cgi:
 Click OK to make this dialogue box disappear, and then with your new connection visible in the Server Connections box, click "Connect" to connect to the server.
 
 If the URL was correct, you should now see a long list of processes or Identifiers, with their Title and Abstract. If the list of Identifiers is not in alphabetical order, click the column title to sort it to your liking:
+
 ![WPS Processes](../images/wps_processes.png)
 
 From the list, find the Buffer service, and either highlight it and click "OK", or double-click it. This will bring up a simple form with the Input Vales in it. Enter the following options:

GettingStarted/HelloWorld.md

@@ -39,21 +39,21 @@ In the file manager, navigate to the /usr/lib/cgi-bin directory and right-click
 
 The first 8 lines contain metadata about the service. These include the following:
 
-* **processVersion**: A user-defined version number for the service
-* **storeSupported**: Should ZOO be able to store the results of the service? (True/False)
-* **statusSupported**: Should ZOO be able to run the service as a background task? (True/False)
-* **serviceProvider**: The name of the file containing the code for the service
-* **serviceType**:  The programming language used
+* **processVersion**: A user-defined version number for the service;
+* **storeSupported**: Should ZOO be able to store the results of the service? (True/False);
+* **statusSupported**: Should ZOO be able to run the service as a background task? (True/False);
+* **serviceProvider**: The name of the file containing the code for the service;
+* **serviceType**:  The programming language used.
 
 This section can also contain a <MetaData> section if you like, containing additional information about the service.
 
 Below the metadata section are the DataInputs and DataOutputs sections. The DataInputs block contains the following:
 
-* **[name]**: The name of the input- this is how it will be referred to in the service code
-* **Title/Abstract**: Metadata about the input, for use in the DescribeProcess response
-* **minOccurs/maxOccurs**: Mandatory- the number of times the input will occur
-* **<LiteralData>**: The type of data node for the input. Remember from the introduction that the data type can either be LiteralData, BoundingBoxData or ComplexData.
-* **dataType**: The type of data for the given node.
+* **[name]**: The name of the input- this is how it will be referred to in the service code;
+* **Title/Abstract**: Metadata about the input, for use in the DescribeProcess response;
+* **minOccurs/maxOccurs**: Mandatory- the number of times the input will occur;
+* **<LiteralData>**: The type of data node for the input. Remember from the introduction that the data type can either be LiteralData, BoundingBoxData or ComplexData;
+* **dataType**: The type of data for the given node;
 * **<Default />**: Mandatory section, but not used for LiteralData types.
 
 The DataOutputs block contains very similar sections, but instead of describing the input, it's describing the output response. Therefore it doesn't need to contain the minOccurs/maxOccurs sections.
@@ -68,9 +68,9 @@ Each service function must return an integer value representing the execution st
 
 Each service takes exactly three arguments, and these are in the form of python dictionaries, which are a type of Key Value Pair:
 
-* **conf**: the main environment configuration (eg the information from main.cfg)
-* **inputs**: the requested or default inputs
-* **outputs**: the requested or default outputs
+* **conf**: the main environment configuration (eg the information from main.cfg);
+* **inputs**: the requested or default inputs;
+* **outputs**: the requested or default outputs.
 
 If you open hello_service.py in a text editor you will see the following:
 

Introduction/Summary.md

@@ -4,7 +4,7 @@ The three WPS packages are listed below.
 
 ## Geoserver
 
-![Geoserver Logo](../images/Geoserver.png)
+![Geoserver Logo](../images/geoserver.png)
 
 [Geoserver](http://Geoserver.org) is a fully featured Web Mapping Server, and WPS integration is available as an addition. It has the advantage of being easier to install and comes pre-configured with a number of WPS processes, but it is not possible to create your own processes.
 

Routing/Map.md

@@ -82,6 +82,8 @@ The runRouting function is defined at line 597, and the first thing it does is t
 
 Finally, two further WPS processes are also called in this block: UnionOneGeom and computeRouteProfile. These are needed for the elevation profile which is also computed, and the turn-by-turn directions.
 
+### The End!
+
 If you are interested in building your own web application for WPS using openlayers then there are a number of useful tutorials. For one that is specific to ZOO, I would recommend the [Practical Introduction to ZOO](http://www.zoo-project.org/docs/workshop/2010/index.html) given at FOSS4G 2010 (Osaka).