Changeset 262 for trunk/docs/workshop/2010/exercise.txt
- Timestamp:
- Jul 15, 2011, 8:03:05 PM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/docs/workshop/2010/exercise.txt
r256 r262 2 2 3 3 Exercise 4 ####### 4 ######## 5 5 6 You know everything now about writting zcfg matadata files and get short pieces of code in ``service.c`` or ``ogr_service_provider.py`` depending if you choosen C or Python programming language respectively. 6 You know everything now about writting zcfg matadata files and get short pieces 7 of code in ``service.c`` or ``ogr_service_provider.py`` depending if you choosen 8 C or Python programming language respectively. 7 9 8 10 The goal of this exercise is to implement the following multiple geometries services : … … 14 16 15 17 C version 16 ********* *18 ********* 17 19 18 Your are now invited to edit the source.c file you have created during this workshop to add the multiple geometries, using the following OGR C-API functions : 20 Your are now invited to edit the source.c file you have created during this workshop 21 to add the multiple geometries, using the following OGR C-API functions : 19 22 20 23 - `OGR_G_Intersection <http://www.gdal.org/ogr/ogr__api_8h.html#5a271b5c7b72994120e7a6bbc7e7e5cb>`__ (OGRGeometryH, OGRGeometryH) … … 23 26 - `OGR_G_SymmetricDifference <http://www.gdal.org/ogr/ogr__api_8h.html#d6dacf495617a230c6f19950bc415f17>`__ (OGRGeometryH, OGRGeometryH) 24 27 25 You can use the ``Boundary.zcfg`` file as example, rename the InputPolygon input to ``InputEntity1`` and add a similar input named ``IntputEntity2``. You are invited to update other values in the ZOO Metadata File to set the proper metadata informations. 28 You can use the ``Boundary.zcfg`` file as example, rename the InputPolygon input 29 to ``InputEntity1`` and add a similar input named ``IntputEntity2``. You are 30 invited to update other values in the ZOO Metadata File to set the proper 31 metadata informations. 26 32 27 33 Python Version 28 ************** **34 ************** 29 35 30 Your are invited to edit the ``ogr_ws_service_provider.py`` file you created during this workshop to add the multiple geometries using the following ``osgeo.ogr`` Geometry methods applied on the first Geometry instance : 36 Your are invited to edit the ``ogr_ws_service_provider.py`` file you created 37 during this workshop to add the multiple geometries using the following 38 ``osgeo.ogr`` Geometry methods applied on the first Geometry instance : 31 39 32 40 - Intersection(Geometry) … … 35 43 - SymmetricDifference(Geometry) 36 44 37 You can once again use the ``Boundary.zcfg`` file as example, rename the ``InputPolygon`` input to ``InputEntity1`` and add a similar input named ``IntputEntity2``. You are invited to update other values in the ZOO metadata file to set the proper metadata informations. 45 You can once again use the ``Boundary.zcfg`` file as example, rename the ``InputPolygon`` 46 input to ``InputEntity1`` and add a similar input named ``IntputEntity2``. You are 47 invited to update other values in the ZOO metadata file to set the proper metadata 48 informations. 38 49 39 50 Testing your services 40 ********************* **51 ********************* 41 52 42 Once the multiple geometries Services are deployed on your local environment, please reload the ``zoo-ogr.html`` file created during the previous section from your browser and test your brand new ZOO Services. 53 Once the multiple geometries Services are deployed on your local environment, 54 please reload the ``zoo-ogr.html`` file created during the previous section 55 from your browser and test your brand new ZOO Services. 43 56
Note: See TracChangeset
for help on using the changeset viewer.