Changes between Version 8 and Version 9 of GsocDSMGenerationToolForOSSIM


Ignore:
Timestamp:
Jun 6, 2014, 4:44:31 PM (10 years ago)
Author:
martidi
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GsocDSMGenerationToolForOSSIM

    v8 v9  
    2626'''Week 1:'''
    2727
    28 WHAT I GET DONE THIS WEEK::
     28WHAT I GET DONE THIS WEEK:
    2929
    3030I have prepared the wiki page (http://trac.osgeo.org/ossim/wiki/GSoC_2014) and the Git repository (https://github.com/martidi/OSSIM-GSoC-2014.git) for code hosting.
     
    5454'''Week 2:'''
    5555
    56 WHAT I GET DONE THIS WEEK::
     56WHAT I GET DONE THIS WEEK:
    5757
    5858I have created the Eclipse project for OSSIM to manage all the source code.
     
    8383
    8484
     85
     86
     87=== Weekly Report 3 (2014, June 06) ===
     88
     89'''Week 3:'''
     90
     91WHAT I GET DONE THIS WEEK:
     92
     93As a result of a discussion with mentors I have discarded the ossim-orthoigen tool as a reference for my ossim-epipolar app and turned towards ossim-chipper, a newer and clearer one.
     94
     95I have begun to write the ossim-epipolar app editing the ossimSrtmSupportData class, in order to compute the median height and the standard deviation of SRTM values, parameters that are required for the automatic generation of the quasi-epipolar images.
     96
     97I have upload the drafted ossim-epipolar app and the related code modified (ossimSrtmSupportData) on the repository (https://github.com/martidi/OSSIM-GSoC-2014).
     98
     99[[BR]]
     100WHAT I PLAN ON DOING NEXT WEEK:
     101
     102To solve the problem on which I am stuck.
     103
     104To continue working on epipolar images generation
     105
     106To assess the automatic Tie Points identification.
     107
     108To begin the implementation of the OpenCV SIFT procedure for automatic TPs generation
     109
     110To test and control implementation efficacy – discuss results with mentors.
     111
     112[[BR]]
     113SOMETHING ON WHICH I AM BLOCKED:
     114
     115I'm trying to use an ASCII DEM file as input for the elevation data, but I have had some issues with it.