extensibility

Version: 1.2 - Created: 06 Nov 2009

Version: - Created: 02 Sep 2009

Teradata Geospatial Import/Export utilities for Windows and Linux. README Teradata TDGeoImportExport Release 1.1 for Teradata 13.0 Change History ========================================== Release 1.1 ----------- - Install directory changed from TDGeoImport to TDGeoImportExport - Added TDGeoExport to export geometries from the database Release 1.0 ----------- - Initial release Documentation ========================================================== Please see document B035-1181-098A, SQL Geospatial Types, for program documentation. Chapter 4, Data Loading and Formats describes TDGeoImport. A description of TDGeoExport is contained within this file Platforms ========================================================== This version of TDGeoImport/TdGeoExport runs on Windows 32-bit clients only. Software ========================================================== The Teradata Driver for the JDBC Interface on Windows must be installed. Example Run - TDGeoImport ========================================================== Assume an input file exists named co99_d00.shp in the directory c:\data\demo\load. Also assume that there is a user named geo_user and a database called mydb on a system called geo_system. Change to the TdGeoImportExport\bin directory and execute the following to load the layer named c099_d00 into the database: java -Xms256m -Xmx512m -classpath .;"c:\Program Files\Teradata\Tdat\LTDBMS\bin\terajdbc4.jar";"c:\Program Files\Teradata\Tdat\LTDBMS\bin\tdgssconfig.jar";. com.teradata.geo.TDGeoImport -l geo_system/geo_user,geo_pw -s mydb -f c:\data\demo\load -n co99_d00 Note that some large data files may exceed the Java Heap memory. In the above command, the -Xms option is used to set the initial Java heap size to 256MB. The -Xmx option is used to set the maximum Java heap size to 512MB. Example Run - TDGeoExport ========================================================== Assume a table named co99_d00 exists in the database mydb. It contains a column of type ST_Geometry. Also assume that there is a user named geo_user and a database called mydb on a system called geo_system. Change to the TdGeoImportExport\bin directory and execute the following to export the table to an ESRI shapefile named c099_d00 in the c:\data\demo\load directory. Note that this will overwrite any files of the same name in that directory: java -Xms256m -Xmx1024m -classpath .;"c:\Program Files\Teradata\Tdat\LTDBMS\bin\terajdbc4.jar";"c:\Program Files\Teradata\Tdat\LTDBMS\bin\tdgssconfig.jar";. com.teradata.geo.TDGeoExport -l geo_system/geo_user,geo_pw -s mydb -t co99_d00 -f "ESRI Shapefile" -o c:\data\demo\load -n co99_d00 Note that some large data files may exceed the Java Heap memory. In the above command, the -Xms option is used to set the initial Java heap size to 256MB. The -Xmx option is used to set the maximum Java heap size to 512MB. TDGeoExport Documentation ========================================================== TDGeoExport Data Export Program Purpose Convert geospatial data from the database into ESRI and TIGER/Line data. Syntax TDGeoExport -l logon_string -s database_name -t table_name -f format_name -o output_directory_name [-n layer_name] Where: -l logon_string: the Teradata Database logon string, where the format of logon_string is: Database/User,Password -s database_name: the database name that contains the table to convert -t table_name: the table name (or view) to convert -f format_name: Output file format name. The possible values are as follows: -f "ESRI Shapefile" -f "TIGER" -f "MapInfo File" -o output_directory_name: the directory where the output data files will be generated -n layer_name: the name of the layer to create (defaults to the table name) Usage Notes 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 file(s) in the directory specified by the -o output_directory_name parameter. Restrictions There can be at most one geospatial column in the table. BLOB/CLOB columns and UDT columns other than the ST_Geometry column are not supported.  

Version: - Created: 02 Sep 2009

 The Teradata Geospatial Extension includes types, methods, functions, and utilities for loading, modeling, and analyzing spatial objects. README Teradata Geospatial Release 1.4 The Orange Book can be found in install\doc\Geospatial Orange Book.doc The open source libraries can be found in install\Open Source. Release 1.4 ----------- - TDGeoImport in releases prior to 1.4 did not support splitting large polygons with inner rings when the "-z 2" option was used. This restriction has been removed with release 1.4. The existing "-z 2" option will now split polygons/multipolygons with inner rings in them. - There was a bug where TDGeoImport may generate a geometry that is slightly too big, which would fail during the mload execution. This has been fixed. - Beginning in 1.3, AggGeomIntersection and AggGeomUnion would erroneously report an error if a MultiPolygon or MultiLineString were involved in the aggregation. This has been fixed. MultiPolygons and MultiLineStrings are supported in the union and intersection aggregate functions. Geometry collections are not supported, and an error will be reported if a geometry collection is passed to the aggregate function or if a geometry collection is produced during the execution of the aggregate function (e.g., union of a point and a linestring, which produces a geometry collection). Release 1.3 ----------- - Fixed a problem where the installation would fail if you unzipped the installation files into a Windows directory that contains spaces in the path name. ERRORWITHPATH would show up in the external name clause of CREATE FUNCTION statements. - Fixed a problem where you install the geospatial files onto a Linux system for the first time and it is unable to create the /home/tdatuser/geospatial/1.0 directory. The previous solution was to repeat the installation a second time. This is no longer necessary. - Fixed a problem where you may get a library not found error after adding additional UDTs/functions to the SYSUDTLIB database. A /etc/ld.so.conf.d/tdgeospatial.conf file was added so that ld can locate the libraries in /home/tdatuser/geospatial/1.0. - Fixed two problems in AggGeomUnion and AggGeomIntersection concerning NULL parameters passed to this functions and NULL geometry values. - The install will now abort with an error message if you try to install this on an invalid platform/DBS version. Supported versions include: MP-RAS (6.x and greater), Windows (6.x and 12.x), Linux (6.x and 12.x). Release 1.2 ----------- - Fixed failure in ST_Transform on Linux and MP-RAS platforms. Error message: Error in call to transform in ST_Point_Transform. This fix may also prevent lib rev errors after a DBS restart. - Fixed performance bug on MP-RAS when SpheroidalDistance is called on two points that are at the same location. Release 1.1 ----------- - Added SpheroidalDistance functions - Fixed missing libraries for SLES10 and Windows 64-bit installation Release 1.0 ----------- - Original release  

Version: - Created: 20 May 2009

The Teradata Geospatial Extension includes types, methods, functions, and utilities for loading, modeling, and analyzing spatial objects. README Teradata Geospatial Release 1.3 The Orange Book can be found in install\doc\Geospatial Orange Book.doc The open source libraries can be found in install\Open Source. Release 1.3 ----------- - Fixed a problem where the installation would fail if you unzipped the installation files into a Windows directory that contains spaces in the path name. ERRORWITHPATH would show up in the external name clause of CREATE FUNCTION statements. - Fixed a problem where you install the geospatial files onto a Linux system for the first time and it is unable to create the /home/tdatuser/geospatial/1.0 directory. The previous solution was to repeat the installation a second time. This is no longer necessary. - Fixed a problem where you may get a library not found error after adding additional UDTs/functions to the SYSUDTLIB database. A /etc/ld.so.conf.d/tdgeospatial.conf file was added so that ld can locate the libraries in /home/tdatuser/geospatial/1.0. - Fixed two problems in AggGeomUnion and AggGeomIntersection concerning NULL parameters passed to this functions and NULL geometry values. - The install will now abort with an error message if you try to install this on an invalid platform/DBS version. Supported versions include: MP-RAS (6.x and greater), Windows (6.x and 12.x), Linux (6.x and 12.x). Release 1.2 ----------- - Fixed failure in ST_Transform on Linux and MP-RAS platforms. Error message: Error in call to transform in ST_Point_Transform. This fix may also prevent lib rev errors after a DBS restart. - Fixed performance bug on MP-RAS when SpheroidalDistance is called on two points that are at the same location. Release 1.1 ----------- - Added SpheroidalDistance functions - Fixed missing libraries for SLES10 and Windows 64-bit installation Release 1.0 ----------- - Original release

Version: - Created: 26 Feb 2009

Teradata XML Services provide assistance in database transformation of XML structures to and from relational structures. This is primarily an enterprise fit feature. XML in this context is regarded as a data format that is used to describe incoming or outgoing warehouse data. A key concept for this feature is that we are not transforming to store XML but rather to maintain a relational data model or to integrate relational data into an enterprise XML message structure! The relational data model is bested suited for enterprise analytics. XML structures are best suited for enterprise integration. This feature will be delivered asynchronously from any specific Teradata warehouse release. The delivery format will be as a web download, available for each Teradata server platform. The feature is considered a part of the Teradata product and will be supported through normal support channels. Teradata XML Services consists of the following components: Xerces XML parser and Xalan XSLT transformer packaged as a platform specific operating system library. Shredding Framework which consists of a combination of stored procedures and functions. A stored procedure controls the shredding process. When shredding one to a few documents the stored procedure directly invokes the data maintenance DML. When shredding many documents, the stored procedure uses a set-based approach through the invocation of a table generation function. Parallel Publishing Framework which consists of a combination of stored procedures and functions. A stored procedure will control the publishing process. The stored procedure can either return a string representing an XML object type or a SQL statement that represents the XML data stream. The SQL statement can be reused in views, macros, fast export, etc. General purpose XSLT transformation function. Two XPATH search functions, one that returns a scalar character value and one that returns an XML fragment character value. XML schema validation function. XML Schema and Stylesheet loading and dependency resolution. XML schema generation procedures. Perl based installation process.