Data Types
The CPF supports common data types that can be used for batch job parameters, structured data parameters, and result fields for a business application. The CPF does not support custom data types or Enums, these must be converted to/from one of the standard data types by the business application.
If the File Format supports the data type then the value must be encoded according to that file format.
Otherwise the values must be converted to a string representation using the following rules.
- UTF-8 or US-ASCII encoding must be used for strings and text files.
- Numbers will use the sign (-) prefix for negative numbers, the digits (0-9) for the integer portion, a period (‘.’) for decimal numbers, and the digits (0-9) for the fractional part. For example -1234.56789.
- Booleans use the values true and false.
- Geometries can be encoded using OGC Well-Known Text (WKT) or PostGIS Extended-WKT (EWKT). For example SRID=4326;POINT(-124 50).
Internally the CPF converts all values to the string encoded form.
The table below shows the supported data types.
| Data Type | Description |
|---|---|
| boolean | true or false. |
| byte | 8-bit signed number. |
| short | 16-bit signed number. |
| int | 32-bit signed number. |
| long | 64-bit signed number. |
| float | 32-bit IEEE 754 floating point number. |
| double | 64-bit IEEE 754 floating point number. |
| String | A character string. |
| Date | A Date in the format yyyy-MM-dd. |
| DateTime | A Date with millisecond precision time in the format yyyy-MM-dd HH:mm:ss.SSS format. |
| DateTime | A Date with nanosecond precision time in the format yyyy-MM-dd HH:mm:ss.SSSSSSSSS format. |
| URL | A URL or the string encoding of a URL. |
| Point | A Point geometry. |
| LineString | A LineString geometry. |
| Polygon | A Polygon geometry. |
| MultiPoint | A MultiPoint geometry. |
| MultiLineString | A MultiLineString geometry. |
| MultiPolygon | A MultiPolygon geometry. |