Execute TDGeoImport:
java -Xms256m -Xmx512m -classpath .;terajdbc4.jar;tdgssjava.jar;tdgssconfig.jar;tdgeospatial.jar; com.teradata.geo.TDGeoImport -l hyvm20/geouser, geouser -s geouser -f D:\anuguraju\anuguraju\GeoSpatial\TestEnv\geodata -n customers
Figure 7 shows execution of TDGeoImport.
Figure 7: TDGeoImport Example
Note: 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 Teradata 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 Teradata Database or JDBC connectivity issues, stack trace is printed to the console. Refer to JDBC or Teradata Database documentation for trouble shooting. 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.
Figure 8 shows the data imported from the import job.
Figure 8: Imported Data Using BTEQ Example