BLACKMORE / TECHNOLOGY PORTFOLIO

BSIE spatial computing engine

BSIE is BTG’s spatial intelligence foundation for geospatial and augmented-reality applications, with work that must be tested against actual terrain, sensors, offline datasets and device limits.

Blackmore Technology Group approved emblem

Spatial inputs and outputs

The BSIE research programme addresses terrain, locations, visibility and geospatial relationships required by field applications. Depending on the deployment, inputs can involve elevation models, position and heading sensors, paths, water and legal or safety datasets. Output may be a 2D map, world-aligned AR overlay, terrain intersection or a bounded spatial interpretation.

Offline and device operation

Field software needs to account for GPS uncertainty, stale packs, unavailable networks, sensor drift, orientation and the distinction between map geometry and observed camera views. An attractive visual overlay is not independent proof that a predicted location is correct on the ground.

Applications with distinct safety requirements

HuntAR focuses on authorized hunting field use and local conditions; SearchAR addresses controlled rescue-related shared context; HikeAR serves hiking and trail awareness; ShowAR represents the broader visualization programme. Each requires its own user journey, governing rules, supported datasets and qualification criteria.

Accuracy, validation and limits

Spatial evidence needs coordinate reference definitions, source versions, device and OS identity, orientation, measured location error and representative terrain conditions. A passing synthetic intersection or device build does not establish every overlay, legal boundary or rescue decision as independently verified.

High-consequence field and emergency use must preserve human judgment and relevant professional requirements.

Rights and data provenance

Base maps, elevation packs, trails and public-safety datasets carry source licensing, currency and confidentiality obligations. Bridge-style source authorization and ENTITY provenance can help maintain their permitted use, but neither component overrides a source provider’s terms.