Yet another NITF related problem. An ntf file contains (no SUBDATASETS)
gdalinfo -nogcp -nomd -mm M1BS.ntf
,--%---
Band 1 Block=1024x1024 Type=UInt16, ColorInterp=Blue
Computed Min/Max=183.000,2047.000
Overviews: 3438x3448, 1719x1724, 859x862, 429x431, 214x215
Overviews: arbitrary
Band 2
On Wednesday 31 of July 2013 11:55:27 Nikos Alexandris wrote:
Yet another NITF related problem. An ntf file contains (no SUBDATASETS)
gdalinfo -nogcp -nomd -mm M1BS.ntf
,--%---
Band 1 Block=1024x1024 Type=UInt16, ColorInterp=Blue
Computed Min/Max=183.000,2047.000
Overviews:
lpinner wrote:
A workaround to your 2nd question is to set the GDAL_PAM_PROXY_DIR
environment variable, either permanently or on the commandline before you
call gdalinfo.
set GDAL_PAM_PROXY_DIR=%TEMP%
gdalinfo -stats some.ntf
Thank you Luke.
1st, that would be
,--%---
# set variable
Luke:
%TEMP% is the Windows environment variable pointing to the temp directory.
For Unix/linux:
,--%---
# set variable
export GDAL_PAM_PROXY_DIR=/tmp
# confirm
echo $GDAL_PAM_PROXY_DIR
/tmp
`---%--
So much to my bash knowledge... :D
It works fine, thank you very much!
Nikos
[rest
2013 10:25 PM
To: gdal-dev@lists.osgeo.org
Cc: Pinner, Luke
Subject: Re: [gdal-dev] Working with NTF files
lpinner wrote:
A workaround to your 2nd question is to set the GDAL_PAM_PROXY_DIR
environment variable, either permanently or on the commandline before you
call gdalinfo.
set
Nikos Alexandris:
I am trying to handle ntf files (NITF) as easy as possible -- working
with some WorldView 01/02 and QuickBird imagery.
[..]
2) A second, of less importance, question, is: how important are the
warnings like: Warning 1: Unable to save auxilary information in
-Working-with-NTF-files-tp5066312p5069520.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Nikos A:
No (except that I left this option as the final attempt of many tests --
working with some 1GB images here, so it took me hours... :D). Your
confirmation, though, is highly useful!
Eli Adam wrote:
Sometimes to avoid materializing large intermediate datasets on disk, a VRT
can
No (except that I left this option as the final attempt of many tests --
working with some 1GB images here, so it took me hours... :D). Your
confirmation, though, is highly useful!
Sometimes to avoid materializing large intermediate datasets on disk, a VRT
can be used. I'm not sure if this
Hi list apologies for cross-posting.
In short,
I am trying to handle ntf files (NITF) as easy as possible -- working with
some WorldView 01/02 and QuickBird imagery.
1) The question is: how do you correctly import in GRASS-GIS QuickBird
WorldView imagery from N(I)TF containers?
2) A
On Sun, Jul 14, 2013 at 2:53 PM, Nikos Alexandris
n...@nikosalexandris.netwrote:
Hi list apologies for cross-posting.
In short,
I am trying to handle ntf files (NITF) as easy as possible -- working with
some WorldView 01/02 and QuickBird imagery.
1) The question is: how do you correctly
Nikos Alexandris:
I am trying to handle ntf files (NITF) as easy as possible -- working with
some WorldView 01/02 and QuickBird imagery.
1) The question is: how do you correctly import in GRASS-GIS QuickBird
WorldView imagery from N(I)TF containers?
Frank Warmerdam wrote:
Your
12 matches
Mail list logo