Write Spatial Data

Write Spatial Data allows you to insert data into a writable named table as output of a job, or update or delete records in a named table using a primary key or a filter. You have the option to insert the columns that you would like to write to the table; it is not necessary to specify all columns. If a column is not specified, a null value will be inserted. The option to update or delete by filter allows you to use an MI SQL WHERE clause to specify criteria for the operation. The option to update or delete by primary key uses the primary key as the criteria; the primary key matches the input features with the features in the table that you want to update or delete.

Note: You must have View permissions on the named table as well as Create/Modify/Delete permissions on the named table's associated dataset to perform insert, update, and delete operations on writable tables. See Users and Roles in the Administration section for more information.

The Write Spatial Data stage requires an upstream stage such as Read From File or Read Spatial Data. This stage also accepts geometries that are generated by stages in the Enterprise Routing Module, such as a LineString or Polygon.

Since Write Spatial Data uses an existing named table, it is necessary to create a writable named table where records will be inserted, updated, or deleted using the Spectrum Spatial Manager before configuring the Write Spatial Data stage.

Note: The Write Spatial Data stage supports PostgreSQL/PostGIS, Oracle, SQL Server, GeoPackage, and generic JDBC tables. It also supports MapInfo native TAB and extended native TAB (NativeX) files. The table must include a primary key for the table to be writable. Named tables with composite primary keys are not writable.

ACL Authorization Flow

To insert insert data into a writable named table, the user (or the role they belong to) needs both EXECUTE and CREATEpermission on the Named table.