I'm not aware that loading out-db rasters using Windows network path names will work. What happens if you add that network path as a network drive?
Can you try something like the following? All I've done is replace the backslash with a forward slash... raster2pgsql -R -a -F \\\\fileserver/raster/419/napoleonien/*.tif catalog I'm wondering if some escaping rules are getting in the way. On Thu, Jan 29, 2015 at 4:42 AM, Tumasgiu Rossini <rossin...@gmail.com> wrote: > Hi List, > > I am experiencing a problem with outdb geotiff importation. > > I am using the raster2pgsql utility : > > raster2pgsql -R -a -F \\fileserver\raster\419\napoleonien\*.tif catalog > > On a particular set of geotiff ( wich are generated with the same routine > as the others ), the command seems to work fine > but St_BandPath() output null when I'm trying to register the tiffs on a > local server, and it output the character 'ô' on the production server. > > On others set of raster, the band path is correctly stored. > > What am I doing wrong ? > > > > My configuration is the following : > Both Local and server -> > PostgreSQL 9.3.5 installed with EntrepriseDB > Postgis "2.1 USE_GEOS=1 USE_PROJ=1 USE_STATS=1" > Win 7 64bit > "French_France.1252" > > _______________________________________________ > postgis-users mailing list > postgis-users@lists.osgeo.org > http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users >
_______________________________________________ postgis-users mailing list postgis-users@lists.osgeo.org http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users