[GRASS-dev] [GRASS GIS] #3048: r.out.gdal does not write EPSG code of the projection

GRASS GIS trac at osgeo.org
Sat May 28 04:22:12 PDT 2016

#3048: r.out.gdal does not write EPSG code of the projection
  Reporter:  sbl          |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:  7.0.5
 Component:  Raster       |    Version:  svn-trunk
Resolution:               |   Keywords:  r.out.gdal
       CPU:  Unspecified  |   Platform:  All

Comment (by sbl):

 To me it seems the issue is also present in your nc_spm_08_grass7

 Replying to [comment:2 neteler]:
 > Thinking more about it, I believe that it is not possible to generate
 the AUTHORITY here because GRASS internally uses the PROJ.4

 In my location the AUTHORITY parameter is present but it is not used in
 r.out.gdal never the less, so it would not have to be generated.

 > Note that EPSG codes often don't include the DATUM string since several
 datums may exist (that's why GRASS comes with a sophisticated lookup
 mechanism which isn't present in GDAL for example).
 > Back to the original report:
 > > which is thus not properly recognized by other tools (e.g. QGIS, but
 esp. !GeoServer).
 > Can you elaborate?
 Sure, in QGIS my raster in EPSG:25832 is interpreted as EPSG:3044 (both
 have equal proj-strings). However, CRS do not match and also in PostGIS
 SRID would not match, so they have to defined manually for analysis with
 other data one has in the originally used CRS 25832.
 In GeoNode / GeoServer the GeoTiffs exported from GRASS are shown as pink
 boxes as long as one does not define the projection in GeoServer manually.

Ticket URL: <http://trac.osgeo.org/grass/ticket/3048#comment:3>
GRASS GIS <https://grass.osgeo.org>

More information about the grass-dev mailing list