Forum

Author Topic: Pre-processing workflow for spliting up +10000 images for Aerial Imagery?  (Read 8981 times)

tforward2

  • Newbie
  • *
  • Posts: 17
    • View Profile
I have a project area of 21 km by 13 km (13 miles x 8 miles) with about +10000 images covering the area. I need to produce a DEM and Orthophoto for the area. I cannot pass +10000 images to AgiSoft at once to process as will just run out of memory, so we have been manually splitting up the images into smaller 100-150 images chunks and then processing them. This is obviously a time consuming process and we want to ramp up are aerial imagery collection in the Spring. Does anyone have an automated workflow for pre-processing large aerial imagery into smaller workable chunks?

r0xx

  • Jr. Member
  • **
  • Posts: 73
    • View Profile
Re: Pre-processing workflow for spliting up +10000 images for Aerial Imagery?
« Reply #1 on: November 26, 2014, 12:45:27 PM »
Would be interested in something like this too!

flomoa

  • Newbie
  • *
  • Posts: 7
    • View Profile
Re: Pre-processing workflow for spliting up +10000 images for Aerial Imagery?
« Reply #2 on: December 03, 2014, 12:24:27 PM »
Me too ...

kovar

  • Newbie
  • *
  • Posts: 1
    • View Profile
Re: Pre-processing workflow for spliting up +10000 images for Aerial Imagery?
« Reply #3 on: December 29, 2014, 06:24:05 PM »
Greetings,

What are the selection criteria you are using to split them up? If you are doing it by area, I suspect you could read the EXIF data, find all the images within n meters of a specific point, and copy those to a folder. Iterate through your entire area.

I am brand new to PhotoScan and need to look at their API to figure out the next steps....

-David

tforward2

  • Newbie
  • *
  • Posts: 17
    • View Profile
Re: Pre-processing workflow for spliting up +10000 images for Aerial Imagery?
« Reply #4 on: December 30, 2014, 09:29:53 PM »
I ended up building my own solution to this problem.

In short:

- Read EXIF X, Y data from all images
- Project Points to UTM
- Determine best size for chucks (this is more complicated then it sounds, took some trial and error to find something that works mostly used Arcpy tools for doing this)
- Build a JSON file that has the list of chucks and path to the image. (I did not want to move the images to a seperate dir as the copy/paste operation would take along time. Instead I just leave the images where they are but in Agisoft break into smaller chucks by importing the JSON file that tell the program how to chuck the data.)