[gdal-dev] gdal_translate segfault with large netCDF

2011-04-19 Thread Josh.Vote
Hi, I'm new to GDAL so please forgive any glaring ignorance :) Currently I have an 8GB ER Mapper (ERS) dataset that I want to convert to a NetCDF file with gdal_translate which always results in a segfault when using the following command. gdal_translate -of netCDF input.ers output.nc Whereas

RE: [gdal-dev] gdal_translate segfault with large netCDF

2011-04-19 Thread Josh.Vote
Thanks for the suggestions - > I would like to suggest that you do a gdal_translate from a subset of the > ERS file at the bottom right corner of the source just to ensure that it > isn't a problem with reading past the 4GB mark in the ERS file. I just managed to run 'gdal_translate -of netCDF -s

[gdal-dev] GDAL build problems under Linux debian x86_64

2011-05-16 Thread Josh.Vote
Hi, I'm currently trying to build gdal trunk (rev 22377) on an amd64 Linux (Debian) box and I keep getting an error whenever I try to run 'make'. See below for the output of make (./configure returned no obvious errors). (cd port; make) make[1]: Entering directory `/home/JoshVote/gdal/port' /bi

RE: [gdal-dev] GDAL build problems under Linux debian x86_64

2011-05-16 Thread Josh.Vote
Hi Antonio, That seems to have gotten the compiler running. For future Debian users experiencing this problem setting SHELL=/bin/bash worked for me. Thanks a lot Josh Vote -Original Message- From: gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of A

[gdal-dev] GDAL ERS unable to process GDA94 under amd64

2011-05-27 Thread Josh.Vote
Hi All, Sorry the subject is a bit of an acronym soup but I'm having an interesting problem with an ERS file under my amd64 compile of GDAL trunk (revision 22366). I may as well start by describing my problem from the beginning... The attached ERS header belongs to a 5GB ER Mapper dataset for w

RE: [gdal-dev] GDAL ERS unable to process GDA94 under amd64

2011-05-29 Thread Josh.Vote
Hi All, > This is the target directory when building and installing GDAL. This is then > looked for when trying to open of the resource files like ecw_cs.wkt. You can > overrirde this by setting the GDAL_DATA environment variable to point to the > directory where those files are. It turns out