JSONFragmenter

For each newly created feature, the attribute identified by the JSON Attribute parameter will contain JSON text referred to by the JSON query.  

The json_type attribute will contain the JSON type of the text (object, array, string, etc) and the json_index parameter will contain the object key or array index of the JSON value.

If the JSON query cannot be fully evaluated, a message will be logged, and the translation will continue.

The JSON Attribute parameter identifies the feature attribute which contains the original JSON text.

For each newly created feature that is output through the Exploded port, the attribute identified by this parameter will contain JSON text referred to by the JSON query.

The JSON Query parameter is the JSON query referring to the JSON values which will become new FME features.  

A JSON query is a mechanism to refer to values inside JSON text. The outermost JSON value, which must be an object or an array, is always referred to by the term "json".  Contained values can be referred to using JavaScript-like square bracket index operators.  A value in an array can be referred to using its zero-based position in the array (for example, json[2] for the third element).

A value in an object can be referred to using its object key name. For example:

json["key"]

All of the values in an array or object can be referred to collectively using a wildcard index. For example:

json[*]

The query used by this transformer can have multiple expressions, separated by a '+' operator. This allows the transformer to refer to values in different areas of the JSON text. For example:

json["resultSet_1"][*] + json["resultSet_2"][*]

See below for more information on JSON queries.

If the JSON text is in GeoJSON or EsriJSON format, you can select "Explode as format" to "GEOJSON" or "ESRIJSON". This will inform JSONQueryFactory that GeoJSON or ESRIJSON features need to be automatically recognized and extracted from the query results.

The default format, "JSON", parses the JSON text as plain JSON. If no GeoJSON or ESRIJSON features were constructed, a warning will be issued and the text will be treated as plain JSON.

If the JSON query produces a JSON Object, the keys may be used to produce additional attributes for the new feature(s) by setting ‘Load Keys as Attributes’ to ‘Yes’. If the JSON query produces a JSON array, and a value is provided to the ‘Prefix New Attributes With’ parameter, a list attribute will be created, using the prefix as the list name, and the JSON array values as the list elements.

Note: Attribute lists are not accessible from the output schema in Workbench unless they are first processed using a transformer that operates on them, such as ListExploder or ListConcatenator. All attribute list transformers are displayed in the Contents pane of the Transformer Help under Lists. Alternatively, AttributeExposer can be used.

When the ‘Load Keys as Attributes’ parameter is set to ‘Yes’, this parameter controls the attributes which are created. If it is set to ‘No’, each JSON object key will become an attribute and the corresponding JSON value will become the attribute value. If this parameter is set to ‘Yes’, only object values which are simple types (integers, strings, etc) will become attribute values, while nested objects and arrays will be recursively flattened.

If the ‘Load Keys as Attributes’ parameter is set to ‘Yes’, the ‘Prefix New Attributes With’ parameter may be used to provide a string with which to prefix the newly-created attributes. If the selected format is GeoJSON or ESRIJSON, the format-specific keys will not be added as attributes, but will instead be handled by the appropriate format parser.

Exposes any attributes so they can be used by other transformers. Type directly in the text box or click the browse button to display the editor and add attributes there.