JSON

This is a reference documentation of the JSON reader in hale studio. Usually you will not need this reference, as in hale studio the configuration of I/O providers is done via the respective wizards for import and export. Where this reference can come in handy is if you want launch a transformation via the command line.

Configuration parameters

Following are the specific configuration parameters for this reader.

• Read mode

  Mode for reading Json structure

  Setting name	mode
  Example value	singleObject
  	When the source file is only a single object at its root, use this mode
  Default value	auto
  	Load objects from a Json array or a GeoJson FeatureCollection

• Force default type

  Always use default type for all objects read

  Setting name	forceDefaultType
  Example value	true
  	Use the configured default type for all instances read
  Default value	false
  	By default allow other mechanism to determine an instance type

• Default type

  Name of the default type to use for read Json objects

  Setting name	defaultType

The following configuration parameters are shared for all instance readers.

• Default SRS

  For cases where the spatial reference system cannot be detected from the data you can specify a default SRS to assume for these geometries. The SRS can be provided as code (with prefix code: ) or as WKT (with prefix wkt: )

  Setting name	defaultSrs
  Example value	code:EPSG:25832

The following configuration parameters are shared for all I/O providers.

• Content type

  During import the content type is tried to be auto-detected, for export this is not possible, but I/O providers may have a default content type associated. If an I/O provider only supports one content type, it's usually not necessary to set this parameter. In any case you can override the content type to use/assume using a content type identifier (see the list of supported content types at the bottom of the page).

  Setting name	contentType
  Example value	eu.esdihumboldt.hale.io.json

• Character encoding

  Specifying a character encoding is important especially for the import, so data is interpreted correctly. Not every I/O provider may respect this setting though (e.g. if the encoding is given by the data source).
  Specify a character encoding by its name as recognised by Java.

  Setting name	charset
  Example value	UTF-8

Supported content types

• JSON File (eu.esdihumboldt.hale.io.json)
• GZiped JSON File (eu.esdihumboldt.hale.io.json.gzip)