Product
VPF Product Name
The value for this parameter is the type of VPF product database to produce:
DNC, FFD, VMAP0, VMAP1, VMAP2, DNC, UVMAP.
- Copy the schema template for your product into FME_HOME/vpf. See one of the other schema templates in FME_HOME/vpf for an example.)
- Open the file FME_HOME/metafile/vpf_db.fmf and add your product type on the line:
GUI CHOICE PRODUCT DNC%FFD%VMAP0%VMAP1%VMAP2%UVMAP VPF Product Name:
by adding %<product_type> after UVMAP.
For example:
GUI CHOICE PRODUCT DNC%FFD%VMAP0%VMAP1%VMAP2%UVMAP%NEW_PRODUCT VPF Product Name:
The name of the product type in the metafile must be the same as the folder containing the schema template within FME_HOME/vpf, although the case of the letters can be different.
Workbench Navigator Parameters
These parameters are visible in the Navigator pane after you add the writer to the workspace.
VPF Feature Class Separator
The value for this parameter is the character that is used in a feature’s feature type to separate the library and coverage names from the metadata table and feature class names.
If this attribute is not specified, then the backslash (\) separator is assumed.
Log all Messages
In addition to typical FME log messages, the VPF writer module can also generate many internal information messages. By default, this parameter is set to exclude these internal messages.
- Yes: All the messages including internal messages and the writer itself will be logged.
- No: Only messages coming from the writer module will be logged. Any messages generated internally by the writer will not be logged.
Writer Mode
Note: For more information on this parameter, see the chapter Database Writer Mode.
In UPDATE mode, the destination dataset may contain previously written coverages; existing entries in the database-level Coverage Attribute Table (CAT) will be left intact. Note that each coverage being written by the current translation will still be overwritten in this mode; the point of this mode is to allow separate coverages to be written by distinct translations and for the destination database to be valid as a whole.
In OVERWRITE mode, the destination folder tree is cleared at the beginning of the translation. Use caution with this mode, since any existing data in the destination folder will be lost.
Skip Tile Clipping
By default, this parameter is set to No.
Setting this parameter to Yes assumes that the data is already clipped to the tiles, and can increase workspace performance if:
- the source dataset is also VPF;
- the data has not been modified so that it violates the integrity of the tiling.
Thematic Index Order
When writing a thematic index, if a template for the file exists in the product schema (for example, install/vpf/vmap1/lib/bnd/txt_id.tti), the ordering given in the template's header will be respected: S for sorted, and anything else for unsorted.
If a template for the file does not exist, by default, FME writes unsorted thematic indexes.
This parameter allows you to change the default:
- Unsorted if no template
- Sorted if no template
- Always Sorted
- Always Unsorted