codeName already exists.
If the dataset already exists, Tilebox applies the same schema update rules as a direct update. New fields can be added to non-empty datasets. Breaking schema changes are only allowed for empty datasets.
New queryable fields and changes to an existing field’s queryable annotation are also only allowed for empty datasets.
Parameters
Options
Dataset kinds
Field types
Field options
Optional. Set the RFC 6901 path to this field in the source JSON, such as
/properties/eo:cloud_cover. This is useful
when transforming datapoints to JSON because Tilebox can reconstruct nested source objects from flattened dataset
fields.Make a non-repeated
String, Bool, Int32, Int64, Uint64, or Float64 field available for server-side custom
field filters. A dataset can contain at most two queryable string fields.Optional. Set a JSON Schema reference URI or URI fragment for the field. Use this when the field follows a well-known
schema, such as a STAC extension. Tilebox emits the reference as
$ref when advertising the field in STAC queryables.Set semantic display roles for the field. The only currently supported role is
field.RolePrimaryTitle.