Hi Jukka Rahkonen,
Thanks for the provided information.
Now I am able to see the lat/long values in the GeoLocator tool for the files
created with ISO32000 option.
I have installed the Terrago tool bar and created the file with OGC_BP option
and noticed that neither Adobe's GeoLocator tool nor T
On 2015-04-07 16:33, Even Rouault
wrote:
This RFC modifies the GDALRasterBand GetHistogram(), GetDefaultHistogram() and
SetDefaultHistogram() methods to accept arrays of 64-bit integer instead of
the current arrays of 32-bit integer for bucket counts. This will fi
Hi,
This is a call for discussion on "64-bit bucket counts for histograms" (last
one for today ;-) and hopefully a no-brainer)
https://trac.osgeo.org/gdal/wiki/rfc57_histogram_64bit_count
Summary :
This RFC modifies the GDALRasterBand GetHistogram(), GetDefaultHistogram() and
SetDefaultHistog
Even Rouault-2 wrote
> Yuta,
>
> Increasing GDAL_CACHEMAX might accelerate in case of repeated reads on
> windows
> that are identical or overlapping already read windows. Or if the way you
> read
> the raster doesn't follow its block shape : for example if the raster is
> organized by lines/st
Hi,
This is a call for discussion on "RFC 56: OFTTime/OFTDateTime millisecond
accuracy".
https://trac.osgeo.org/gdal/wiki/rfc56_millisecond_precision
Summary :
This RFC aims at adding millisecond accuracy to OFTTime and OFTDateTime fields,
as a number of formats support it explicitely or impl
Hi Evan,
Thanks for the prompt reply.
Regards
Sunil
-Original Message-
From: Even Rouault [mailto:even.roua...@spatialys.com]
Sent: 07 April 2015 01:21:PM
To: gdal-dev@lists.osgeo.org
Cc: Vankadara, Sunil
Subject: Re: [gdal-dev] Relating to GeoLocation tool of Geospatial PDF Document
L
Hi Jukka Rahkonen,
Thanks for the prompt information. My GDAL is not linked to proj4 libraries to
use ISO32000 option.
I am trying to link the GDAL with Proj4 and test the Geolocation workflow.
Regards
Sunil
-Original Message-
From: gdal-dev-boun...@lists.osgeo.org
[mailto:gdal-dev-bou
Vankadara, Sunil hexagongeospatial.com> writes:
>
>
>
> Hi Team,
>
> I created a PDF file with OGC_BP as GEO_ENCODING option like shown in the
below command. The below tif file’s Datum and Projection details are WGS84
/Geographic (lat/lon).
>
> ./gdal_translate.exe -of PDF ../../Data/inp
Le mardi 07 avril 2015 01:15:17, Mike Toews a écrit :
> On 6 April 2015 at 09:39, Even Rouault wrote:
> > I should have mentionned what currently exists indeed :
> > struct {
> >
> > GInt16 Year;
> > GByte Month;
> > GByte Day;
> > GByte Hour;
> >
Le mardi 07 avril 2015 09:37:35, Vankadara, Sunil a écrit :
> Hi Team,
>
> I created a PDF file with OGC_BP as GEO_ENCODING option like shown in the
> below command. The below tif file's Datum and Projection details are
> WGS84 /Geographic (lat/lon).
>
> ./gdal_translate.exe -of PDF ../../Data/
Hi Team,
I created a PDF file with OGC_BP as GEO_ENCODING option like shown in the
below command. The below tif file's Datum and Projection details are WGS84
/Geographic (lat/lon).
./gdal_translate.exe -of PDF ../../Data/input/sample256x256_1.tif
../../Data/output/sample256x256_1.pdf -co GEO
Brad Hards frogmouth.net> writes:
> The problematic part is that "PROJECTION" definition. I was originally
going to
> argue it should be Mercator_1SP, but it looks like the EPSG decided to change
> it (in EPSG::2010.058) to this new "Mercator_variant_A" form, and keep the
> "Mercator_1SP" for
12 matches
Mail list logo
