[GRASS-dev] [GRASS GIS] #3191: coordinate reference system issue when exporting to Rasterlite

GRASS GIS trac at osgeo.org
Mon Oct 24 10:20:42 PDT 2016


#3191: coordinate reference system issue when exporting to Rasterlite
--------------------------+-------------------------------------
  Reporter:  vincent      |      Owner:  grass-dev@…
      Type:  defect       |     Status:  new
  Priority:  normal       |  Milestone:  7.0.6
 Component:  Raster       |    Version:  unspecified
Resolution:               |   Keywords:  gdal export, Rasterlite
       CPU:  Unspecified  |   Platform:  Unspecified
--------------------------+-------------------------------------

Comment (by hellik):

 Replying to [comment:2 vincent]:
 > Yes, I've come to the same observation so far, but I don't know enough
 about how GRASS parses projection info to gdal; sorry for this rather
 naive question but in the case of GTiff driver why then is there no need
 to worry about coordinate reference system information for it to work?
 >
 > Well, if you all prefer, we can close the ticket.

 taken from the [https://lists.osgeo.org/pipermail/gdal-
 dev/2016-October/045359.html GDAL ML]

 {{{
 > is this intentional that there is no srs by a simple gdal_translate of a
 > geotiff to a Rasterlite db?

 From what I can see the driver doesn't handle adding a new entry in the
 spatial_ref_sys table if there's no AUTHORITY node, such as in your use
 case.
 From what I can see, it also probably doesn't properly support creating
 entries in spatial_ref_sys with Spatialite 4 layout (the driver has been
 likely developped during Spatialite 3 era)
 It is "intentional" in the meaning that this wasn't implemented, but could
 potentially be added. Could be worth a ticket in Trac.

 > maybe there is some other command line option related to Rasterlite db
 > which I'm missing?

 No, the workaround is the one you found. Make sure a EPSG code is attached
 to
 the input dataset, or assign it explictly
 }}}

 I think this ticket can be closed; but I'll open another one for the last
 issue mentioned above.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3191#comment:4>
GRASS GIS <https://grass.osgeo.org>



More information about the grass-dev mailing list