Image Annotation to Object

This page describes how to use the extension “Image Annotation to Object”

Main Toolbar > Extensions > Image Annotation to Object

The “Image Annotation to Object” extension makes it possible to convert image annotations defined with pixel coordinates or pixel bounds into 3D coordinates or 3D boxes using the pointcloud resource.

Image annotations for mapping run imagery can be defined with two pixel coordinates or pixel bounds defined by four pixel coordinates. The image pixels are converted into 3D coordinates or 3D boxes using the mapping run pointcloud and original/optimized images.

The image_pixel.ini file describes the tags in the annotation file used for the conversion. Every annotation can have a tag to overlay on the opened image.

Select how the annotations are defined.

Every annotation is defined by 1 coordinate having two pixel coordinates: X and Y.

Every annotation is defined by 4 pixel coordinates that form the bounds of the rectangle: MinX, MaxX, MinY and MaxY.

Optional

Choose how the reference files are structured:

There is one csv or xml file in the original or processed folder that is linked to an image via equal filenames. The image_pixel.ini file describes the xml tags to be used for conversion.

    Element=
    Filename=
    PixelX=
    PixelY=
    PixelMinX=
    PixelMaxX=
    PixelMinY=
    PixelMaxY=
    Tags=
    Attribute0=
    Attribute1=
    ...    

There is one csv or xml file to be selected in which all annotation are described.

After selecting the target file location and CRS, choose to create 3D point objects or boxes.

The result is an ovf with the

The pixels_not_converted.txt contains the list of objects that couldn't be converted.

Depending on the chosen source and target options, the used parameters will be enabled.

Slices are created along the vector line between the camera position and the pixel point. Within a radius around the vector, points are detected and clustered to create the 3D coordinate.

Slices are created along the vector line between the camera position and the pixel point. Within the pixel coordinate bounds around the vector, voxels are created and clustered to create the 3D coordinate.

If objects on ground, use ground margin.

If objects on ground, use ground margin.

The thickness of the slices created from camera position to pixel point to search for points.

• For creating 3D Coordinates: If a slice has an object, don't search in the following slices.
  
• For creating 3D Boxes: Do search in the following slices up until the Search Dist Max is reached.

The maximum distance from the camera to create slices and detect points.

The radius around the vector between the camera position and pixel point to search for cluster points within a slice. Minimum cluster gap size.

This value counts also as the cluster distance which is the minimum cluster gap size.

The minimum number of points to have a cluster. For less dense point clouds, decrease this parameter.

The search radius around the direction camera to pixel position to search for the 3D object.

The ground margin used to identify a 3D box reached the ground to be able to end the clustering. To be used if the object to identify is located on the ground. If you don't remove the ground, the object will become bigger. For bins, hyrdants

Use to create boxes for objects on the ground.

The box is divided into voxels of this size.

Nearby voxels that have the minimum number of points will be clustered into an object.

The result is an ovf with the attributes from the image_pixel.ini file. The following attributes are extra:

• FD_ImageAnnotationSequence: Is to indicate the sequence of annotation on the same image.
• FD_PixelDistanceFromAnnotation: The distance to the pixel coordinate or the center of the pixel bounds, expressed in pixels.
• FD_InsideAnnotationBounds: The value can be zero/false or one/true. True means that the display of the created object is still within the bounds of the original annotation. False means that the display of the created object is outside the bounds of the original annotation. For pixel coordinate definition always false/zero.

The pixels_not_converted.txt contains the list of objects that couldn't be converted. The image objects and tags can be displayed on the imagery via the Preferences of Mapping.