The suffixes shown are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the DSFL reader is DSFL.
DATASET
Required/Optional: Required
The file name of the input DSFL file.
Example:
DMDF_DATASET /usr/data/dmdf/input.dd1
Workbench Parameter: Source DSFL File(s)
OUTPUT_ORIGINS
Required/Optional: Optional
Determines whether or not the origin data is output as a separate features. If the value is YES, then origin data is output as dsfl_origin feature type with each feature having its unique index number in dsfl_record_index_number attribute. If the value is NO, then the origin data is merged with other data features.
Range: YES | NO
Default: NO
Example:
DMDF_RASTER_POINT_FEATURE_CODE HA35000000
Workbench Parameter: Output Origin Data
KEEP_Z_NULL
Required/Optional: Optional
This directive determines whether or not to preserve the null value placeholder for z coordinates defined by %H9 header tag. If the value is YES, the z coordinate of the geometry will be unchanged; if the value is NO, it will be set to 0.
For example, if the %H9 tag is set to -99.00 and, while reading a feature, it encounters a z coordinate of -99.00, then based on the value of this keyword, either the z coordinate will remain as -99.00 (if value is YES) or changed to 0.0 (if the value is NO).
Range: YES | NO
Default: YES
Workbench Parameter: Preserve Original Null Value for Z
SPLINE_EDGE_TOLERANCE
Required/Optional: Optional
After the DSFL reader has converted splines to straight lines, this directive can be used to remove extraneous points. Real values from 0 and up are acceptable. If a negative number is input, the DSFL reader will ignore it, and not generalize the line. This will only be used if SPLINE_TO_POINTS was set to at least 1.
In Workbench, this functions like a LineGeneralizer transformer using the Douglas algorithm.
A recommended use is to set SPLINE_TO_POINTS to a moderately high number, such as 100, and then generalize to an acceptable precision. This will keep the overall number of points generated down, but will ensure precision is available where it is needed to keep the error down.
Example:
The following example sets the edge tolerance for generalizing lines to 2.5:
DSFL_SPLINE_EDGE_TOLERANCE 2.5
Workbench Parameter: Edge tolerance for generalizing splines
SPLINE_TO_POINTS
Required/Optional: Optional
The DSFL reader converts all spline curves into straight lines by inserting intermediate points. This directive specifies the number of intermediate points to be inserted. Integer values from 0 to 10 are acceptable. If an illegal value is entered, the DSFL reader will automatically use the default value of 3. The recommended range is 0 to 10.
Example:
The following example sets the number of intermediate points to be calculated to four:
DSFL_SPLINE_TO_POINTS 4
Range: >=0
Default: 3
Workbench Parameter: Points Per Segment
COMMA_IS_A_DELIMITER
Required/Optional: Optional
When set to “Yes”, this directive will tell the DSFL reader to also use the comma (,) as a delimiter when separating DSFL tokens as well as when parsing attributes. This will remove commas from attributes (for example, “Vancouver, Canada” becomes “Vancouver Canada”). Therefore, by setting this value to “No,” it will keep the commas in the attributes.
It should be noted that if the DSFL file’s tokens or coordinate points were separated with commas, then the reader may not work properly. However, since FME only supports the basic version of DSFL (and commas are not allowed to separate tokens and coordinates in the basic version), this should never be a problem.
The default value of this directive is “No”. However, if the directive is missing, then it will implicitly set the value to “Yes” so that workspaces created prior to the addition of this directive will continue to exhibit the same behavior as before.
Example:
DSFL_COMMA_IS_A_DELIMITER No
Range: Yes | No
Default: No
Workbench Parameter: Use Comma as a Delimiter
SEARCH_ENVELOPE
Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that interact with the bounding box are returned.
If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.
Mapping File Syntax
<ReaderKeyword>_SEARCH_ENVELOPE <minX> <minY> <maxX> <maxY>
Note: If all four coordinates of the search envelope are specified as zero, the search envelope will be disabled.
Required/Optional
Optional
Workbench Parameter
Minimum X, Minimum Y, Maximum X, Maximum Y
SEARCH_ENVELOPE_COORDINATE_SYSTEM
This directive specifies the coordinate system of the search envelope if it is different than the coordinate system of the data.
The COORDINATE_SYSTEM directive, which specifies the coordinate system associated with the data to be read, must always be set if the SEARCH_ENVELOPE_COORDINATE_SYSTEM directive is set.
If this directive is set, the minimum and maximum points of the search envelope are reprojected from the SEARCH_ENVELOPE_COORDINATE_SYSTEM to the reader COORDINATE_SYSTEM prior to applying the envelope.
Required/Optional
Optional
Mapping File Syntax
<ReaderKeyword>_SEARCH_ENVELOPE_COORDINATE_SYSTEM <coordinate system>
Workbench Parameter
Search Envelope Coordinate System
CLIP_TO_ENVELOPE
This directive specifies whether or not FME should clip features to the envelope specified in the SEARCH_ENVELOPE directive.
Values
YES | NO (default)
Mapping File Syntax
<ReaderKeyword>_CLIP_TO_ENVELOPE [yes | no]
Workbench Parameter
Clip To Envelope