* Yi Dong [2015-06-15 14:18:02 -0400]:
> Dear List,
>
> I have a question about recitify satellite images that has RPC camera
> using gdalwarp. I know gdalwarp can be used for this task, with using
> RPC metadata (either packed inside the NITF or stored inside RPB files)
> Normally, the image
RC2 compiles and runs on Windows.
-jeff
On 2015-06-14 4:28 PM, Even Rouault wrote:
Hi,
Due to a regression that could cause compressed GeoTIFF created by GDAL to be
almost twice as large as their optimal size in some circumstances (see
https://trac.osgeo.org/gdal/ticket/5999), I have prepar
Hi Evan,
Thanks a lot! Your suggestion is exactly what I am looking for. To
keep the record, here is what I did
1. gdal_translate -of VRT input.ntf input.vrt
2. modify the 'input.vrt' w.r.t. correct RPC model, name it as
'input_correct.vrt'
3. gdalwarp -rpc -to RPC_HEIGHT=200 input_correct.
Le lundi 15 juin 2015 21:00:15, Nicolas Cadieux a écrit :
> Thanks Even,
> One last question about the buffer. Is 2GB is the max buffer size for
> gdal_grid? If I select that, am I likely to run into problem with some
> values?
The variable is a uint32 so you could probably go up to 4 GB.
> Apar
Hi Nicolas,
I see someone already posted something about lidar2dems. We also wanted
to use only open-source, so put together this project to easily be able to
make DEMs using what's out there already.
The documentation gives an overview of what it can do and a tutorial for
processing a large are
Thanks Even,
One last question about the buffer. Is 2GB is the max buffer size for
gdal_grid? If I select that, am I likely to run into problem with some values?
Apart from trial and error, is there a balance that should be stuck between
available computer memory (currently at 64GB), input file
Le lundi 15 juin 2015 20:18:02, Yi Dong a écrit :
> Dear List,
>
> I have a question about recitify satellite images that has RPC camera
> using gdalwarp. I know gdalwarp can be used for this task, with using
> RPC metadata (either packed inside the NITF or stored inside RPB files)
> Normally, th
Hi Yi,
GDAL use the RPC which it report by gdalinfo. If gdalinfo reports old
RPC, you have to clean them from dataset. It seem's to me that rpb
(*_rpc.txt, etc.) files accepted only on GeoTIFF and TILL formats. On
GDAL 2.0 also jp2 added. So NITF is not a right format for use external
RPC. So
Dear List,
I have a question about recitify satellite images that has RPC camera
using gdalwarp. I know gdalwarp can be used for this task, with using
RPC metadata (either packed inside the NITF or stored inside RPB files)
Normally, the image folder shall contain following files
input.ntf
inp
I'll call soon on a vote on this if nobody has remarks.
Le jeudi 04 juin 2015 16:05:00, Even Rouault a écrit :
> Hi,
>
> I've updated an old RFC initiated by Tamas. The main idea, having a hashset
> based implementation as an alternative to the array based, remains. Changes
> consist mainly in co
Ah, great! That fixed it :-)
Is there an official 1.11.3 release in the works? It's a bit of hassle for
me to integrate it into our build system here, so if there's a new official
version out soon I probably won't bother to integrate the current snapshot.
Thanks so much for your help, Even!
- Th
Le lundi 15 juin 2015 15:51:37, Thomas Sevaldrud a écrit :
> When using the same image in GeoTIFF with overviews, it works correctly,
> which may indicate something with the ECW drivers. I suppose it must be
> something triggered by something weird I'm doing though, or else I would
> think that oth
When using the same image in GeoTIFF with overviews, it works correctly,
which may indicate something with the ECW drivers. I suppose it must be
something triggered by something weird I'm doing though, or else I would
think that other people would have the same problem.
The weird thing is that if
Thomas,
2 suggestions to help narrowing down the issue :
- try gdalwarp of GDAL 2.0 that can select the most appropriate overview
given the target resolution / raster size
- try with the ECW translated as a GeoTIFF to check if it isn't an issue with
the ECW driver itself.
Even
> Hi,
>
> I am
Argh, I managed to send it while editing :-)
Anway, input to this code section is the wanted overview level and the
derived scale factors in X- and Y-direction. Output is the vrtDS dataset
that is used in the GDAL Warp api later.
Are there any obvious mistakes I've made here?
I see that in GDAL
Hi,
I am having a bit of trouble with warping a dataset (an ECW file) with
multiple overviews. The base file is huge, so I am selecting the overview
that matches closest to my output resolution and makes an in-memory VRT of
this, consisting of the overview bands of the original image.
This seems
Hi,
Below information is also true for GDAL Trac.
Even
-- Message transmis --
Sujet : [GRASS-user] Please check your trac settings for email notifications
Date : lundi 15 juin 2015, 11:14:29
De : Markus Neteler
À : GRASS developers list , GRASS user list
Hi all,
FYI
recen
Graeme B. Bell wrote
> You'll need to tell it what size you want to burn. You can do that by
> looking at the extents (northeast, southwest) of your current
> raster/geotiff.
If you make a copy of the Geotiff you already have, you can provide it as
the 'destination dataset' for gdal_rasterize, it
Great work, really looking forward to it. If i understand it correctly this
should make working with GDAL much more robust if you are using it with
language bindings.
For example, when using Conda (package/env manager) with GDAL and the Python
bindings. I often put the location of the GDAL utilit
19 matches
Mail list logo
