[GRASS5] EPSG update to GRASS?

GRASS GIS GRASS GIS developer
,
1

Hi,

please take the time to look at
http://bugzilla.remotesensing.org/show_bug.cgi?id=510

Frank updated EPSG files in PROJ and GDAL in CVS. I
assume that we should do the same to maintain synchronization.

If there are no objections, I'll update the two files
as indicated in above bug report.

Markus

2

On Wed, Apr 26, 2006 at 09:56:32AM +0200, Markus Neteler wrote:

Hi,

please take the time to look at
http://bugzilla.remotesensing.org/show_bug.cgi?id=510

Frank updated EPSG files in PROJ and GDAL in CVS. I
assume that we should do the same to maintain synchronization.

If there are no objections, I'll update the two files
as indicated in above bug report.

OK, I didn't see objections.

So I have updated

lib/proj/
gcs.csv
pcs.csv
stateplane.csv

in CVS using the recently updated files from GDAL (gdal/data/)
which were also updated in PROJ4 (proj/nad/).

Since new GDAL and PROJ releases are expected very soon, there
shouldn't be any packaging issues.

Markus

PS: the related GDAL changlog entries:

2006-04-21 06:30 fwarmerdam
        * gcs.csv, pcs.csv: updated overrides

2006-04-21 06:01 fwarmerdam
        * gcs.csv, pcs.csv: updated with show_crs and deprecated columns

2006-04-08 01:26 fwarmerdam
        * stateplane.csv: Fixed California VII to point to fixed EPSG code.

2006-02-28 06:44 fwarmerdam
        * ellipsoid.csv, gcs.csv, gdal_datum.csv, pcs.csv,
          projop_wparm.csv, unit_of_measure.csv: upgrade to EPSG 6.9

The related PROJ entries:

2006-04-21 06:35 fwarmerdam
        * epsg: upgraded epsg lookup file

2006-03-10 14:30 fwarmerdam
        * epsg: updated to EPSG 6.9

3

Hello Markus,

On Thu, 27 Apr 2006 17:35:27 +0200 Markus Neteler <neteler@itc.it>
wrote:

On Wed, Apr 26, 2006 at 09:56:32AM +0200, Markus Neteler wrote:
> Hi,
>
> please take the time to look at
> http://bugzilla.remotesensing.org/show_bug.cgi?id=510
>
> Frank updated EPSG files in PROJ and GDAL in CVS. I
> assume that we should do the same to maintain synchronization.
>
> If there are no objections, I'll update the two files
> as indicated in above bug report.

OK, I didn't see objections.

So I have updated

lib/proj/
gcs.csv
pcs.csv
stateplane.csv

in CVS using the recently updated files from GDAL (gdal/data/)
which were also updated in PROJ4 (proj/nad/).

Since new GDAL and PROJ releases are expected very soon, there
shouldn't be any packaging issues.

for backward-compatibility could you tag (or somewhere promote the
cvs-commit-date of this update in CVS) so that we
know where to stop updating at least the proj-files to not run in
trouble when still using proj 4.4.9 and gdal 1.3.1?

Thanks

  Stephan