Delimited File

1. Considerations

• Geometry, Geography, and Binary data types are not supported for Delimited Files.

2. Load Metadata

Source	The source of your file. This can be local upload, Amazon S3, or Azure Blob Storage.
delimiter	The delimiter character, use U+#### syntax (e.g. U+0001) for unicode characters
textQualifier	The text qualifier character, e.g. " (which would be represented as "")
headerRowsToIgnore	The number of records from the top of the file to ignore before the data starts (includes column header). See note below for more on this parameter.
encoding	The encoding of the file, defaults to UTF8 if not specified, but also supports UTF8_BOM, ASCII, and UTF16
path	The path to the source file to load. To upload a local file, you must first insert a Parameter in the Info tab of the connection (ex: filepath). Then, you would reference that same value in this location (Ex: @Filepath). This will then trigger a File Upload option to import your delimited file.
Auth Type	This field defines the authentication type for your data sync. Cinchy supports "Access Key" and "IAM" role. When selecting "Access Key", you must provide the key and key secret. When selecting "IAM role", a new field will appear for you to paste in the role's Amazon Resource Name (ARN). You also must ensure that: The role must be configured to have at least read access to the source The Connections pods' role must have permission to assume the role specified in the data sync config Note: This field was added in Cinchy v5.6

If you use both useHeaderRecord="true" and HeaderRowsToIgnore = 1, two rows will be ignored. Refer to the below to ensure you are receiving the results you want: One row as headers: useHeaderRecord="true" and HeaderRowsToIgnore = 0

Two rows as headers: useHeaderRecord="true" and HeaderRowsToIgnore = 1 Three rows as headers: useHeaderRecord="true" and HeaderRowsToIgnore = 2

Image 1: Load the Metadata

2. Schema

Geometry, Geography, and Binary data types are not supported for Delimited Files.

1. Add in your applicable column(s) (Image 2). See the documentation here for further details on each column type.

Image 2: Schema

3. Filter

1. You may choose to use CQL to create a filter (Image 3). Review the documentation here for more on filters.

Image 3: Adding a Filter