Dataset Parameters
Feature Type Name(s)
This parameter allows you to choose different naming schemes, and the number of feature types generated for the reader.
Feature type name choices:
- From File Name(s): Generates one feature type per source filename.
- From Format Name: Produces only a single feature type containing the format name.
Read Additional Line Header Data
Enable this parameter to create and populate components from the ZFS Line Header fields, including software time, line number, user data, counters, and GPS coordinates.
- No (default): Do not create additional components for line header fields.
- Yes: Create additional components as defined in the capture. Available components depend on the parameters that were set on the scanner during capture time. The ZFS reader will produce components for all available Line Header fields in each input point cloud. As a result, two scans run with different scanner options may have differing schemas. Since these values do not change per point, each point within the same ZFS line will have the same values for each Line Header field component.
Read PPS/GPS Time Data
Enable this parameter to create components from the ZFS scan. These components contain information that will allow you to determine the time of point capture (if the scan was obtained with a PPS signal). The accuracy of these values is dependent on the equipment and settings used to capture the scan, as detailed in the Z+F documentation.
- No (default): Do not read time synchronization data and do not generate these components.
- Yes: Read and calculate time sync data and add their values to these components. Components created when using this option are: pps_week, pps_weeksec, and pps_seconds. The ZFS reader will add these components to the point cloud.
Note: Calculating the time synchronization data for the scan is expensive, and may take several minutes depending on the size of the input file.
Schema Attributes
Additional Attributes to Expose
Use this parameter to expose Format Attributes in Workbench when you create a workspace:
- In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
- In a non-dynamic scenario, you can use this parameter to expose additional attributes on multiple feature types.
Use 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 intersect with the bounding box are returned.
If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.
Clip to Search Envelope
When selected, this parameter removes any portions of imported features being read that are outside the Search Envelope.
The example below illustrates the results of the Search Envelope when Clip to Search Envelope is not selected (set to No) and when it is selected (set to Yes).
- No: Any features that cross the search envelope boundary will be read, including the portion that lies outside of the boundary.
- Yes: Any features that cross the search envelope boundary will be clipped at the boundary, and only the portion that lies inside the boundary will be read. The underlying function for the Clip to Search Envelope function is an intersection; however, when Clip to Search Envelope is selected, a clipping operation is also performed in addition to the intersection.
