
Strayos Block Model
Usage Instructions
The Block Model CSV is expected to be a plain
CSV file without any metadata in the CSV. The text content should be tabular
information of all the blocks. The very 1st row in the CSV is expected to be
the Header row which the following mandatory columns
Block Center
X
Block Center
Y
Block Center
Z
Block Size X
Block size Y
Block Size Z
Block Unique
ID
NOTE: It's not necessary for the column
headers to follow the exact name mentioned above. You will be given an option
to select the column headers in the UI
Valid Block Model conditions
& checks
Block-Model boundary intersection
The boundary (bounding box) of block-model
should intersect with the boundary of the terrain of the current dataset
This is calculated by using the Block Model
CRS provided during upload, calculating the boundary of block-model using the
CRS, intersecting
Block-Model Unique ID
The values of the “Block Unique ID” column
should all be unique
Block Model Split Polygon
Split polygon inside Block-Model
The Block-model split polygon is expected to
be drawn within the boundary of the full block-model. If the split-polygon is
drawn outside of the full block-model, it will result in an incompatible split
polygon
Too small Split Polygon
If the split polygon is too narrow, it may not
always include the blocks from the block-model. This is because the algorithm
checks if the block-center is inside the polygon. If not then the block is
ignored for the polygon. So if the split-polygno is too narrow and the
dimensions of the blocks in the block-model are too big, then its possible for
the polygon not include any blocks

Too large Split polygon
● The split polygon is currently
limited to an area of 200,000 sq.m.
● Additionally the app only supports
loading 500,000 blocks at a single time. So if any of the polygons has a block
count of more than 500,000, it is automatically ignored with a notification.
Multiple Block Model variations
A block-model is considered as an asset of the
site (NOT dataset). So it is possible for you to upload multiple block-models
with similar naming with mild modifications. Strayos allows this flexibility so
that you can upload multiple block-models with new scans or updated
information.
But this also creates confusion while drawing
split polygons, because the boundary of the block-model variations may not
always be the same, and its currently not actively known.
For example, if you have a block-model with 1
mill rows and you create a copy of it with 100,000 blocks for testing and
upload it. The upload will be successful, but the split polygon may not always
have a block inside it.
So it is essential to know the extents of the
block-model while drawing the split polygon.
Example
The Green polygon is drawn for the 1st
block-model, the red polygon is drawn for the 2nd block-model.
The 1st block-model is a smaller version of
the 2nd. And the 1st block-model doesn't have any blocks in the area drawn, so
the polygon is invalid and doesn't have any blocks, whereas the red polygon
does.
