Note:
At ArcGIS Enterprise 10.9.1 or higher it is recommended that you add or edit big data file shares through your portal contents page instead of ArcGIS Server Manager. Learn more about adding big data file shares in the portal.
Big data file shares are registered as a data store through your portal contents page. Big data file shares require a manifest to outline the schema of the data, as well as the fields that represent geometry and time in the dataset. The manifest is automatically generated when you register a big data file share, but you may need to make modifications if there are any changes to your data, or if the manifest generation was unable to determine all the information needed (for example, if the automatically generated manifest did not select the correct field for the geometry or time).
Note:
Editing your big data file share through the manifest is an advanced option. To learn more about applying changes to individual datasets in your big data file share, see Manage big data file shares in portal. To learn about applying a hints file for delimited files, see Hints file.
The manifest is composed of datasets. The number of datasets depends on the number of folders your big data file share contains. In the following example, there are five datasets:
"datasets":[
{.. dataset1 ..},
{.. dataset2 ..},
{.. dataset3 ..},
{.. dataset4 ..},
{.. dataset5 ..},
]
Within each dataset, there are five top-level objects that may be applicable. Of these objects, name, format, and schema are required.
{
"name": "dataset1",
"format": {},
"schema": {},
"geometry": {},
"time": {}
}
Name
The name object is required and defines the name of the dataset. This must be unique within the manifest.
Format
The format object is required and defines the dataset type and its format.
Syntax | Example |
---|---|
| Example using a shapefile:
Example using a delimited file:
|
Description | |
|
Schema
The schema object is required; it defines the dataset fields and field type.
Syntax | Example |
---|---|
|
|
Description | |
Note:When big data file shares are analyzed through GeoAnalytics Toolss and saved as a feature service, the types might change. For example, an esriFieldTypeBigInteger in a big data file share will become a esriFieldTypeDouble field in a feature service. |
Geometry
The geometry object is optional. It's required if a dataset has a spatial representation, such as a point, polyline, or polygon.
Syntax | Example |
---|---|
| Example using a delimited file with x- and y-values:
Example using a delimited file with x-, y-, and z-values:
Example using a .tsv file:
|
Description | |
Note:Since the geometry object is optional, the following properties are listed as required or optional, assuming that a geometry is used:
|
Time
The time object is optional. It is required if a dataset has a temporal representation.
Syntax | Example |
---|---|
| Example using an instant, with multiple formats in the time fields:
Example using an interval, with multiple fields used for startTime:
|
Description | |
Note:Since the time object is optional, the following properties are listed as required or optional, assuming that time is used:
|