There is a set of images (a handful of .img) and only one block file. I can
open any of the images but that doesn't seem to access the metadata that's
stored on the block file.
-Ryan
On Thu, May 29, 2014 at 3:24 PM, Even Rouault
wrote:
> On Thursday 29 May 2014 12:41:17 Ryan wrote:
>
> > I ha
On Thursday 29 May 2014 12:41:17 Ryan wrote:
> I have some imagery that has metadata stored in Erdas Block Files (.blk)
> that I am having a hard time reading.
>
> It likes the data is stored in an HFA Header, when viewing the file (cat or
> less) it begins with "EHFA_HEADER_TAG".
>
> However, th
> AHH. This changes the whole story. Some cases do not set a SRS. Is
> there any fall-back SRS that I could use when no info is available to
> create one?
> Type, 'linear in unknown units'?
I've successfully tried with :
mem_ds.SetProjection('LOCAL_CS["Unknown"]')
Thanks a lot. I'll
On Thursday 29 May 2014 22:48:04 Joaquim Luis wrote:
> On 29-05-2014 22:08, Even Rouault wrote:
> > > Glad to not do, but than I'm left with nothing. If I do instead as
> >
> > you say
> >
> > > GDALSetMetadataItem(hDstDS, GDALMD_AREA_OR_POINT, "Point", NULL);
> > >
> > >
> > >
> > > which tha
On 29-05-2014 22:08, Even Rouault wrote:
>
> Glad to not do, but than I'm left with nothing. If I do instead as
you say
>
> GDALSetMetadataItem(hDstDS, GDALMD_AREA_OR_POINT, "Point", NULL);
>
> which than equivalent to
>
> GDALSetMetadataItem(hDstDS, "AREA_OR_POINT", "Point", NULL);
>
>
> Glad to not do, but than I'm left with nothing. If I do instead as you say
>
> GDALSetMetadataItem(hDstDS, GDALMD_AREA_OR_POINT, "Point", NULL);
>
> which than equivalent to
>
> GDALSetMetadataItem(hDstDS, "AREA_OR_POINT", "Point", NULL);
>
> than, as I showed before and contrary
This is what GDALMD_AREA_OR_POINT is supposed to do, although I can
imagine that not all drivers will set it even if they should.
Ah, good news.
> GDALSetMetadataItem(hDstDS, "GDALMD_AREA_OR_POINT", "Point", NULL);
Don't do that !!! As I said before "GDALMD_AREA_OR_POINT" as no
particul
On Thursday 29 May 2014 20:58:36 Joaquim Luis wrote:
> > It's a pity that the original
> >
> > > registration type is not preserved in GDAL so we could respect it.
> >
> > Is not preserved : through which operations ?
>
> Through some form of metadata that would inform us that:
> "Although I'm
It's a pity that the original
> registration type is not preserved in GDAL so we could respect it.
Is not preserved : through which operations ?
Through some form of metadata that would inform us that:
"Although I'm reporting cell corner coordinates this file was
originally using cell cen
I have some imagery that has metadata stored in Erdas Block Files (.blk)
that I am having a hard time reading.
It likes the data is stored in an HFA Header, when viewing the file (cat or
less) it begins with "EHFA_HEADER_TAG".
However, there are no raster bands so using gdalinfo or GDALOpen error
On Thursday 29 May 2014 20:16:12 Joaquim Luis wrote:
> On 29-05-2014 19:26, Even Rouault wrote:
> > Joaquim,
> >
> > I'm confused by what you are actually trying to do.
>
> OK Even, I'll try to explain better. As we all know here, GDAL reports
> all region limits as pixel corner coordinates (AREA
It's a pity that the original registration type is not preserved in
GDAL so we could respect it.
Just to be clear. I meant the "original registration type information"
(there are formats that don't even support the "Area" model). Not that
GDAL should do differently that it does.
___
On 29-05-2014 19:26, Even Rouault wrote:
Joaquim,
I'm confused by what you are actually trying to do.
OK Even, I'll try to explain better. As we all know here, GDAL reports
all region limits as pixel corner coordinates (AREA_OR_POINT=Area for
GeoTiffs). GMT on the other hand keeps track of
David,
If you have plenty of storage space, you could translate each JPEG2000 image
to a tiled uncompressed geotiff. Ideally you would use tiles of size 128 to
match with the block size of the VRT driver.
If storage space is an issue, yes you can try reversible JPEG2000 (although
compression ra
Joaquim,
I'm confused by what you are actually trying to do.
GDALMD_AREA_OR_POINT is a #define that evaluates to "AREA_OR_POINT". The string
"GDALMD_AREA_OR_POINT" however is nowhere used in GDAL.
Regarding the MEM driver, GDALMD_AREA_OR_POINT is just a random metadata item.
Some drivers will s
Hi,
I made GMT respect as far as possible the AREA_OR_POINT GeoTiff key
for read/write, but ...
The following was silently ignored (GMT uses the MEM driver)
GDALSetMetadataItem(hDstDS, "AREA_OR_POINT", "Point", NULL);
so digging here and there I found about GDALMD_AREA_OR_POINT, and in
fa
Am 29.05.2014 17:23, schrieb Marcela Campo:
Sure, this is the output of gdalinfo -nomd -norat on the original img file
Origin = (4392504.764280953444541,7439406.971977045759559)
Pixel Size = (30.015846093058180,-30.015846093058180)
Corner Coordinates:
Upper Left ( 4392504.764, 7439406.972) ( 64
On 28/05/2014 19:48, Rémy GOURRAT wrote:
do i need to install the GDAL-1.11.0.win-amd64-py3.3.msi , i think
that’s it just for AMD Processor, right ?
Thanks for your help
Rémy Gourrat
Bonjour,
Since you are French, you may find useful to read this page :
http://geotribu.net/node/636
Jean-C
Sure, this is the output of gdalinfo -nomd -norat on the original img file
Thanks!
Driver: HFA/Erdas Imagine Images (.img)
Files: rec_230076_1994-12-31_f4.img
rec_230076_1994-12-31_f4.img.aux.xml
rec_230076_1994-12-31_f4.rrd
Size is 725, 734
Coordinate System is:
PROJCS["Transverse M
Am 27.05.2014 18:45, schrieb Marcela Campo:
I am not sure about source projection, I found it out doing:
gdalinfo -proj4 input.img
Can you add the full output of gdalinfo input.img (before any reprojection)?
Greetings,
André Joost
___
gdal-dev m
I am working on a project where am creating (and re-creating) a large image
from ~125 image tiles. Each tile is a 5000x5000px jp2000 compressed image,
with no internal tiles.
I have a vrt set up and I have merged them all together using
gdal_translate, but it took ~20 hours to run on an admittedl
Hi Andre, thank you for the information. I mentioned 900913 in the response
because the error code actually refers to it, I have no idea why. I don't
reproject to it and I don't see any mention of it in the geographical
information in the tiff.
The shift is of a couple of kilometers. I have one im
Hello,
I am trying to have GDAL play nice with some geotiff aerial images, and
I have an issue with the way the units are handled on the false
easting/northing parameters.
The images use the California State Plane projection (zone 2), in feet,
not meters, i.e.:
http://spatialreference.org/
23 matches
Mail list logo
