Changes between Version 4 and Version 5 of Correlator

Timestamp:

May 5, 2012, 11:17:23 AM (12 years ago)

Author:

warmerdam

Comment:

Minor formatting.

Correlator

@@ -1 @@
-'''Correlator in GDAL'''
+= Correlator in GDAL =
 
-'''Short description'''
+== Short description ==
 
 Producing a single seamless mosaic from single frames (remote sensing data from aircrafts and UAVs)
 
-'''Introduction'''
+== Introduction ==
 
 Today gathering of a large number of remote sensing data from aircrafts and UAVs is carried out. In most cases data contains single frames, so there is a task to create single seamless mosaic from several mutually overlapping images by finding tie points (“feature points”) and optimal correct transformations. Due to lots of photos, which should be processed, we need to have fast, robust, convenient and simple tool for handling images in automatic mode without close human participation. At present, GDAL doesn’t have such algorithm and even more there isn’t suitable specific third-party applications. Many geospatial open source projects use GDAL, such as Quantum GIS and GRASS, so existing a tool for stitching photos in GDAL can be useful and irreplaceable for images processing in the all dependant programs, can make usage of these software easier, more general and comprehensive.
 
-'''Main idea'''
+== Main idea ==
 
 I propose to implement in GDAL correlator, which will carry out process of creation mosaic and simple geographical orientation using telemetry. According to my investigations, I’ll compare one of existing methods and my idea.
@@ -31 +31 @@
     6. Apply transformations which we got at previous step. For ultimate mosaic we use GDAL images merge algorithm to fuse all images in one (requires images in one coordinate system). 
 
-'''Plan && Timeline'''
+== Plan & Timeline ==
 
     1. Check and test all necessary methods/functions from OpenCV and GDAL for correlator implementation (20-25 days). At this moment, I should be able to have all necessary knowledge about transformations, image processing, according algorithms and able to develop my code.
@@ -42 +42 @@
     8. Test the whole implementation. (1-2 days)
 
-'''Future ideas'''
+== Future ideas ==
 
 Make acceptable to handle raw photos without telemetry and any additional data. I think that is quite possible because in my first research I didn’t rely on additional information about relief, GPS and camera parameters and tried to make universal algorithm. Maybe implement another optimization method instead of gradient descent.