When I use single quotes, I get no errors, but instead I get returned the
column name = FIELD_1, and all values = column.name.one
I'm using the ExecuteSql() on a WFS datasource, so it might be the WFS driver
which causes the undesired FIELD_1 result.
>Odd-Ragnar<
-Original Message-
From
On 10/4/12 11:10 PM, Etienne Tourigny wrote:
Hi list,
I would like to know if the overview resampling methods listed on help
pages are really up-to-date, because I found some discrepancies in the
docs and code:
- gdaladdo utility page / http://www.gdal.org/gdaladdo.html
nearest,average,gauss,
Just letting folks know that we've released an OGR wrapper for the
Triangle library. It would be great if folks could test it. I could
also use some help improving the OGR bits.
Cheers,
THK
https://bitbucket.org/keittlab/meshpoly
--
Timothy H. Keitt
http://www.keittlab.org/
FYI
I have created a QGIS plugin "Tile Index Viewer" (in the official
plugin repos, still marked as experimental)
This plugin can show a raster preview of the tiles on the canvas, and
also load rasters from selected tiles
1) using contextual menu on the map canvas
2) using theTileIndex plugin me
Thanks, I just noticed that when I pulled the code to a new machine.
I've renamed the repository to
https://github.com/lukeroth/gdal_go to avoid the problem.
Luke
On Thu, Oct 4, 2012 at 12:57 AM, minux wrote:
>
> On Oct 4, 2012 2:46 AM, "Luke Roth" wrote:
>> set of GDAL bindings for the Go langu
Hi,
You haven't said which platform and binding/command line you are using.
In linux command line you would probably replace "." with "\."
Also column name should probably enclosed in quotes, not brackets.
Etienne
On Thu, Oct 4, 2012 at 8:29 AM, Odd Ragnar Lydersen
wrote:
> Is it possible to
Is it possible to make OGRDataSource:: ExecuteSQL() to work with a column name
containing "."?
Here is an example:
select column.name.one, column.name.two from 'wfs:layerName'
I have tried to enclose the column name in [] brackets, but that was invalid as
well.
Any ideas on how to get around th
Hey Simon,
I took a quick look out of curiosity. Regarding your second grid, and first
call:
If you run gdalinfo on the input .asc file, you can see that the coordinate
system is not recognized properly. You say its geographic so you can first
do this additional step to manually assign it:
gdal