Import From SDTS (Coverage)

Summary

Creates ArcGIS coverages or grids from a Spatial Data Transfer Standard (SDTS) Topological Vector Profile (TVP) or Point Profile Transfer.

Usage

• SDTS is a large standard composed of smaller, more limited subsets that are federally approved as part of the SDTS FIPS 173 standard. These subsets are called profiles. The Topological Vector Profile (designed specifically for planar vector data with topology), raster, and point profiles are the only profiles supported by Import From SDTS. The type of profile being converted is automatically determined by the tool.

• Import From SDTS can read the U.S. Bureau of the Census TIGER, U.S. Geological Survey (USGS) DLG-3 vector data, National Geodetic Survey geodetic control point data, and USGS DEM raster data in SDTS format.

• A set of files containing global information about more than one transfer can be external from the transfer but must be under a directory called masterdd located at the same directory level as the transfer directory. If the command is executed from the same directory as the transfer files, specify a path to the prefix so the masterdd is used correctly. For example, ..tvpdata\tr01 would be used as the input prefix if the master data dictionary is at the same level as the tvpdata directory.

• Polygon and line topology is generated for TVP data. Point topology is generated for Point Profile data.

• Complex spatial object modules in a TVP transfer are converted to either regions or route/sections depending on the spatial object type.

• Aggregated spatial object modules or data layers are converted separately by executing Import From SDTS for each layer or raster object record number in the transfer.

• The raster profile provides a flexible way to encode raster data. In a raster transfer, there should be one RSDF module, one LDEF module, and one or more cell modules. Each record in the RSDF module denotes one raster object. Each raster object can have multiple layers. Each layer will be encoded as one record in the LDEF module. The actual grid data is stored in the cell module which is referenced by the layer record. A typical USGS DEM dataset will have one RSDF record, one LDEF record, and one cell file. A typical ERDAS image dataset will have one RSDF record, multiple LDEF records, and one or more cell files.

• Related attribute tables are written to the output dataset.

• The relate environment is stored in Output Dataset.REL and/or Output Point Cover.REL.

• An additional cross reference table, Output Dataset.XREF, will be written to store both the from and to table information for all related attribute tables.

• Attribute tables will be named with either Output Dataset or Output Point Cover prefix and either APxx or ASxx extensions. Region and Route subclasses will be named with FFxx extensions.

• Use the AIDF module when converting an SDTS dataset that was created by the Export to SDTS tool. The module contains information on items and redefined items in INFO.

• Information in the CATS module is saved as follows:

  • CATS-MAP—Saved in <out_dataset>.IDEN as item MAP
  • CATS-DOMN—Saved in Output Dataset.IDEN as item MAP
  • CATS-THEM—Saved in Output Dataset.IDEN as item THEME
  • CATS-AGOB—Saved in Output Dataset.IDEN as item LAYER

    If the COMT subfield contains valuable information, the NAME and COMT subfields are saved in Output Dataset.CATS as items NAME and COMT.

Syntax

SDTSImport_arc (in_transfer_prefix, output, {out_point_cover}, {layer_name}, {data_dictionary}, {convert_void})

Parameter	Explanation	Data Type
in_transfer_prefix	A four-character prefix common to all files in the SDTS transfer. The prefix may include a pathname to a directory. If no directory pathname is given, the files in the transfer will be read from the current workspace.	String
output	The coverage or grid to be created.	Coverage; Grid
out_point_cover (Optional)	The name of an optional point coverage to be created when the Topological Vector Profile is converted. This option is ignored if the SDTS dataset is not the Point Profile Transfer.	Coverage
layer_name (Optional)	The name of an aggregated spatial object that represents a single data layer in a transfer. There can be multiple layers in a single transfer. By default, the first layer encountered is the only one that will be converted.	String
data_dictionary (Optional)	Option to retain or drop the data dictionary. DD —Retain the data dictionary. DROP_DD —Discard the data dictionary.	Boolean
convert_void (Optional)	Used to convert or preserve void and fill values in the raster transfer. In the raster profile, NULL values are defined in two general categories: (Undefined, not relevant) or (Relevant but unknown or missing). CONVERT —Convert void and fill values in the raster transfer. PRESERVE —Preserve void and fill values in the raster transfer.	Boolean

Code Sample

SDTSImport example (stand-alone script)

The following stand-alone script demonstrates how to import a coverage from SDTS format.

# Name: SDTSImport_Example.py
# Description: Imports a coverage from SDTS format
# Requirements: ArcInfo Workstation
# Author: ESRI

# Import system modules
import arcpy
from arcpy import env

# Set environment settings
env.workspace = r"C:\data"

# Set local variables
inTransferPrefix = "UTHY"
output = "C:/output/uthydro"
dataDictionary = "DROP_DD"

# Execute SDTSImport
arcpy.SDTSImport_arc(inTransferPrefix, output, "", "", dataDictionary, "")

Environments

Current Workspace, Level Of Comparison Between Projection Files, Precision For Derived Coverages, Precision For New Coverages, Scratch Workspace

Licensing Information

ArcView: No

ArcEditor: No

ArcInfo: Requires ArcInfo Workstation installed