Hi all,
I'm trying to project a raster from EPSG:4326 to EPSG:3857 and I get the
following error:
> gdalwarp -s_srs EPSG:4326 -t_srs EPSG:3857 -of GTiff
-dstnodata 255 vc_2006.tif vc_2006_2.tif
ERROR 1: failed to load NAD27-83 correction file
ERROR 1: GDALSuggestedWarpOutput() failed because
> Hi,
>
> I am trying to use gdal_grid to interpolate some data and I am having
> trouble making gdal_grid treat spatial data (WGS84 lat/lon coordinates) as
> points on a continuous plane. It seems to be ignoring the dateline so for
> example values at 45, 179 are not properly interacting with
On 27-12-2012 19:22, Even Rouault wrote:
Le jeudi 27 décembre 2012 20:14:40, Andrew Smith a écrit :
Hi,
I am trying to use gdal_grid to interpolate some data and I am having
trouble making gdal_grid treat spatial data (WGS84 lat/lon coordinates) as
points on a continuous plane. It seems to be
Le jeudi 27 décembre 2012 20:14:40, Andrew Smith a écrit :
> Hi,
>
> I am trying to use gdal_grid to interpolate some data and I am having
> trouble making gdal_grid treat spatial data (WGS84 lat/lon coordinates) as
> points on a continuous plane. It seems to be ignoring the dateline so for
> exa
Hi,
I am trying to use gdal_grid to interpolate some data and I am having
trouble making gdal_grid treat spatial data (WGS84 lat/lon coordinates) as
points on a continuous plane. It seems to be ignoring the dateline so for
example values at 45, 179 are not properly interacting with values at 45,
Thanks Trent, I tried it out:
original: 3.886.894.126b
compressed DEFLATE:266.046.034b
compressed LZW: 372.085.756b
compressed JPEG: 90.055.344b
Although DEFLATE and LZW give very good results, JPEG compression is so
much better that I need t
Jan,
Jpeg is a lossy compression and thus the collar will not be maintained
perfectly as black (or 0). You will not get as much compression, but you
can try a lossless method like LZW or Packbits. If you are getting close to
the 4GB limit you might need to add "-co bigtiff=if_safer".
Good luck,
Le jeudi 27 décembre 2012 15:35:25, Jan Hartmann a écrit :
> On 12/27/2012 03:11 PM, Even Rouault wrote:
> > Le jeudi 27 décembre 2012 15:11:23, Jan Hartmann a écrit :
> >> On 12/27/2012 02:41 PM, Even Rouault wrote:
> >>> I've just pushed a fix since building overviews with "--config
> >>> COMPRES
On 12/27/2012 03:11 PM, Even Rouault wrote:
Le jeudi 27 décembre 2012 15:11:23, Jan Hartmann a écrit :
On 12/27/2012 02:41 PM, Even Rouault wrote:
I've just pushed a fix since building overviews with "--config
COMPRESS_OVERVIEW JPEG -- config PHOTOMETRIC_OVERVIEW
YCBCR" when there's a .msk did
Le jeudi 27 décembre 2012 15:11:23, Jan Hartmann a écrit :
> On 12/27/2012 02:41 PM, Even Rouault wrote:
> > I've just pushed a fix since building overviews with "--config
> > COMPRESS_OVERVIEW JPEG -- config PHOTOMETRIC_OVERVIEW
> > YCBCR" when there's a .msk didn't work.
> >
> >> OK Even, thanks
On 12/27/2012 02:41 PM, Even Rouault wrote:
I've just pushed a fix since building overviews with "--config
COMPRESS_OVERVIEW JPEG -- config PHOTOMETRIC_OVERVIEW
YCBCR" when there's a .msk didn't work.
OK Even, thanks. This means that I should use gdal-svn?
Not necessarily. I think you can wo
Le jeudi 27 décembre 2012 14:37:49, Jan Hartmann a écrit :
> On 12/27/2012 02:27 PM, Even Rouault wrote:
> > The artifacts are due to the lossy characteristics of JPEG compression
> > that are particularly visible on borders between nodata pixel and valid
> > pixels. An option would be to use nearb
On 12/27/2012 02:27 PM, Even Rouault wrote:
The artifacts are due to the lossy characteristics of JPEG compression that
are particularly visible on borders between nodata pixel and valid pixels. An
option would be to use nearblack to create a .msk mask file :
nearblack -setmask -o big_with_mask
Le jeudi 27 décembre 2012 13:38:50, Jan Hartmann a écrit :
> Can anyone tell me wath is happening here? I have a large three-band
> raster (3.8G) looking like this:
>
> http://mapserver.sara.nl/map2a.png
>
> I compress it (from information from this list a few days ago) with:
>
> gdal_translate
That would be an option. Am I right that the datasource of the -cutline
option is a closed polygon, and that everything outside the polygon will
be clipped?
However, I would prefer not to add extra steps. These are large maps and
there are lots of them (about 17.000 for the whole of the Nether
Hi Jan,
You can cut result raster with the geometry (shape file) using gdalwarp
with cutline option (http://gdal.org/gdalwarp.html).
Best regards,
Dmitry
27.12.2012 16:38, Jan Hartmann ?:
Can anyone tell me wath is happening here? I have a large three-band
raster (3.8G) looking like
Can anyone tell me wath is happening here? I have a large three-band
raster (3.8G) looking like this:
http://mapserver.sara.nl/map2a.png
I compress it (from information from this list a few days ago) with:
gdal_translate -co COMPRESS=JPEG -co PHOTOMETRIC=YCBCR big.tif small.tif
gdaladdo --conf
17 matches
Mail list logo
