Changes between Version 36 and Version 37 of ZooWorkshop/FOSS4GJapan/CreatingOGRBasedWebServices

Timestamp:

Oct 16, 2010, 1:05:22 AM (14 years ago)

Author:

djay

Comment:

--

ZooWorkshop/FOSS4GJapan/CreatingOGRBasedWebServices

@@ -610 +610 @@
 ==== C Version ====
 
-Please add first the following code to the service.c source code :
+Please add first the following code to the {{{service.c}}} source code :
 
 {{{
@@ -627 +627 @@
   tmp1=getMapFromMaps(outputs,"Result","mimeType");
   if(strncmp(tmp1->value,"application/json",16)==0){
-    addToMap(outputs->content,"value",OGR_G_ExportToJson(res));
-    addToMap(outputs->content,"mimeType","text/plain");
+    char* tmp=OGR_G_ExportToJson(res);
+    setMapInMaps(outputs,"Result","value",tmp);
+    setMapInMaps(outputs,"Result","mimeType","text/plain");
+    free(tmp);
   }
   else{
-    addToMap(outputs->content,"value",OGR_G_ExportToGML(res));
-  }
-  outputs->next=NULL;
+    char* tmp=OGR_G_ExportToGML(res);
+    setMapInMaps(outputs,"Result","value",tmp);
+    free(tmp);
+  }
   OGR_G_DestroyGeometry(geometry);
   OGR_G_DestroyGeometry(res);
@@ -640 +643 @@
 }}}
 
-This new code is exactly the same as for the Boundary Service. The only thing we modified is the line where the OGR_G_ConvexHull function is called (rather than the OGR_G_GetBoundary you used before). It is better to not copy and paste the whole function and find a more generic way to define your new Services as the function body will be the same in every case. The following generic function is proposed to make things simpler :
+This new code is exactly the same as for the Boundary Service. The only thing we modified is the line where the [http://www.gdal.org/ogr/ogr__api_8h.html#7a93026cfae8ee6ce25546dba1b2df7d OGR_G_ConvexHull] function is called (rather than the OGR_G_GetBoundary you used before). It is better to not copy and paste the whole function and find a more generic way to define your new Services as the function body will be the same in every case. The following generic function is proposed to make things simpler :
 
 {{{
@@ -693 +696 @@
 The genericity of the applyOne function let you add two new Services in your ZOO Services Provider : !ConvexHull and Centroid.
 
-Note that you should define MY_OGR_Centroid function before the Centroid one as OGR_G_Centroid don't return a geometry object but set the value to an already existing one and support only Polygon as input, so to ensure we use the !ConvexHull for MultiPolygon. So please use the code bellow :
+Note that you should define MY_OGR_Centroid function before the Centroid one as [http://www.gdal.org/ogr/ogr__api_8h.html#23f5a19a81628af7f9cc59a37378cb2b OGR_G_Centroid] don't return a geometry object but set the value to an already existing one and support only Polygon as input, so to ensure we use the !ConvexHull for MultiPolygon. So please use the code bellow :
 
 {{{
@@ -709 +712 @@
 }}}
 
-To deploy your Services, you only have to copy the Boundary.zcfg metadata file from your cgi-env directory as !ConvexHull.zcfg and Centroid.zcfg. Then, you must rename the Service name on the first line to be able to run and test the Execute request in the same way you did before. You only have to set the Identifier value to !ConvexHull or Centroid in your request depending on the Service you want to run.
+To deploy your Services, you only have to copy the Boundary.zcfg metadata file from your cgi-env directory as {{{ConvexHull.zcfg}}} and {{{Centroid.zcfg}}}. Then, you must rename the Service name on the first line to be able to run and test the Execute request in the same way you did before. You only have to set the Identifier value to !ConvexHull or Centroid in your request depending on the Service you want to run.
 
 Note here that the !GetCapabilities and !DescribeProcess requests will return odd results as we didn't modified any metadata informations, you can edit the .zcfg files to set correct values. By the way it can be used for testing purpose, as the input and output get the same name and default/supported formats.