no, no : it was just an imaginary srid for the example. V.
Le mardi 25 octobre 2016 à 12:15 +0200, Maciej Sieczka a écrit : > W dniu 25.10.2016 o 12:02, Vincent Bain pisze: > > thanks for your suggestion. In fact, the script runs without error or > > warning but it does not change anything : > > > > gdalinfo Rasterlite:my_db.sqlite,table=my_raster > > [...] > > AUTHORITY["EPSG","54321"]] > > [...] > > > > gdal_edit.py -a_srs EPSG:12345 \ > > Rasterlite:my_db.sqlite,table=my_raster > > What is EPSG:12345? This doesn't look like a common EPSG SRID. If you > want to use it with GDAL, you would need to make sure it's defined in > GDAL support files. > > From https://trac.osgeo.org/grass/ticket/3191#comment:1 it looks like > you are after EPSG:31255 actually. Does this one work with gdal_edit.py? > > > gdalinfo Rasterlite:my_db.sqlite,table=my_raster > > [...] > > AUTHORITY["EPSG","54321"]] > > [...] > > > > Anyway, on the spatialite> prompt it's a matter of seconds... > > > > Le mardi 25 octobre 2016 à 11:39 +0200, Maciej Sieczka a écrit : > >> W dniu 24.10.2016 o 14:06, Vincent Bain pisze: > >>> Unfortunately this is not a valid lco... > >>> > >>> OK, it is not really a critical issue as we can easily solve it whether > >>> via gdal_translate or via a simple sql update, > >> > >> Maybe `gdal_edit.py -a_srs' will be the simplest workaround? _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
