| Getting Started | The Gocator Development Kit (GDK) provides a complete framework for the development, testing and deployment of custom Gocator firmware |
| Build System | The build system utilizes a solution generator, which generates the project files for different build environments within one solution, as well as a per-project build script which compiles your project for all supported architectures |
| API Limitations | Due to the system architecture used for the GDK, there are some limitations in the API a developer has access to |
| ▼Tool Development | Using the GDK, a developer can create custom tools that integrate seamlessly into the sensor |
| Life Cycle | The GDK framework constructs an instance of the associated tool class for each tool defined in the sensor job file or for each tool added using the Gocator UI or SDK |
| Tool Definition | A custom tool is represented by a class deriving from the base class GdkTool |
| Configuration | Tools can contain user-defined parameters, inputs and outputs which are described in the VDescribe method |
| Data Processing | While the sensor is running, the VProcess method is called whenever there is a scan of data ready to be used |
| Geometric Feature Outputs | Geometric features can be defined within a tool to be sent as outputs to other tools |
| Data and Generic Outputs | A tool can also output data such as profiles, surfaces, as well as generic data that can then be selected as stream inputs for other tools |
| Memory Management | Proper attention should be paid to memory management because it is critical to the reliable operation of the sensor |
| ▼Experimental Features | This section describes experimental features |
| Multi-Reference Frame Support | Multi-reference frame support allows a tool to transform data represented in different reference frames into a common one, so that meaning results can be produced |
