Hexagon Geospatial
MENU

ERDAS IMAGINE

Discuss and share topics of interest using ERDAS IMAGINE the world’s leading geospatial data authoring system.
Showing results for 
Search instead for 
Do you mean 
Reply
Contributor
Posts: 25
Registered: ‎12-06-2017
Accepted Solution

AutoSync Questions I have here

I am going to work a lot of aerial photos I have on my external hard drive. They do not have georeferenced in them. It was scanned by a contractor and they were flown over one of the  National Forest area in Central Colorado, USA.

 

I  have several questions for you out there that I may have trouble with.

 

For the input I have them as a jpg but I export them to TIFF files.

For the Reference image I use the NAIP 2015 files that are in MrSID. They are really huge area and are covered in by county.

For the Z values, I have a DEM that are in  10 meters.

For the aerial photos  They are very old and are in black and white,

 

I have the instruction on how to perform them that I had from the training materials. I have been reading and research them. I still have not grasp about this.

 

So when I set them up and I have a question about the project properties, my question to you for the Geometric Model, which one would be correct for the  aerial photos ?

 

For the Reference image, do they need to be bigger area than the input image ?

 

how many tie points do you recommend for this ?

 

Do they need to have the same pixel size for both the input and Reference ?

 

Let me know if you have any question you might have.

 

                                                             

Highlighted
Staff
Posts: 210
Registered: ‎02-12-2016

Re: AutoSync Questions I have here

Hi Robert,

 

Have you reviewed the IMAGINE Online Help ‘AutoSync User Guide’? It addresses all of the topics that you are asking about.

Help > User Guides > AutoSync User Guide.

 

Geometric Properties

If the input is unrectified and the reference image is orthorectfied, you will want to use a 3D geometric model with an accurate DEM. Otherwise there may be issues with vertical terrain displacement. In your case using Direct Linear Transform would be an option.

 

Reference image area

Ideally the reference image should cover the area of interest from your input data.

 

Tie Points

There’s no hard number of tie points that is applied to every data source for every geometric model that I know of. There is a minimum number of tie points required based on the geometric model selection. Discussed in the ‘AutoSync User Guide’.

 

Pixel Size

Ideally the reference area pixel size should be the same or higher resolution than the input image. Too much variance (higher than a factor of 6) between input and reference resolution will have a negative impact on tie point generation.

 

Kind regards,

Jeff

Contributor
Posts: 25
Registered: ‎12-06-2017

Re: AutoSync Questions I have here

Thank you. Yes I have been reading all kind of information about AutoSync what it can do what it cannot do.

Staff
Posts: 210
Registered: ‎02-12-2016

Re: AutoSync Questions I have here

Hi Robert,

 

Your questions probably require a more in-depth discussion of your specific project requirements and data. Please open a Support Ticket.

 

Kind regards,

Jeff

Frequent Contributor
Posts: 153
Registered: ‎10-27-2015

Re: AutoSync Questions I have here

>I have been reading all kind of information about AutoSync what it can do what it cannot do.

 
In nutshell it measures control points automatically and that works better or worse depending how well datasets looks equal. Normally it measures them typically better than you expected. Rest is then just configuration and automation. It is a brilliant piece of software for certain tasks and if your project fits its scope it makes your life easier.
 
 
Contributor
Posts: 25
Registered: ‎12-06-2017

Re: AutoSync Questions I have here

Thank you for your time talking to me !

Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Service Request through our Support Portal.