- -logmech logon_mechanism
- Teradata Logon mechanism ,which determines the connection's authentication and encryption capabilities (either TD2 (default) or LDAP).
- -logdata log_data
- Specifies additional data needed by a logon mechanism.
- -l logon_string
- Database logon string, where the format of logon_string is: Database/User,Password
- -s data_source_name
- Database name that contains the table to convert
- -t table_name
- Table name (or view) to convert
- -f format_name
- Output file format name. The valid values for format_name are:
- MapInfo File
- TIGER version_code
- ESRI Shapefile shape_type [ ONLY ]
Exported ESRI Shapefiles can contain only one shape type, which must be specified. "POINT","LINESTRING","POLYGON","MULTIPOINT","MULTILINESTRING","MULTIPOLYGON" shape type can be specified for 2D geometry type and "POINT25D","LINESTRING25D","POLYGON25D","MULTIPOINT25D","MULTILINESTRING25D", "MULTIPOLYGON25D","POINTZ","POLYGONZ","MULTIPOINTZ" can be specified for 3D geometry type. If multiple shape types occur in the table that is to be exported, specify the optional ONLY keyword to restrict the export to only the specified type. Perform separate export operations to export several different shape types.
- -o output_directory_name
- Directory where the output data files will be generated
- -a_srs coordinate_system_name
- Coordinate system. If not specified, the default is to use the coordinate system appropriate to the output file format type. -a_srs can be specified as one of the four well-known systems (WGS84, WGS72, NAD83, NAD27) or in the form of EPSG:n where n is EPSG GCS or PCS code.
- -n layer_name
- Optional name of the layer to create.
If the -n option is omitted, then TDGeoExport uses the table name as the name of the layer to create.
- -CSET charset_name
- Specifies the client character set while logging onto the database.
If not present default character set is assumed. (ASCII for N/W clients)Applicable values are UTF8.
The table or view should consist of a single geometry column of type ST_Geometry and one or more additional columns which represent the feature attributes. Each row of the table is considered a feature and the entire table is considered a layer. All columns in the table will be converted to the layer. If a subset of columns in the table is desired instead of the entire table, a view that represents this subset should be created.
The program will place the output files in the directory specified by the
-a_srs can be specified as one of the four well-known systems (WGS84, WGS72, NAD83, NAD27) or in the form of EPSG:n where n is the EPSG GCS or PCS code. Note that this does NOT perform a transformation. It sets the spatial reference system of the exported data so that an external program can interpret the data using the specified coordinate system.
When TIGER is specified as output format, we now require a version_code to be specified. This is because specific versions adhere to specific structures and other requirements, and must therefore be specified for correct export.
Please use the following as TIGER version_code for corresponding TIGER/Line Shapefiles as mentioned in below table while exporting in TIGER data format.
|0000||TIGER/LINE Precensus Files, 1990|
|0002||TIGER/LINE Initial Voting District Codes Files, 1990|
|0003||TIGER/LINE Files, 1990|
|0005||TIGER/LINE Files, 1992|
|0021||TIGER/LINE Files, 1994|
|0024||TIGER/LINE Files, 1995|
|0697 to 1098||TIGER/LINE Files, 1997|
|1298 to 0499||TIGER/LINE Files, 1998||Range is not numeric. It is in mmyy.|
|600, 700, 800||TIGER/LINE Files, 1999||Range is not numeric. It is in mmyy.|
|1000, 1100||TIGER/LINE Files, Redistricting Census 2000|
|0301 to 0801||TIGER/LINE Files, Census 2000||Range is not numeric. It is in mmyy.|
|0302 to 0502||TIGER/LINE Files, UA 2000||Range is not numeric. It is in mmyy.|
|1002 to 0603||TIGER/LINE Files 2002||Range is not numeric. It is in mmyy.|
|1203 to 0304||TIGER/LINE Files, 2003||Range is not numeric. It is in mmyy.|
|0404 +||TIGER/LINE Files, 2004 e.g. 0504 will set TIGER_2004 as export format||The format is mmyy.|
When ESRI Shapefile is specified as output format, we now require a shape_type to be specified. ESRI Shapefile can only contain one shape type, so we require the user to decide what shape type will be for any given export. If the shape type is incorrect (i.e., ANY value in the geometry column contains data of a different type) an error will be reported, and export will fail. If the user knows that multiple shape types are in one table which will be exported, the user can specify “only” following shape type and ONLY shapes of the specified type will be exported. All others will be skipped over. In this way, data which contains multiple shape types can be exported, with a different export/Shapefile for each shape type.
Geometrycollection cannot be specified as a shapetype when ESRI Shapefile is specified as output format. If specified the export job will terminate with an error.
If the geometry column contains geometrycollection shape type data then this geometry data cannot be exported with any of the supported shape type names.