Binary File
This page describes how to use a binary file as a data source in Connections.
- Binary File does not support Geomtry or Geography data types.
To connect a Binary File as a Data Source, fill in the following parameters (image 1):
Parameter | Value |
Source | The location of the source file. Either a Local upload, Amazon S3, or Azure Blob Storage
The following authentication methods are supported per source:
Amazon S3: Access Key ID/Secret Access Key
Azure Blob Storage: Connection String |
Header Lines to Ignore | The number of records from the top of the file to ignore before the data starts (includes column header). |
Footer Lines to Ignore | The number of records from the bottom of the file to ignore |
Encoding | The encoding of the file. This default to UTF8, however also supports: UTF8_BOM, UTF16, ASCII. |
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 file. |

Image 1: Binary File parameters
Geometry and geography data types are not supported for binary files.
- 1.Add in your applicable columns (Image 2). Review the documentation here for information on the column types available.
- 2.Binary File sources have a unique parameter for Standard Columns:
- 1.Parse Content By - Choose from the following three options to define how you want to parse your content:
- Byte Length - The content length in number of bytes
- Trailing Byte Sequence - the trailing sequence in base64 that indicates the end of the field
- Succeeding Byte Sequence - the trailing sequence in base64 that indicates the start of the next field, and thus the end of this one.

Image 2: Schema Columns
Adding a filter section allows you to enter a CQL filter statement for your results (Image 3). See here for more information on adding a Filter.

Image 3: Adding a Filter Section
Last modified 8d ago