Select the File Geodatabase folder.
- If this option is unchecked (default) and a database already exists, then tables and features are written to the existing database.
- If this option is checked, any existing database is deleted before writing begins.
If no database exists when writing begins, a new database is created.
Note: After a database is deleted, it cannot be recovered – all data is lost.
If a template File Geodatabase is specified, the writer will make a copy of the template into the location specified in the Dataset parameter. All operations will be performed on the copy while the original template File Geodatabase remains unchanged.
The parameter is available only when Overwrite Existing Database is enabled.
Note: Since it is doing a complete copy, any data present in the template will also be copied to the destination. To remove unwanted data from tables or feature classes, set Truncate Table to Yes on each feature type. Alternatively, to copy only schema and not data, use ArcGIS to export the schema to an XML Workspace Document, then set the writer to import the resultant schema with the Import XML Workspace Document (Schema Only) parameter (below).
This parameter determines which version of Geodatabase should be created: 9.3, 10.0, or CURRENT (which is the default).
This parameter defines the type of compression to use on mosaic dataset overviews.
- JPEG (default)
- LZ77: The only valid compression option for images with a colormap.
- JPEG2000: Available only on rasters with an 8-bit pixel depth and no colormap
The degree of lossiness caused by the compression. Valid values are integers from 0 (lowest quality) to 100 (highest quality).
This value is ignored when not using one of the JPEG compression types.
Determines the resampling type to be used when generating reduced resolution pyramids on the destination raster dataset.
Nearest Neighbor is the default value, which provides the fastest output but the poorest quality. Cubic Convolution provides the best quality, but can reduce performance when writing.
Specifies the number of reduced resolution pyramids to build.
More pyramids enable better performance when viewing raster data using FME and Esri products.
This parameter tells the writer whether it should ignore features that would usually cause the translation to fail. This includes features that are topologically incorrect, are not supported by the Geodatabase writer, or conflict with the definition of the table to which it is to be inserted (that is, they are outside of the geometry envelope specified by the feature class). Additionally, the writer will also ignore polygons, donuts, or aggregates of polygons/donuts that cannot be reoriented.
The default setting is No, which means that failed features are not ignored and will cause the translation to fail when encountered.
This parameter sets the number of features to ignore before causing a translation to fail due to a problematic feature. (However, the translation may still fail for other reasons.)
Values:To ignore all failed features: -1; otherwise 0 or a positive integer.
This parameter allows you to store the failed features to an FFS file for later viewing.
This parameter allows you to specify an FME Feature Store (FFS) file to store any failed features.
This file will be created automatically, but will only be created if there is a failed feature.
Note: If the writer encounters a failed feature and writes to this file, and if a file with the same name already exists, the existing file will be overwritten.
This parameter is required when Dump Failed Features to File is set to Yes.
Values: path and filename
If either the path or the filename contains a space, the value must be enclosed in double quotation marks. The filename must end in the extension .ffs.