| 05 Jun 2012 11:58 AM |
|
|
I am opening a geotiff file in ENVI and everything looks fine - except for it being off > 1km, which is a lot when working with 4m data... The data opens correctly in ArcGIS. I am checking it against Google Earth, using an easily recognizable feature, and the coordinates for the feature are approximately the same as in Google Earth when opening the geotiff file in ArcGIS, but quite a bit off when opening it in ENVI. Probably one way around would be to use ArcGIS for all processing, but I am more familiar with ENVI and therefore would like to use ENVI for some processing steps. I am running ENVI 4.7 SP2. Anybody else encountered this problem? Please help.
|
|
|
|
MariM
Veteran Member
Posts:2396  
| 05 Jun 2012 12:55 PM |
|
|
What projection/datum does ENVI show? It may be that the image has a datum not natively recognized in ENVI that is recognized in ArcGIS. I would compare the projection/datum information between the two. You may need to add a custom datum in ENVI and the best way to get advice on how to do this would be to contact Technical Support directly. Additionally,full ESRI projection support was added in ENVI 5 so perhaps updating to the latest version would help.
|
|
|
|
Deleted User
New Member
Posts:7 
| 05 Jun 2012 01:49 PM |
|
|
Thanks for the reply. Of course I did a comparison of the information in ArcGIS and ENVI before I even posted here, and yes, they show the same projection/datum (geographic and WGS 1984). This is a pretty standard datum. Good to hear that ENVI 5 has full ESRI projection support. I'll have a new computer soon, will update then.
|
|
|
|
Deleted User
New Member
Posts:7
| 05 Jun 2012 02:01 PM |
|
|
Whatever the problem is - I haven't resolved it yet - it would be good if ENVI would show at least a warning if it encounters a file and doesn't know the datum, instead of displaying it as if it were good. A few km off are much more of a problem than 30 degrees off, because it goes unnoticed so easily, and someone will do his whole analysis and then compare to another dataset and it doesn't overlay correctly! So please, take a note of this issue...
|
|
|
|