Granted, I haven't tried V 5 yet, but your quote also states, "Google Earth
Pro or EC". Are you using one of those versions of the client? In any
case, if the file opens in OpenEV, chances are good that the .ntf generated
by gdal is ok, and that there is some sort of problem with how Google Earth
Google Earth 5.0 supports NITF see
http://earth.google.com/intl/en/userguide/v5/ug_importdata.html
[Importing Imagery
You can open GIS imagery files in Google Earth Pro or EC and have the files
correctly projected over the proper map coordinates in the 3D viewer. Google
Earth Pro and EC suppo
See http://earth.google.com/userguide/v4/ug_imageoverlays.html#requirements,
I don't believe the "NITF (rw+): National Imagery Transmission Format" is
supported by Google Earth.
Roger
--
On Wed, Apr 8, 2009 at 3:27 PM, mohwawang wrote:
>
> Hi all,
>
> I'm sorry that this is the third time I tri
Hi all,
I'm sorry that this is the third time I tried to send this message out because
I myself didn't get the first two through gdal-dev@lists.osgeo.org so I thought
others might not get it either.
I used gdal_translate to convert a tif image to a nitf image as:
>gdal_translate -of nitf in.ti
Le Wednesday 08 April 2009 23:31:59 Ivan Lucena, vous avez écrit :
> Hi Even,
>
> D'accord. Good tip.
>
> Although I am planning to read a relative large number of bands (temporal
> series) I can probably enlarge my query windows and balance the memory load
> that it will take. I would do that if I
Hi Even,
D'accord. Good tip.
Although I am planning to read a relative large number of bands (temporal series) I can probably
enlarge my query windows and balance the memory load that it will take. I would do that if I was
developing some kind of application. The thing is that Python + GDAL +
I'm not aware any further dependencies of the hfa driver so it should
compile.
You might want to try the build SDKs available here for your
compiler/platform.
http://vbkto.dyndns.org:1280/sdk/index.html
Just extract any type 'nmake gdal' in a Visual Studio Command Prompt to
build it.
Best regards
Hi all,
My apology if you get this email twice. I myself didn't get the first one so I
thought others might not get it either.
I used gdal_translate to convert a tif image to a nitf image as:
>gdal_translate -of nitf in.tif out.ntf -co ICORDS=G
Input file size is 561, 420
0...10...20...30...40
And I forgot to mention that if you need to operate on big images, you'll have
probably suboptimal/poor performance by just extracting one pixel at a time,
as there's a non neglectable overhead for each binding function call,
especially that one. I'd advise you to read bigger chunks at once, and
Ivan,
yes I can also reproduce it with GDAL 1.6.0 swig python bindings. This was a
memory leak in a python typemap that has been fixed in the stable branch SVN
(most probably by http://trac.osgeo.org/gdal/changeset/16453) and trunk SVN.
Best regards,
Even
___
Hi all,
I used gdal_translate to convert a tif image to a nitf image as:
>gdal_translate -of nitf in.tif out.ntf -co ICORDS=G
Input file size is 561, 420
0...10...20...30...40...50...60...70...80...90...100 - done.
I can display both in.tif and out.ntf with OpenEV. So both in.tif and out.ntf
we
Hi,
I have a small Python script that uses ReadRaster to collect some values in
order to do some math.
The problem is that once I run the script through a Python IDE I can see the
memory usage increasing but it does
not decrease at the end.
After some runs I got a out of memory crash on the
Wendy Fay Stevenson wrote:
Hi
I have successfully built Gdal-1.5.3 on Windows using Visual Studio 2008. I am
trying to build the latest release but I obtain an unresolved external for
_HFAAuxBuildOverviews. How can I fix this error.
I have read all the information I could find on building g
Hi
I have successfully built Gdal-1.5.3 on Windows using Visual Studio 2008. I am
trying to build the latest release but I obtain an unresolved external for
_HFAAuxBuildOverviews. How can I fix this error.
I have read all the information I could find on building gdal for windows but
nowhere
Hi again,
We passed through the "error LINK2001: unresolved external symbol" errors.
We are stuck with the following error message now:
gr_capi_test.c
..\gdalwin32-1.4.1\include\cpl_port.h(106) : fatal error C1001:
INTERNAL COMPILER ERROR
(compiler file 'msc1.cpp', line 1786)
chalda wrote:
Hello,
I have question about setting of compression of the ECW codec. I have
read the article on the page http://www.gdal.org/frmt_ecw.html and there
is said that option TARGET=percent sets size reduction as a percentage
of the original image.
I'm using the ECW codec through g
Hello,
I have question about setting of compression of the ECW codec. I have
read the article on the page http://www.gdal.org/frmt_ecw.html and there
is said that option TARGET=percent sets size reduction as a percentage
of the original image.
I'm using the ECW codec through gdal_translate b
What OS are you in? What output format is that, JDEM, USGSDEM, an elevation
model in any other raster format?
Check the "for" help (type "for help" on Windows, "man for" on UNIX).
Example in Windows with Geotiff output:
C:\> for %I in (E:\asci\*.asc) do gdal_translate -of gtiff %I
E:
Hello everyone,
i am new with gdal and i need someone help. I need to translate a lots of
ascii file in some other formats, dem for example.
I searched a lot in the net but i couldn't find the right command to do
that. I mean, i found some but i always get an error message. I miss
something...
My
19 matches
Mail list logo
