ArcGIS Engine Developer Guide

BUILDING A COMMAND-LINE JAVA APPLICATION
BUILD SUCCESSFUL
Total time: 1 second
Now that your build environment is prepared, you can proceed with writing the
Java source code for the example application.
Use your favorite text editor or IDE to write
your source code.
Creating the TintoPoint main class
1. Begin your source code by adding the signature for the main class in this exercise:
package engine.scenario.analyst3d;
The datasourcesfile, geodatabase, geometry, and
system Java packages are the equivalent of the
DataSourcesFile, GeoDatabase, Geometry, and
System libraries of ArcGIS Engine.
public class TintoPoint{}
The class will eventually have three private static methods and one public main
entry point. For the sake of simplicity, private static methods are used to do the
work for the application. While some Java developers believe that when a
method can be either static or an instance, an instance method should be utilized,
this scenario uses the simplest approach—static methods. Each of these methods
will be covered in upcoming sections.
Next, look at what imports are required by the class.
As discussed earlier, this scenario uses the datasourcesfile, geodatabase, geometry,
and system Java packages.
• datasourcesfile—provides workspace factories and workspaces for vector data
formats supported by the geodatabase API. You will use the
ShapefileWorkspaceFactory class in this exercise to create your generated 3D
shapefile.
• geodatabase—provides all definitions relating to data access including TINs
and feature classes. You will be using the GeometryDef class to define spatial
qualities for your generated feature class.
• geometry—contains the core geometry objects, as well as spatial reference
information. In this scenario, you will use the Point class as a representation of
all the TIN nodes in your input TIN dataset.
• system—contains objects that expose services used by the other libraries
within ArcGIS Engine. You will use the AoInitializer object to initialize and
uninitialize your application.
2. Below the package declaration you made above, import the classes as shown.
Use fully qualified imports so you can see explicitly which classes from the
ArcGIS Engine—Java API you are working with.
import java.io.File;
import java.io.IOException;
import com.esri.arcgis.datasourcesfile.ShapefileWorkspaceFactory;
import com.esri.arcgis.geodatabase.Field;
import com.esri.arcgis.geodatabase.Fields;
import com.esri.arcgis.geodatabase.GeometryDef;
import com.esri.arcgis.geodatabase.IEnumTinNode;
import com.esri.arcgis.geodatabase.IFeatureBuffer;
import com.esri.arcgis.geodatabase.IFeatureClass;
import com.esri.arcgis.geodatabase.IFeatureClassProxy;
416 • ArcGIS Engine Developer Guide