Search Results

This section describes the API used to submit material changes to the tracking layer. In general, the API will use a POST REST call that involves: An event type, which can be UPDATE, SIM_START or SIM_END An entity Id to identify which material tracking la...

The REST interface allows to retrieve voxel sagas. The interface returns sagas in singularities and in space. Method GET URL <server>/entity.ashx Parameters To retrieve the contents of a singularity, use the following parameters: project ...

The material tracking layer entity is initialized in the same fashion as other processed entities in the platform. These steps are described in this topic in a general way: Triggering Jobs It is also possible to update an existing material tracking layer...

The Material Tracking information can be retrieved from the system using the C# client library. The information stored by the Material Tracking Layer can be used equally to produce visualizations and to compute reports. In both cases, the functioning principl...

A Material Operation Table is a CSV file, where each row contains a material tracking operation. The first line of the file must contain comma-separated header identifiers. The system will look for the following reserved headers (case sensitive): T...

The Material Tracking Layer builds entropy as it operates, following the direction of time. That is, the outcome of a particular event may depend on events that happened before. For this reason, out of order events are not permitted and any conflicting spatial...

Creating a View for your project. The WebUI provides two different ways to start the creation of a View... More  options for View

A heightmap entity is a special type of Ortho-Imagery set where images describe altitude instead of color. The images for these sets must be in 16bit grayscale PNG format. Once you select “Heightmap” from the “Add” menu, you will see the following options:  ...