X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 18 Apr 2014 10:10 AM by  anon
using in_memory for image processing workflows
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
18 Apr 2014 10:10 AM
    Hello -- I'm rather new to IDL so please, if this question is answered in some basic reference material, just point me towards it. I'm trying to set up a basic set of modis processing steps for hundreds of images. I just want to convert the hdfs (convert_modis_data), reproject to utm (envi_convert_file_map_projection), and reorder the bands (existing custom code). I'm wondering about best practices for batching multiple steps together, each of which will, by default, create a file output. It seems better to to run through each of these steps and only have one new file output. I'm not sure the best way to do this though. Is this making use of IN_MEMORY? If so, I wasn't allowed to use this flag for the envi_convert_file_map_projection call. Other suggestions? Any thoughts (or nudges towards useful existing resources) are much appreciated , Mike

    Deleted User



    New Member


    Posts:
    New Member


    --
    21 Apr 2014 02:02 AM
    Try MODIS Conversion Toolkit (MCTK) https://github.com/dawhite/MCTK/releases

    Deleted User



    New Member


    Posts:
    New Member


    --
    24 Apr 2014 11:28 AM
    Hi Alex -- I'm already using MCTK. In order to run a bunch of images, one uses the convert_modis_data procedure (which I am using successfully). This question was about using IN_MEMORY. Any best practices on that when an image processing workflow contains multiple steps? Thanks, Mike
    You are not authorized to post a reply.