Add Terrain Points (3D Analyst) |
|
Release 9.3
Last modified February 9, 2011 |
![]() ![]() ![]() Print all topics in : "Tools" |
NOTE: This topic was updated for 9.3.1.
This adds multipoints to an embedded terrain feature class by appending them or by using them to replace existing multipoints that fall within the same extent.
Usage tips
This tool adds multipoints to a feature class embedded in a terrain. The terrain and the embedded feature class must already exist.
Only multipoints can be embedded in a terrain. Therefore, the input feature class must be of type multipoint.
This tool performs two types of operations, APPEND and REPLACE. Use the method argument to indicate which mode of operation you want to use.
Either operation uses a rectangular Area of Interest (AOI). By default, the AOI is equal to the extent of the input feature class. The geoprocessing environment can be used to define a specific extent if a subset of the input feature class is desired. In the case of APPEND, the vertices of the input feature class that fall within the AOI will be added. REPLACE works in two phases. First, vertices of the embedded feature class that fall within the AOI are deleted. Then, those within the AOI of the source feature class are added. If a multipoint crosses the AOI boundary, only those vertices within the boundary are operated on.
If you want to add points to a regular feature class potentially referenced by a terrain but not embedded in it, use the Append tool.
Add Terrain Points looks for an existing edit session to piggyback on. This supports undo if the edit session was initialized to support undo (e.g., using the Editor inside ArcMap). If there's no edit session, it starts and stops one itself, in which case there is no chance for an undo.
In order to use this tool on a terrain inside an SDE database, the terrain needs to be registered as versioned. You do this by registering the feature dataset the terrain lives in as versioned.
Adding points to an embedded feature class will invalidate the terrain. Run Build Terrain after adding points.
The following environment settings affect this tool:
Command line syntax
An overview of the Command Line window
AddTerrainPoints_3d <in_terrain> <terrain_feature_class> <in_feature_class> {APPEND|REPLACE}
Parameter | Explanation | Data Type |
<in_terrain> |
The terrain dataset to be modified |
Terrain Layer |
<terrain_feature_class> |
The embedded feature class to which points will be added |
String |
<in_feature_class> |
The feature class containing the points to be added |
Feature Layer |
{APPEND|REPLACE} |
Indicates whether points are appended to the target or used to replace those in the target |
String |
AddTerrainPoints_3D d:\workspace\gdb.mdb\dataset\myterrain lidarpoints d:\workspace\gdb.mdb\dataset\newpoints append
Scripting syntax
About getting started with writing geoprocessing scripts
AddTerrainPoints_3d (in_terrain, terrain_feature_class, in_feature_class, method)
Parameter | Explanation | Data Type |
in_terrain (Required) |
The terrain dataset to be modified |
Terrain Layer |
terrain_feature_class (Required) |
The embedded feature class to which points will be added |
String |
in_feature_class (Required) |
The feature class containing the points to be added |
Feature Layer |
method (Optional) |
Indicates whether points are appended to the target or used to replace those in the target |
String |
# Purpose: Add data points to an embedded terrain (append or replace). # Create the Geoprocessor object import arcgisscripting gp = arcgisscripting.create() #Check out the 3D Analyst extension gp.CheckOutExtension ("3D") try: # Set the workspace (to avoid having to type in the full path to the data every time) gp.workspace = "D:/Docs1/GP/GPOutput" # Select the 3D Analyst Toolbox gp.toolbox = "3D" # Process: Add data points to an embedded terrain gp.addterrainpoints_3d ("napa_terrain.mdb/napa_terrain/napa_terrain_justpointsembed", "napa_points", "napa_terrain.mdb/napa_buildtest/mass", "APPEND") # Note: use backslashes to break up long lines if needed except: # If an error occurred while running the tool, print the error messages. print gp.GetMessages()