OpenStreetMap (OSM) Protocolbuffer Binary Format (PBF) Reader Parameters

This parameter specifies the maximum size of the in-memory temporary database that is used to process elements that reference other elements’ geometry. After this size is reached, the temporary database will be written to disk.

If not specified, a default value will be used.

The parameter controls whether or not to use a faster, but more failure-prone, method of indexing nodes during processing.

The faster method can fail if node IDs are non-increasing, or if node IDs are particularly large in value. In these cases, the translation will fail and an error message will recommend that this parameter be set to No.

By default, this parameter is set to Yes.

This parameter specifies the file that is used to control how OSM PBF files are interpreted. Undefined behavior may occur if this parameter is changed after an OSM PBF has been generated.

If customization is required, the default file can be found at the location shown as the default value for this parameter. It can be used as a template for a modified configuration file.

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 where you have multiple feature types, it is convenient to expose additional attributes using this one parameter. For example, if you have ten feature types and want to expose the same attribute in each one, it is easier to define it once than it is to set each feature type individually in the workspace.

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.

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.