Hello list,
Just observed a puzzling behaviour of the netCDF driver. When creating a
netCDF dataset of Byte type, the netCDF driver seems to interpret the
nodata value as a signed byte.
For example a nodata value assigned with -a_nodata 200, will become -56.
Of course one can work around this
Le lundi 26 octobre 2015 22:35:48, David Adler a écrit :
> I'm getting closer after installing the MS compiler for Python and
> running "python setup.py build" successfully but still get a failure.
>
> Does the usual GDAL Python user need to go through all this? I see lots
> of information and tut
I'm getting closer after installing the MS compiler for Python and
running "python setup.py build" successfully but still get a failure.
Does the usual GDAL Python user need to go through all this? I see lots
of information and tutorials about using the GDAL Python API but haven't
found much a
Le lundi 26 octobre 2015 20:32:12, David Adler a écrit :
> Thank you for the quick response.
>
> I've not used Python before so I'm stumbling getting the environment to
> work. Python 2.7 is installed and I am running from the autotest
> directory. It isn't obvious to me how the PYTHONPATH variabl
Yes, I understand this. Namespaces use can go a long way to prevent loss of
source information while presenting information in the new target format. It
can be verbose, though.
Original message
From: Damian Dixon
Date: 26-10-2015 3:04 PM (GMT-05:00)
To: Tim Crook
Cc: dou
Thank you for the quick response.
I've not used Python before so I'm stumbling getting the environment to
work. Python 2.7 is installed and I am running from the autotest
directory. It isn't obvious to me how the PYTHONPATH variable is
supposed to be set, but I pointed it to the python directo
My thoughts on an XML encapsulation of metadata would be (I'll leave the
exact layout and details to the experts):
name of product
vpf/shape etc...
Problems I can see with this:
- Should the data wrap the product?
- How do you encapsulate XML
Le lundi 26 octobre 2015 19:11:02, Miller, Doug a écrit :
> Even,
>
> Thanks for the response. How is that set programmatically? Is it with
> CPLSetConfigOption?
Yes
>
> Thanks,
>
> Doug
>
> From: Even Rouault
> Sent: Monday, October 26, 2015 1:28 PM
Le lundi 26 octobre 2015 18:48:47, David Adler a écrit :
> I am close to finished with this driver which was delayed significantly
> getting access to a DB2 for z/OS test environment to verify that it
> works across IBM DB2 platforms.
>
> What is the proper way to handle authorship in the source c
I am close to finished with this driver which was delayed significantly
getting access to a DB2 for z/OS test environment to verify that it
works across IBM DB2 platforms.
What is the proper way to handle authorship in the source code? The DB2
driver is based on the MS SQL driver with signific
Doug,
you might try defining the RPFTOC_FORCE_RGBA envirnoment variable/config option
to YES. This should avoid GDALOpen'ing all the tiles at dataset creation.
However the presence of all tiles will be checked via a 'stat' call, which can
still be a potential bottleneck. That could probably be
When retrieving a sub dataset from GDAL using GDALOpen() and expressing the
file path as "NITF_TOC_ENTRY:CADRG_TLM50_50K_2_18:C:/rpf/a.toc " there is a
considerable delay. This delay is acceptable if the RFP's coverage is for the
United States, but if the coverage is for the world then it bec
Yes, it had occurred to me that XSLT would be a flexible way of handling a lot
of the metadata mappings.
From: Damian Dixon
Sent: Monday, October 26, 2015 8:36 AM
To: Tim Crook
Cc: doug_newc...@fws.gov ; gdal dev
Subject: Re: Follow on to the "ISO Metadata" post
Hi Tim,
Personally I would no
Hi Tim,
Personally I would not use ISO 19115-1 as an internal format.
There are not a huge number of data formats/products that store metadata as
XML out of the box. When they do store metadata it is usually specific to
the data and data product (regardless of how the metadata is stored).
There
Hi all,
For the head of svn trunk
Anyone have use cases that only work with the old PCIDSK driver? If so,
let me know and I'll see if I can add some documentation. Otherwise, I
propose removing the old driver and the autoconf/make tests and
conditionals that support it.
https://trac.osgeo.
Sorted this out myself.
The problem was the "type" property of "element" elements in
DescribeFeatureType. It was not recognized by GDAL. GDAL makes them ok,
but for PostgreSQL data sources I'm using Perl database tools and
obviously need to pay a bit more attention to setting the type.
Ari
Hi,
I'm developing a WFS server in Perl based on GDAL (i.e., GDAL is
generating the GML the server sends to the client) and I'm testing it
using the GDAL WFS client.
I'm obviously ignorant on some basic issues since I'm getting an error
"Cannot insert feature because we didn't manage to pars
17 matches
Mail list logo
