1. JSON to IGeometry: The server will receive a json object representing the polygon digitized by the user. The first step is to convert the JSONObject to IGeometry. I particularly liked NicoGIS's solution to the issue which is shown below:
public IGeometry ConvertAnyJsonGeometry(JsonObject jsonObjectGeometry)
{
object[] objArray;
if (jsonObjectGeometry.TryGetArray("rings", out objArray))
{
return Conversion.ToGeometry(jsonObjectGeometry, esriGeometryType.esriGeometryPolygon);
}
if (jsonObjectGeometry.TryGetArray("paths", out objArray))
{
return Conversion.ToGeometry(jsonObjectGeometry, esriGeometryType.esriGeometryPolyline);
}
if (jsonObjectGeometry.TryGetArray("points", out objArray))
{
return Conversion.ToGeometry(jsonObjectGeometry, esriGeometryType.esriGeometryMultipoint);
}
try
{
return Conversion.ToGeometry(jsonObjectGeometry, esriGeometryType.esriGeometryPoint);
}
catch
{
try
{
return Conversion.ToGeometry(jsonObjectGeometry, esriGeometryType.esriGeometryEnvelope);
}
catch
{
return null;
}
}
} 2. IGeometry to IFeatureClass: Once I have IGeometry, many times I want to convert it to an IFeatureClass so I can use it in an operation like zonal statistics. Zonal Statistics actually takes an IGeodataset, but IFeatureClass extends IGeodatatset, so all that is required is a cast. Here is a function to convert IGeometry to IFeatureClass:
public IFeatureClass CreateFeatureClassFromGeometry(IGeometry pGeometry, IFeatureWorkspace pOutFeatWorkspace, int wkid = 4236)
{
try
{
IFields pFields = new Fields() as IFields;
{
// Set up the shape field for the feature class
IFieldsEdit pFieldsEdit = (IFieldsEdit)pFields;
IField pField = new Field();
IFieldEdit pFieldEdit = (IFieldEdit)pField;
pFieldEdit.Name_2 = "Shape";
pFieldEdit.Type_2 = esriFieldType.esriFieldTypeGeometry;
IGeometryDef pGeometryDef = new GeometryDef();
IGeometryDefEdit pGeometryDefEdit = (IGeometryDefEdit)pGeometryDef;
pGeometryDefEdit.GeometryType_2 = pGeometry.GeometryType;
ISpatialReference pSpatialReference;
if (wkid == 4326)
{
ISpatialReferenceFactory2 pSpaRefFact2 = new SpatialReferenceEnvironment() as ISpatialReferenceFactory2;
IGeographicCoordinateSystem pGeoCoordSys = pSpaRefFact2.CreateGeographicCoordinateSystem(wkid);
pSpatialReference = (ISpatialReference)pGeoCoordSys;
}
else if (wkid == 102100 || wkid == 3857)
{
ISpatialReferenceFactory2 pSpaRefFact2 = new SpatialReferenceEnvironment() as ISpatialReferenceFactory2;
IProjectedCoordinateSystem pProjCoordSys = pSpaRefFact2.CreateProjectedCoordinateSystem(wkid);
pSpatialReference = (ISpatialReference)pProjCoordSys;
}
else
{
throw new ArgumentNullException("Invalid Spatial Reference Well Known Id: Please use 4326 for Geographic or 102100 for Web Mercator");
}
ISpatialReferenceResolution pSpatialReferenceResolution = (ISpatialReferenceResolution)pSpatialReference;
pSpatialReferenceResolution.ConstructFromHorizon();
pGeometryDefEdit.SpatialReference_2 = pSpatialReference;
pFieldEdit.GeometryDef_2 = pGeometryDef;
pFieldsEdit.AddField(pField);
// Add other required fields to the feature class
IObjectClassDescription pObjectClassDescription = new FeatureClassDescription();
for (int i = 0; i < pObjectClassDescription.RequiredFields.FieldCount; i++)
{
pField = pObjectClassDescription.RequiredFields.get_Field(i);
if (pFieldsEdit.FindField(pField.Name) == -1)
pFieldsEdit.AddField(pField);
}
}
// Create the feature class
string sFeatureClassName = "tmp" + Guid.NewGuid().ToString("N");
IFeatureClass pFeatureClass = pOutFeatWorkspace.CreateFeatureClass(
sFeatureClassName, pFields, null, null, esriFeatureType.esriFTSimple, "Shape", null);
// Add the input geometry to the feature class and return
IFeatureCursor pFeatureCursor = pFeatureClass.Insert(true);
IFeatureBuffer pFeatureBuffer = pFeatureClass.CreateFeatureBuffer();
pFeatureBuffer.Shape = pGeometry;
pFeatureCursor.InsertFeature(pFeatureBuffer);
// Flush the feature cursor and release COM objects
pFeatureCursor.Flush();
Marshal.ReleaseComObject(pFeatureBuffer);
Marshal.ReleaseComObject(pFeatureCursor);
return pFeatureClass;
}
catch (Exception e)
{
Console.WriteLine(e.Message);
throw e;
}
}
3. Create In-Memory Workspace: As you notice, the function above requires a workspace. I like to use in-memory workspaces and to create them I use the following function:
public IWorkspace CreateInMemoryWorkspace()
{
try
{
// Create an InMemory workspace factory.
IWorkspaceFactory workspaceFactory = new InMemoryWorkspaceFactory() as IWorkspaceFactory;
// Create an InMemory geodatabase.
IWorkspaceName workspaceName = workspaceFactory.Create("", "MyWorkspace", null, 0);
// Cast for IName.
IName name = (IName)workspaceName;
//Open a reference to the InMemory workspace through the name object.
IWorkspace workspace = (IWorkspace)name.Open();
return workspace;
}
catch (Exception e)
{
Console.WriteLine(e.Message);
throw e;
}
}
4. Get Raster Dataset from Map Service: Keep in mind that an SOE has access to any of the feature classes in the service which uses the SOE as a capability. This means that you shouldn't usually need to have any hardcoded data paths in the actual code. Rather you should try an only use data from the map service itself. If you send in the index of the value raster the user wants to run analysis on, look how easy it is to open:
public IGeoDataset GetGeoDatasetByMapServiceIndex(IMapServer3 mapServer, int layerID)
{
IMapServerDataAccess dataAccess = (IMapServerDataAccess)mapServer;
return dataAccess.GetDataSource(mapServer.DefaultMapName, layerID) as IGeoDataset;
}
5. Pre-loading Rasters during Init(): Loading and unloading rasters from memory can be an expensive operation. Fortunately with SOEs, you can load data into memory when the service starts up, and have it standing by for any request which come in. This is different than Python geoprocessing services which basically need to load data once the actual request is receive. One idea I've been using is to create a data dictionary when the service starts up which keeps my value rasters standing by:
public Dictionary<int, IGeoDataset> CreateGeodatasetDictionary(IMapServer3 mapServer)
{
Dictionary<int, IGeoDataset> data_dictionary = new Dictionary<int, IGeoDataset>();
IMapServerInfo msInfo = mapServer.GetServerInfo(mapServer.DefaultMapName);
IMapLayerInfos layerInfos = msInfo.MapLayerInfos;
int c = layerInfos.Count;
for (int i = 0; i < c; i++)
{
IGeoDataset data = GetGeoDatasetByMapServiceIndex(mapServer, c);
data_dictionary.Add(c, data);
}
return data_dictionary;
}
Basically this dictionary is a mapping between map service indexes and their IGeodatasets which I create in the SOE Init() function and store in memory for the life of the SOE.
6. Running Zonal Statistics: Now that we have both the zone dataset and the value raster at our figure tips, the zonal statistics operation is just a couple lines of code. There are many examples of how to use the zonalops class, but here's the idea:
IZonalOp oZonalOp = new RasterZonalOpClass();
ITable zonalStats = oZonalOp.ZonalStatisticsAsTable(zones, valueRaster, true);
7. ITable to IRecordSet: To return the results of the Zonal Stats from the SOE, you must first convert the ITable to an IRecordSet. Here an straightforward way to do it:
public static IRecordSet ConvertTableToRecordset(ITable table)
{
IRecordSetInit recordSetInit = new ESRI.ArcGIS.Geodatabase.RecordSetClass();
recordSetInit.SetSourceTable(table, new QueryFilterClass());
IRecordSet recordset = recordSetInit as IRecordSet;
return recordset;
}
8. Serialize IRecordset: To convert the IRecordset into return JSON, you can simply use the Conversion.ToJSON method as follows:
IRecordSet return_records = BSharpUtilities.ConvertTableToRecordset(areaTable);
byte[] jsonBytes = Conversion.ToJson(return_records);
return Encoding.UTF8.GetString(jsonBytes, 0, jsonBytes.Length);
That's about it for now. For information on getting started with SOEs, I would check out ESRI's samples that come with the .NET SDK and also NicoGIS posts
