Okay, but how is the best way to fix it? Since pnqnq runs on individual
tiles, I would not expect tiles to have the same palette.
What is needed is to read the nq tiles into memory, convert to RGBA
raster, then put that into overview tile. How tricky is this to do? Any
pointers into the API th
Le vendredi 14 juin 2013 00:26:52, Phil Scadden a écrit :
> >Not sure to completely follow you ...
>
> Okay, what goes on in gdal2tiles.py, is that after creating the base
> tiles, (and in my version, they are quantised) the base tiles are taken
> in groups of 4, read into a new MEM driver raste
>Not sure to completely follow you ...
Okay, what goes on in gdal2tiles.py, is that after creating the base
tiles, (and in my version, they are quantised) the base tiles are taken
in groups of 4, read into a new MEM driver raster to make a one tile,
then resampled down to size of base tile to
Le jeudi 13 juin 2013 06:29:32, Phil Scadden a écrit :
> I was hacking gdal2tiles a bit by running pnqnq of a base tile
> immediately after creating it (I want to be able to run partial updates
> on a TMS which has been pngnq optimised). No problem with that, but
> updating the overview tiles produ
Le jeudi 13 juin 2013 09:46:16, 梁天辰 a écrit :
> Hi all,
>
> According to page http://www.gdal.org/ogr/ogr_sql.html , I found that <, >,
> <= and >= operators are case sensitive.
Hum, it appears that this was true before the rewriting of the OGR SQL engine
for GDAL 1.8.0. The current implementat
Le jeudi 13 juin 2013 15:54:42, Etienne Tourigny a écrit :
> that should be a simple as
>
> gdal_translate -of AAIGrid in.nc out.asc
Except that AAIGrid only supports 1-band datasets. I can't think of a ASCII
based format that supports multi-band datasets.
>
> On Thu, Jun 13, 2013 at 8:32 AM,
PSC / committers / coders,
If you would join the 2014 code sprint at either of the proposed venues, noting
so on the doodle would be must helpful!
P.
--
Paul Ramsey
http://cleverelephant.ca
http://postgis.net
Forwarded message:
> From: Paul Ramsey
> To: Stephan Meißl
> Cc: tospr...@lists
Hi All,
I posted a few days ago about trying to find the transform for a NITF chip, for
instance to map from the chip pixel coordinates to geo coordinates. I was able
to come close in terms of my mapping but it does not seem to match with other
sources that are interpreting the data. Would so
On 6 June 2013 19:06, Even Rouault wrote:
> > frmts/msg/msgcommand.cpp:434: error: 'sprintf' was not declared in this
> > scope
> > (needed a #include)
>
> Perhaps you can provide the patch ? This driver is most likely not
> compiled on
> a regular basis due to its unusual dependencies.
>
I jus
that should be a simple as
gdal_translate -of AAIGrid in.nc out.asc
On Thu, Jun 13, 2013 at 8:32 AM, Paul Meems wrote:
> Hi list,
>
> I have a netCDF file with 24 bands.
> I want to create a new (ASCII) grid with the bands aggregated.
> Is this possible using the gdal tools or with an existing
Hi list,
I have a netCDF file with 24 bands.
I want to create a new (ASCII) grid with the bands aggregated.
Is this possible using the gdal tools or with an existing python script?
Thanks,
Paul
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://
>
> If you feel strong about that, you can file a ticket in Trac about that. Your
> proposal makes sense, although I suspect there could be use cases where it
> wouldn't be desirable, but I can't find them right now...
Thanks. Now logged in trac, #5115
Graeme.
___
Hi all,
According to page http://www.gdal.org/ogr/ogr_sql.html , I found that <, >, <=
and >= operators are case sensitive. My code is something like this: and I
couldn't get the required result. Can anyone give me some suggestions?Thanks
for your help!
OGRFeature *pfea = OGRFeature::CreateFe
13 matches
Mail list logo
