[GRASS5] Using external PROJ with 5.3
paul-grass at stjohnspoint.co.uk
Fri May 21 09:29:36 EDT 2004
On Fri, 14 May 2004, Frank Warmerdam wrote:
> I would also note that if you are going to distribute a GDAL shared library
> with GRASS you also need to carry along the support data (normally installed
> as /usr/local/shared/gdal) with various EPSG tables, and other support data
> files used by specific raster and vector drivers. These could live in the
> GRASS tree, but r.in.gdal would need to be altered slightly to push an
> appropriate file search location on the GDAL data search path.
Good point. The existing GRASS release rules say only to include
libgdal.1.1.so; has this not been a problem for anyone already? In GRASS
5.7 local copies of some of these files are included for co-ordinates
system definitions---the function SetCSVFilenameHook() is used in a few
places to set the correct location to look for these and it works well.
But the point of doing that was that I thought these files weren't
guaranteed to be included in a GDAL installation. But if as you say they
are necessary for some drivers then we probably could rely on them being
installed. Several issues there I suppose with no real answers.
Maybe just make a PROJ and GDAL binary distribution that have been tested
with the GRASS binaries, and distribute them all together. Is there an
easy equivalent to the GRASS 'make bindist' for making PROJ.4 and GDAL
More information about the grass-dev