Shapefile

This is a reference documentation of the Shapefile 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.

• Type name

  The name of the schema type the loaded instances should be associated to. Will be auto-detected if not provided.

  Setting name	typename
  Example value	{namespace}localname
  	The type name is represented like in the given example, with the namespace in curly braces.

• Match short property names

  Match property names in Shapefile to target type properties by checking if there is exactly one target type property name that starts with the Shapefile property name. If there are multiple property names in the target type that start with the Shapefile property name, the property will not be imported.

  Setting name	matchShortPropertyNames
  Example value	true
  	Activate the matching of short property names
  Default value	false
  	By default a source property will only be imported if there is an exact match to a target type property

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.shp

• 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

• Shapefile (eu.esdihumboldt.hale.io.shp)