QueryResult
Bounding box of the search area as integer indexes or model aligned coordinates. If not provided, this is set to the entire block model.
If using integer indexes, they must be >= zero and <= the number of blocks - 1.
For example, if a block model has:
n_blocks: { nx: 10, ny: 10, nz: 10 }
then i_max, j_max, and k_max must all be >= 0 and <= 9.
If using model aligned coordinates, that is, rotated by the same scheme as the block model, centroids that are
encapsulated by the bounding box will be selected. A side effect of this behaviour is a bounding box with x, y, z
min-max can exceed the model along any axis.
Minimum and maximum values for the i column in the file
Maximum value for the column
Minimum value for the column
Minimum and maximum values for the j column in the file
Maximum value for the column
Minimum value for the column
Minimum and maximum values for the k column in the file
Maximum value for the column
Minimum value for the column
Minimum and maximum values for the x column in the file
Maximum value for the column
Minimum value for the column
Minimum and maximum values for the y column in the file
Maximum value for the column
Minimum value for the column
Minimum and maximum values for the z column in the file
Maximum value for the column
Minimum value for the column
Example: "e3c277c2-edc6-4a7a-8380-251dd19231f2"
ID of the block model
List of columns, in addition to the "geometry" columns, that will be included in the output file.
The columns field supports selecting columns by either their title or ID, and can also include a wildcard ("*") placeholder, which will expand to all user columns, ordered alphabetically by title in a case-insensitive manner.
Please note that the wildcard does not cover the system column version_id. To include version_id in the output file, it must also be explicitly specified in the columns field alongside the wildcard.
The order of columns in the output file will match the order in the columns field. Columns that are part of the initial "geometry" columns will be ignored if specified.
Pollable job URL for this query
List of columns, in addition to the "geometry" columns, that will be included in the output file.
The columns field supports selecting columns by either their title or ID, and can also include a wildcard ("*") placeholder, which will expand to all user columns, ordered alphabetically by title in a case-insensitive manner.
Please note that the wildcard does not cover the system column version_id. To include version_id in the output file, it must also be explicitly specified in the columns field alongside the wildcard.
The order of columns in the output file will match the order in the columns field. Columns that are part of the initial "geometry" columns will be ignored if specified.
Example: "618d6339-2fa7-4dfd-9c7f-c0b12016639e"
The ID of the column, a UUID for non-system columns
Capitalized list of supported PyArrow datatypes outlined in https://arrow.apache.org/docs/python/api/datatypes.html.
Timestamp datatype is expected to be used with unit measured in "us" and timezone set to "UTC" inside of parquet column header schema or it won't be accepted; an example for PyArrow binding would look like this: pa.timestamp("us", tz="UTC")
The human-readable label used to identify the column
The ID of the column's unit
Example: 5
Identifier for the version within a block model as a monotonically increasing integer, where 1 is
the version_id for the version created upon creation of the block model.
Example: "3e9ce8de-f6ba-4920-8c6e-0882e90f0ed7"
A universally unique identifier for the version
