[Gdal-dev] "Old-Style" ESRI .PRJ files -- Access Violation on
ImportFromESRI
Christopher Michaelis
cmichaelis at happysquirrel.com
Sat Dec 10 14:11:01 EST 2005
Ben,
Thanks very much for the "CSLLoad" trick! That seemed to make all the
difference in the world. Using your code excerpt makes it work
beautifully... apparently my fread approach was flawed. Problem solved!
Thanks again,
--Chris
----
gdal-dev-request at lists.maptools.org wrote:
From: "Ben Discoe" <ben at vterrain.org>
Subject: RE: [Gdal-dev] "Old-Style" ESRI .PRJ files -- Access
Violation onImportFromESRI
To: <gdal-dev at lists.maptools.org>
Message-ID: <00c601c5fd71$0a576a80$9b02a8c0 at DellWork>
Content-Type: text/plain; charset="us-ascii"
Chris,
Don't know if this helps, but we also moved our project from using
"importFromWkt" to "importFromESRI" and the transition was painless, no
crashes or unexpected behavior.
You could check for the usual things: GDAL is latest release, GDAL data
files are being found, etc. - next step would probably be to step into
importFromESRI and see where it's failing.
BTW, i think you could reduce your test example below to:
OGRSpatialReference oSRS;
char **papszPrj = CSLLoad(argv[1]);
OGRErr eErr = oSRS.importFromESRI(papszPrj);
CSLDestroy( papszPrj );
Good luck,
Ben
More information about the Gdal-dev
mailing list