SDTS export control file

SDTS conversion control file format

An Export To SDTScontrol file allows you to convert INFO tables that are not named using the in_dataset prefix. It can also be used to override default global information and information read from standard SDTS INFO tables.

Each command in the control file takes one line. A line that starts with the characters /* is a comment and will not be executed. The file contains the EXPORT command, a global control block, zero or more feature class or table sections, and the END command.

Global commands

These commands are only valid in the global control block (Scope: Global).

• Table <INFO_name> {IGNORE}—Allows conversion of INFO tables other than the default. The default INFO tables are those that have the same base name as the <in_dataset> name or {in_point_cover} name if specified.
• Title <string> {MasterDD}—Adds a title subfield in the IDEN or MIDE module, where max string is 1024 long.
• Version <d.nn> {MasterDD}—Adds a Data ID subfield in the IDEN or MIDE module, where d = a positive integer with no leading zeros, and nn = a two-digit positive integer.
• MapDate <YYYYMMDD>—Adds a Map Date subfield in the IDEN module.
• CreationDate <YYYYMMDD> {MasterDD}—Adds a dataset creation date subfield in the IDEN or MIDE module.
• MapScale <scale>—Adds a Map scale denominator subfield in the IDEN module.
• ConformanceLvl <level> {MasterDD}—Adds a conformance feature-level subfield in the IDEN or MIDE module, where <level> is 1, 2, 3, or 4.
• ScaleFactor {sfax} {sfay}—Adds and applies x- and y-scale factors to spatial coordinates and subfields in the IREF module where {sfax} {sfay} are real values.
• Shift {xorg} {yorg}—Adds and applies x- and y-origin subfields in the IREF module, where {xorg} {yorg} are real values.
• HorizontalRes {xhrs} {yhrs}—Adds an x- and y-component of horizontal resolution subfields in IREF, where {xhrs} {yhrs} are real values.
• Comment <TEXT | FILE> <module_name> <string>—Adds comment subfields in the MIDE, IDEN, IREF, XREF, or SPDM module.
• AddRecord <TEXT | FILE> <module_name> <string>—Adds Comment subfields in the MQCG, MQHL, DQAA, DQCG, DQHL, DQLC, or DQPA module.

Other export commands

These commands are not limited to the global scope. See each command description for details of where it can be used.

• AUTHORITY <Attr_/Entity_Authority> <Authority_Description>

  Scope: Global and FeatureClass and Table

  Set the attribute (or entity) authority and full description. If the authority is another FIPS standard, then specify FIPS as the authority and give a full reference as the description. The AUTHORITY statement in the Global control block also affects the contents of a README file for TVP transfer and MasterDD transfer.

  Default value: Authority = "unknown" Authority_Desc = ""

  Example: AUTHORITY ESRI 'Environmental System Research Institute, Inc.'

• CellLabel <label_string>

  This command is only used for the RASTER profile.

  Set the output cell value subfield label. If it is not specified, LABEL is used.

• CellNull <null_value>

  This command is only used for the RASTER profile.

  Set the output null value when exporting grid NODATA cells. If you do not specify the cell null value, default values are used according to cell type.

  Cell type	Default null value
  I	-2147483647
  R	-2147483647
  BI8	-127
  BI16	-32767
  BI32	-2147483647
  BUI8	255
  BUI15	4294967295
  BFP32	-2147483647

• CellSequenceCode <GI|GL|GJ>

  This command is only used for the RASTER profile.

  When exporting multiple grids (that is, layers), module RSDF, subfield CSCD can be set through this keyword. If not specified, GI is used.

• DDDEFINITION ENT <Entity_Label> {Entity_Label_Definition} {Source_Definition} DDDEFINITION ATT <Attr_Label> {Attr_Label_Definition} {Source_Definition}

  Scope: FeatureClass and Table

  Allow the definition of the Entity label or Attribute label (that is, subfield) to be translated into the Data Dictionary/Definition module as a record.

  Note: An attribute label's data dictionary information in the DDDF module is altered only if the DDDefinition statement exists in Conv_Ctrl_File and it mentions the attribute label.

  Example 1: DDEFINITION ATT BANK "Describe river bank" "TIGERI Dictionary"

  Example 2: DDDEFINITION ENT 0500206 "This code identifies Danger curve"

• DDDOMAIN <Attr_Label> <Domain_Type> <Domain_Val_Format> <Measure_Unit> ~ <Range_or_Value> <Domain_Val> <Domain_Val_definition>

  Scope: FeatureClass and Table

  This command allows the setting of the attribute label's value domain (that is, range).

  Example 1: DDDOMAIN BANK ENUMERATED A "" VALUE "" "Not Applied"

  Example 2: DDDOMAIN BANK ENUMERATED A "" VALUE L "River left bank"

  Example 3: DDDOMAIN BANK ENUMERATED A ""VALUE R "River Right bank"

• EXPORT Starting of export section, use as conversion control by SDTSExport.
• FEATURECLASS <Arc_FeaCls{.sub_cls}> {IGNORE}

  This marks the beginning of a coverage feature classes block. All commands in the block only apply to this one feature class. The block ends with the next FEATURECLASS, TABLE, END, or IMPORT command.

• HorizontalFmt <BFP64 | BI32> HFMT <BFP64 | BI32>

  This command is only used for the POINT profile.

  Note: HFMT is shorthand for HorizontalFmt. You can use this keyword to specify the HFMT subfield in the IREF module. If the user does not use this keyword to specify the horizontal format, the default value BFP64 is used (that is, high-precision double).

• IGNOREITEM <Item1> {Item2} . . . {Item9}

  Scope: Global and FeatureClass and Table

  Ignore INFO items (Maximum 9 items) so that they are not translated into an SDTS module.

• ITEMBECOMES <item> <Attr_Label> {Format} {Max_length} {Key_Type} {Measurement_Unit} {Description}

  Scope: Global and FeatureClass and Table

  Use the SDTS attribute label (subfield) definition for an INFO item instead of using the default definition.

  Default values

  Parameter	Default value
  key_Type	NOKEY
  Measurement_Unit	""
  Description	Same as the Attr_Label parameter

  INFO data types	SDTS data types							A	I	R	S	C	B16	B32
  	D	1			X	X
  C(n)	1
  I(1-16)		1
  N(1-16)			1
  B(2 bytes)						1
  B(4 bytes)							1
  F(4 bytes)			1
  F(8 bytes)			1

  Key:

  • 1 = Default data type for given INFO data type
  • X -- Invalid data type for given INFO data type
• SRCDEFINITION <Source_Definition>

  Scope: Global and FeatureClass and Table

  ENT or ATT labels' source of definition

  Example 1: SRCDEFINITION 'ARC/INFO Data Model, Concepts, & Key Terms'

  Example 2: SRCDEFINITION "TIGERI Dictionary"

• TABLE <INFO_name> {IGNORE} TABLE <INFO_name> {out_module_name}

  Optional TABLE control blocks allow conversion of INFO tables other than the default. The default INFO tables are those that have the same base name as the <in_dataset> name or {in_point_cover} name if specified.

Command parameter definitions and notes

<Field> and <Tag> are used interchangeably.

<SubField>, <Label>, and <Attr_Label> are used interchangeably.

The following are some of the parameters used by various control file commands:

• Arc_FeaCls{.sub_cls}:

  ARC | NODE | POINT | POLY | TIC | LINK | BND | ANNO.subcls | SECTION.subclass | ROUTE.system | REGION.subclass

• Domain_Type:

  GR-CHARS | ALPHANUM | ALPHABET | INTEGER | REAL | BINARY | ENUMERATED | FIPSCODE

• Domain_Val_Format:

  Value	Meaning
  A	Graphics characters
  I	Implicit-point (integer)
  R	Explicit-point unscaled (fixed-point real)
  S	Explicit-point scaled (floating-point real)
  B	Bitfield data
  BFP32	32-bit floating-point real
  BFP64	64-bit floating-point real
  BI8	8-bit signed integer
  BI16	16-bit signed integer
  BI24	24-bit signed integer
  BI32	32-bit signed integer
  BUI8	8-bit unsigned integer
  BUI16	16-bit unsigned integer
  BUI24	24-bit unsigned integer
  BUI32	32-bit unsigned integer
  C	Character

• Format:

  Either a Domain_Val_Format or ^ (Packed foreign identifier; see 4.1.3.6.7)

• Key_Type:

  NOKEY | PKEY | FKEY | PFKEY

• Range_or_Value:

  VALUE | MIN | MAX

• DQ_Module_Name:

  DQHL | DQPA | DQAA | DQLC | DQCG | MQCG | MQHL

• TEXT:

  The <string> argument is treated as a regular text string.

• FILE:

  The <string> argument is treated as a path to an ASCII text file, and its contents are saved in the target module's subfield.