Recent Changes

Differences

This shows you the differences between two versions of the page.

--- dev:desktop_ext:image_pixel_objects [2021/04/26 07:46]
paulien [Results]
+++ dev:desktop_ext:image_pixel_objects [2021/04/26 11:58]
paulien removed
@@ Line 1: / Line 1: @@
-====== Image Annotation to Object ======
+====== Image Annotations to Objects ======
-This page describes how to use the extension "Image Annotation to Object"\\
+This page describes how to use the extension "Image Annotations to Objects"\\
-{{orbit_desktop:how_to_find.png?25&nolink  |}} [[dev:desktop:workspace:main_toolbar|Main Toolbar]] > Extensions > Image Annotation to Object
+{{orbit_desktop:how_to_find.png?25&nolink  |}} [[dev:desktop:workspace:main_toolbar|Main Toolbar]] > Extensions > Image Annotations to Objects
-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.\\
+The "Image Annotations to Objects" 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.\\
@@ Line 13: / Line 13: @@
 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.
+Every annotation (and optionally the tag) can be overlayed on the opened image.
@@ Line 28: / Line 28: @@
 Every annotation is defined by 4 pixel coordinates that form the bounds of the rectangle: MinX, MaxX, MinY and MaxY.
-Optional
+The center of the bounds can be used to convert to 3D. The same algorithm as for pixel coordinates will be used.
+==== Display Annotations ====
+The original image annotations and tags can be displayed on the imagery via the [[dev:desktop:preferences:mapping|]].
 ===== Reference Files =====
 Choose how the reference files are structured:
 ==== One file for every image ====
-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.
+There is one csv or xml file in the original or processed folder that is linked to an image via equal filenames.
+Example of csv file.
 <code>
-    Element=
+Filename	PixelMinX	PixelMinY	PixelMaxX	PixelMaxY	PhotoName	Tags
-    Filename=
+DSC02497	6366	4079	6973	4621	DSC02497.jpg	corrosion,structural_steel,light
-    PixelX=
-    PixelY=
-    PixelMinX=
-    PixelMaxX=
-    PixelMinY=
-    PixelMaxY=
-    Tags=
-    Attribute0=
-    Attribute1=
-    ...
 </code>
-==== One file for all images ====
+Example of xml file.
-There is one csv or xml file to be selected in which all annotation are described.
+<code>
+<?xml version="1.0" ?>
+<annotation>
+	<folder></folder>
+	<filename>DSC02490.JPG</filename>
+	<object>
+		<tags>corrosion,structural_steel,light</tags>
+		<comment></comment>
+		<bound>
+			<xmin>1541</xmin>
+			<xmax>2008</xmax>
+			<ymin>4257</ymin>
+			<ymax>4555</ymax>
+		</bound>
+	</object>
+</annotation>
-===== Target =====
-After selecting the target file location and CRS, choose to create 3D point objects or boxes.
+</code>
-The result is an ovf with the
+Example of the image_pixel.ini file to describe the xml tags.
+<code>
+Element=object
+Filename=filename
+PixelX=
+PixelY=
+PixelMinX=bound/xmin
+PixelMaxX=bound/xmax
+PixelMinY=bound/ymin
+PixelMaxY=bound/ymax
+Tags=tags
+Attribute0=folder
+Attribute1=comment
+...
+</code>
-The pixels_not_converted.txt contains the list of objects that couldn't be converted.
+==== One file for all images ====
+There is one csv or xml file to be selected in which all annotations are described. The same structure as for one file for one image can be used.
+===== Target =====
+After selecting the target file location and CRS, choose to create 3D point objects or boxes.
+===== Algorithms =====
-===== Advanced Parameters =====
+For every situation, slices are created along the vector line between the camera position and the pixel point.
-Depending on the chosen source and target options, the used parameters will be enabled.
 ==== 3D Coordinates from Pixel Coordinates ====
-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.
+Within a radius around the vector, points are detected and clustered to create the 3D coordinate.
 ==== 3D Coordinates fom Pixel Bounds ====
-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.
+Within the pixel coordinate bounds around the vector, voxels are created and clustered to create the 3D coordinate.
 ==== 3D Boxes from Pixel Coordinates ====
+With a radius around the vector, points are detected and clustered to create the 3D box.
 If objects on ground, use ground margin.
@@ Line 87: / Line 113: @@
 ==== 3D Boxes from Pixel Bounds ====
+Withing the pixel coordinate bounds around the vector, voxels are created and clustered to create the 3D box.
 If objects on ground, use ground margin.
+===== Advanced Parameters =====
+Depending on the chosen source and target options, the used parameters will be enabled.
 ==== Search Slice Thickness ====
 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 Coordinates: If an object is detected in a slice, 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.
+  *For creating 3D Boxes: If an object is detected in a slice, do search in the following slices up until the Search Dist Max is reached.
 ==== Search Dist Max ====
@@ Line 104: / Line 139: @@
 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.
 ==== Cluster Pts Min ====
@@ Line 122: / Line 153: @@
 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.
 ==== Voxel Size ====
-The box is divided into voxels of this size.
+The box in the slice is divided into voxels of this size.
 ==== Voxel Pts Min ====
@@ Line 136: / Line 165: @@
 ===== Results =====
-The result is an ovf with the attributes from the image_pixel.ini file. The following attributes are extra:
+The result is an ovf where every object corresponds to one annotation, having the attributes from the image_pixel.ini file or csv file. The following attributes are extra:
-  * FD_ImageAnnotationSequence: Is to indicate the sequence of annotation on the same image.
+  * FD_ImageAnnotationSequence: Used 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 [[dev:desktop:preferences:mapping|]].