Reader Directives
The directives listed below are processed by the POINTCLOUDXYZ reader. The suffixes shown are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the Point Cloud XYZ reader is POINTCLOUDXYZ.
DATASET
This is the name of one or more XYZ files.
The default extension for Point Cloud XYZ files is .xyz, .csv, or .txt.
Required/Optional
Required
Mapping File Syntax
POINTCLOUDXYZ_DATASET /usr/data/filename.xyz
Workbench Parameter
Point Cloud XYZ File(s)
FIELD_NAMES
Values
yes | no (default)
Required/Optional
Optional
FIELD_NAMES_AFTER_HEADER
Values
yes | no
Required/Optional
Optional
SEPARATOR
Mapping File Syntax
POINTCLOUDXYZ_SEPARATOR \t
There must be a space between POINTCLOUDXYZ _SEPARATOR and <separator>. The opening and closing angle brackets are optional.
Required/Optional
Optional
Values
<separator>
SKIP_LINES
Required/Optional
Optional
Values
<number>
Workbench Parameter
Number of Lines to Skip
SKIP_FOOTER
Required/Optional
Optional
Values
<number>
DUPLICATE_DELIMS
Required/Optional
Optional
Values
yes | no
Workbench Parameter
Skip Duplicate Separators
COLUMN_TO_PCCOMPONENT
Values
<component name, column name> list, or <component name, column name, type > list
Required/Optional
Optional
Workbench Parameter
Component Mapping
STRIP_QUOTES
Values
yes | no
Required/Optional
Optional
Workbench Parameter
Strip Quotes
STRING_DATA_CONTAINS_DELIMS
Values
yes | no
Required/Optional
Optional
Workbench Parameter
String Data Contains Delimiters
ENCODING
This directive specifies the file encoding to use when reading.
Values
<encoding>
Encodings |
UTF-8 |
UTF-16LE |
UTF-16BE |
ANSI |
BIG5 |
SJIS |
CP437 |
CP708 |
CP720 |
CP737 |
CP775 |
CP850 |
CP852 |
CP855 |
CP857 |
CP860 |
CP861 |
CP862 |
CP863 |
CP864 |
CP865 |
CP866 |
CP869 |
CP932 |
CP936 |
CP950 |
CP1250 |
CP1251 |
CP1252 |
CP1253 |
CP1254 |
CP1255 |
CP1256 |
CP1257 |
CP1258 |
ISO8859-1 |
ISO8859-2 |
ISO8859-3 |
ISO8859-4 |
ISO8859-5 |
ISO8859-6 |
ISO8859-7 |
ISO8859-8 |
ISO8859-9 |
ISO8859-13 |
ISO8859-15 |
Required/Optional
Optional
Workbench Parameter
Character Encoding
MAX_LINES
Values
<number>
Required/Optional
Optional
Workbench Parameter
Maximum Lines to Read
SCAN_MAX_LINES
Values
<number>
Required/Optional
Optional
Workbench Parameter
Maximum Lines to Scan
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>
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
EXPOSED_ATTRS
This directive allows the selection of format attributes to be explicitly added to the reader feature type.
This is similar to exposing format attributes on a reader feature type once it has been generated; however, it is even more powerful because it enables schema-driven applications other than Workbench to access and leverage these attributes as if they were explicitly on the schema as user attributes.
The result of picking a list of attributes is a comma-separated list of attribute names and types that will be added to the schema features. Currently all reader feature types will receive the same set of additional schema attributes for a given instance of the reader.
Required/Optional
Optional
Mapping File Syntax
Not applicable.
While it is possible for FME Objects applications to invoke this directive, the required format is not documented.
This directive is intended for use in our GUI applications (for example, Workbench) only.
Workbench Parameter
Additional Attributes to Expose