- Execute TDGeoImport:
java -Xms256m -Xmx512m com.teradata.geo.TDGeoImport -l NODEID/geouser,geouser -s geouser -f C:\GeoSpatial\TestEnv\geodata -n customers
Sample Output of TDGeoImport Utility
C:\Program Files\Teradata\Client\17.20\bin>java -Xms256m -Xmx512m com.teradata.geo.TDGeoImport -l NODEID/geouser,geouser -s geouser -f C:\GeoSpatial\TestEnv\geodata -n customers ============================================== = Teradata GeoImport VERSION 17.20.00.00 = = = = Copyright 2014-2022 Teradata. = = ALL RIGHTS RESERVED. = ============================================== DatabaseName = geouser Data Source = C:\GeoSpatial\TestEnv\geodata LayerName = customers LOGMECH = TD2 Logon = NODEID/geouser,**** connecting to NODEID ... connected! Validating layer: customers All layers successfully validated. ------------------------------------------- Importing layer customers to table CUSTOMERS... (4/4) =========================================== Data importing finished successfully! Importing time is 79.275
If a user specifies -m, a MULTISET. SET table is created by default.It is always better to have a unique column in data because UDT expects uniqueness of the row. Because the database requires ordering functionality for UDTs, an ordering definition exists for the ST_Geometry type. In general, however, ordering ST_Geometry types by their ordering definitions is neither useful nor meaningful. Currently these tools support only one ST_Geometry column and for good results, keep it the same as the last column.
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/.
If a user inserts a multipolygon shape type data into the geometry column of the table and exports successfully via TDGeoExport, then during import the GDAL library reads the data, and if it finds any invalid coordinates in the layer, it will insert geometry data as a Polygon shape type, instead of multipolygon, into the target table.
Example to Verify the Target Table Data Using BTEQ
C:\Program Files\Teradata\Client\17.20\bin>bteq .logon NODEID/dbc,dbc Teradata BTEQ 17.20.00.01 (64-bit) for WIN64. PID: 1964 Copyright 1984-2022 Teradata. All rights reserved. Enter your logon or BTEQ command: .logon NODEID/dbc, *** Logon successfully completed. *** Teradata Database Release is 17.10.03.01 *** Teradata Database Version is 17.10.03.01 *** Transaction Semantics are BTET. *** Session Character Set Name is 'ASCII'. *** Total elapsed time was 3 seconds. BTEQ -- Enter your SQL request or BTEQ command: database geouser; database geouser; *** New default database accepted. *** Total elapsed time was 1 second. BTEQ -- Enter your SQL request or BTEQ command: help user geouser; help user geouser; *** Help information returned. One row. *** Total elapsed time was 1 second. Table/View/Macro name Kind Comment ------------------------------ ---- --------------------------------------- CUSTOMERS T ? BTEQ -- Enter your SQL request or BTEQ command: sel * from customers; sel * from customers; *** Query completed. 4 rows found. 4 columns returned. *** Total elapsed time was 1 second. PKEY CUST_NAME CUST_ZIPCO POINT ----------- ---------- ---------- ----------------------------------------- 3 Mary Willo 90642 POINT (21.45 88.12) 0 Fred Smith 91234 POINT (20.34 80.78) 1 Richard Co 95421 POINT (20.56 89.44) 2 Anita John 98523 POINT (19.12 88.22) BTEQ -- Enter your SQL request or BTEQ command: .logoff; .logoff; *** You are now logged off from the DBC. Teradata BTEQ 17.20.00.01 (64-bit) for WIN64. Enter your logon or BTEQ command: .quit; .quit; *** Exiting BTEQ... *** RC (return code) = 0