10-23-2017 01:07 AM
I am facing an issue with ERDAS Imagine 2015.x, while importing ASTER L1A data bands 3N/3B describes below-
Issue: Using ERDAS Imagine 2015.x for importing data ASTER L1A, bands 3N and 3B and futher used as inputs in Imagine photogrammetry. while adding ASTER 3N/3B orbital, it provides metadata error.
Again i tried using same ASTER L1A data for importing 3N/3B in ERDAS imagine 2014 and 2016 version, bands 3N/3B are opening correctly in Imagine Photogrammetry 2014, 2015 and 2016 version.
Kindly provide any solution of this issue.
Thanks and Regards,
Solved! Go to Solution.
11-02-2017 09:57 AM
The problem you reported is a known issue in ERDAS IMAGINE 2015. It was fixed in ERDAS IMAGINE 2016 v16.1.
Hexagon Geospatial Support
04-17-2019 12:58 PM
I am having an issue when attempting to load ASTER data into the photogrammetry application using Imagine 2018 where it will not recognize the .hdf file, says the file "is not an appropriate file for this type of sensor model" Any suggestions?
04-17-2019 01:34 PM - edited 04-17-2019 01:35 PM
You can not directly use the hdf format as an input image in IMAGINE Photogrammetry. First import the two bands separately using the ASTER EOS HDF format importer and then add them as input images in your photogrammetry project.
Best regards, Sam
04-17-2019 02:01 PM
04-19-2019 02:03 PM
Have you selected Orbital Pushbroom/ASTER geometric model? It accepts .img format ASTER image. Here are some screencaptures.