Executing TDGeoExport - Geospatial Utilities

Teradata® Geospatial Utilities User Guide

Product
Geospatial Utilities
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2022-06-21
dita:mapPath
ygh1641301476787.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
B035-2519
Product Category
Teradata Tools and Utilities
  1. Execute TDGeoExport:
    java -Xms256m -Xmx1024m com.teradata.geo.TDGeoExport -l NODEID/geouser,geouser -t customers -f "ESRI Shapefile" point  -o C:\GeoSpatial\TestEnv\geodata -n customers

    Sample Output of TDGeoExport Utility

    C:\Program Files\Teradata\Client\17.20\bin>java -Xms256m -Xmx1024m com.teradata.geo.TDGeoExport -l NODEID/geouser,geouser -t customers -f "ESRI Shapefile" point -o C:\GeoSpatial\TestEnv\geodata -n customers
    ==============================================
    = Teradata GeoExport  VERSION 17.20.00.00    =
    =                                            =
    = Copyright 2014-2022 Teradata.              =
    = ALL RIGHTS RESERVED.                       =
    ==============================================
    Coordinate System defaulting to NAD83.
    Logon        = NODEID/geouser,****
    LOGMECH      = TD2
    DatabaseName = geouser
    Table Name   = customers
    Export to    = C:\GEOSPATIAL\TESTENV\GEODATA\customers
    File Format  = ESRI Shapefile
    Shape Type   = POINT
    Only 1 Type  = FALSE
    -------------------------------------------
    connecting to NODEID ... connected!
    -------------------------------------------
    exporting table customers to layer customers ...
    Warning 6: Normalized/laundered field name: 'cust_zipcode' to 'cust_zipco'
    (4/4)
    ===========================================
    
    Data exporting finished successfully!
    Exporting time is 10.395
    If the column name is more than 10 chars, tool will truncate and create 10 characters name.

    If -CSET UTF8 is specified, data is exported as UTF8 characters for char/varchar data types. If there are any database or JDBC connectivity issues, stack trace is printed to the console. Refer to JDBC or Vantage documentation for troubleshooting. If there are any errors with GDAL libraries, see http://www.gdal.org/.