Syntax - Analytics Database - Teradata Vantage

point

POINT point_spec

linestring

LINESTRING linestring_spec

polygon

POLYGON polygon_spec

multipoint

MULTIPOINT { EMPTY | ( point_spec [,...] ) }

multilinestring

MULTILINESTRING { EMPTY | ( linestring_spec [,...] ) }

multipolygon

MULTIPOLYGON { EMPTY | ( polygon_spec [,...] ) }

geometrycollection

GEOMETRYCOLLECTION { EMPTY | ( geometry_collection_item [,...] ) }

geosequence

GEOSEQUENCE {
  EMPTY |
  ( ( x-y_pair [,...] ),
    ( ts [,...] ),
    ( linkID [,...] ),
    ( count, uf [,...] )
  )
}

point_spec

{ EMPTY | ( x-y_pair_opt_z ) }

linestring_spec

{ EMPTY | ( x-y_pair_opt_z [,...] ) }

polygon_spec

{ EMPTY | ( linestring_spec [,...] ) }

geometry_collection_item

{ point |
  linestring |
  polygon |
  multipoint |
  multilinestring |
  multipolygon |
  geometry_collection |
  geosequence
}

x-y_pair

x y

x-y_pair_opt_z

x y [ z ]

Syntax Elements

EMPTY

The empty set.

x

A numeric value that represents the x coordinate of a point.

y

A numeric value that represents the y coordinate of a point.

z

A numeric value that represents the z coordinate of a point in 3D space.

ts

A timestamp value with the following format:

   yyyy-mm-dd hh:mi:ss.ms

The first timestamp value is associated with the first point, the second timestamp value is associated with the second point, and so forth.

You must specify n timestamp values, where n is the number of points in the geosequence.

linkID

A NUMERIC(18,0) value for the ID of the link on the road network for a point in the geosequence.

This value is reserved for a future release.

The first link ID value is associated with the first point, the second link ID value is associated with the second point, and so forth.

You must specify n link ID values, where n is the number of points in the geosequence.

count

An integer value that represents the number of uf elements for each point in the geosequence.

A value of 0 indicates that no uf elements appear after count in the character string.

uf

A user field that represents a FLOAT value to associate with a point. For example, certain tracking systems may associate velocity, direction, and acceleration values with each point.

You must specify count groups of n user field values (where n is the number of points in the geosequence). The first group provides the first user field values for each point, the second group provides the second user field values for each point, and so forth.