[GRASS-dev] PROJ csv files sync GDAL -> GRASS?

Markus Neteler neteler at osgeo.org
Tue Aug 26 07:02:20 PDT 2014

(back to very old task)

On Sun, Aug 2, 2009 at 10:39 PM, Markus Neteler <neteler at osgeo.org> wrote:
> (back to old task)
> On Tue, Apr 28, 2009 at 12:57 PM, Paul
> Kelly<paul-grass at stjohnspoint.co.uk> wrote:
>> On Sat, 25 Apr 2009, Markus Neteler wrote:
>>>> I think we can remove the files and the associated stuff you mentioned if
>>>> these conditions are true:
>>>>  * The .csv files are always installed by default with GDAL
>>>>  * A GDAL installation is not considered a working installation if these
>>>>   files are not present
>>> I have no idea if the conditions are true...
>> Me neither. I think perhaps we should experimentally remove the files in 7.x
>> and let GDAL find them itself, and see if there are any problems reported. I
>> will do that when I get some time.
> OK, I'll leave that to you (Paul).

This issue is still open I think.
Did anyone dare to to locally remove the CSV files and continue using GRASS 7?

>>> Since there are new additional CSV files which haven't been there before I
>>> also don't know if to add those or not.
>> Well they look like they might be relevant, and it can't do any harm to add
>> them, so I think for 6.x we should add them just in case they are really
>> needed by the more recent versions of GDAL.
> I have update the files to EPSG 7.1 from GDAL/data/ in 6.4, 6.5 and 7.
>> So - a little more complexity for now, but hopefully if there are no
>> problems we can simplify all this for 7.x.

Perhaps we need to manage all this via trac ticket?


More information about the grass-dev mailing list