Skip to content
Prev 16695 / 29559 Next

raster CRS changes on tis own

On Tue, 13 Nov 2012, Agustin Lobo wrote:

            
That is precisely why I asked you to provide another example of the 
problem. If the problem cannot be reproduced with other data on your 
system, then it is limited to your initial data set, or the specific code 
used when the unexpected behaviour occurred. If you can reproduce it for 
similar data sets, then it is your system. I did note that you are running 
rgdal 0.7-5, mine is 0.7-22 (the current CRAN version). In my case the 
crucial startup messages are:

Loaded GDAL runtime: GDAL 1.9.2, released 2012/10/08
Path to GDAL shared files: /usr/local/share/gdal
Loaded PROJ.4 runtime: Rel. 4.8.0, 6 March 2012, [PJ_VERSION: 480]
Path to PROJ.4 shared files: (autodetected)

but yours are unknown. I install GDAL and PROJ.4 from source; like you, I 
am on:

Platform: x86_64-unknown-linux-gnu (64-bit)
(you are: x86_64-pc-linux-gnu (64-bit))

My intuition is that the problem is a stale GDAL on your system, but from 
reading the GDAL tickets and NEWS logs, I can't see an update to the ENVI 
driver that might explain where the odd extra tags are coming from, so it 
might be something else, assuming it is your system and not an 
idiosyncracy of your handling that data set.

Roger