Perhaps GDAL_PROXY?
-
From: "Even Rouault"
Subject: Re: [gdal-dev] GDAL RPC protocol to make GDAL (more) failsafe
Date: 06 פברואר 2013 03:16
Sent by emoze push mail
Le mercredi 06 février 2013 01:59:46, David Shean a écrit :
> This sounds great. I'm guessing RPC in
Le mercredi 06 février 2013 01:59:46, David Shean a écrit :
> This sounds great. I'm guessing RPC in this context stands for "Remote
> Procedure Call." It seems like this could potentially lead to some
> confusion with existing GDAL functionality (e.g., gdal_rpc.cpp) and
> options (e.g. RPC_DEM)
Even,
This sounds great. I'm guessing RPC in this context stands for "Remote
Procedure Call." It seems like this could potentially lead to some confusion
with existing GDAL functionality (e.g., gdal_rpc.cpp) and options (e.g.
RPC_DEM) where RPC stands for "Rational Polynomial Coefficients" use
Hi,
Just to inform you that I've just commited in trunk a new feature.
See http://trac.osgeo.org/gdal/ticket/4979 :
"""
When dealing with some file formats, particularly the drivers relying on third-
party (potentially closed-source) libraries, it is difficult to ensure that
those third-party l
Le mercredi 06 février 2013 00:05:35, Brett Walker a écrit :
> Hi Richard,
>
> After further investigation I suspect that it is the configuration of my
> Linux box. It reports that it is GPX enabled but after adding an XML
> header () to the file it reported
> that it cannot find the expat library
Hi Richard,
After further investigation I suspect that it is the configuration of my Linux
box. It reports that it is GPX enabled but after adding an XML header () to the file it reported that it cannot find
the expat library. This is more informative that the error message I posted the
other d
Chris English writes:
> Just to close this out,
> New York New Jersey FEMA advisory Base Flood Elevations are ESPG:3857
I don't follow. EPSG:3857 seems to be 'web mercator', which is a 2D
coordinate system and thus cannnot have height. The string you sent
before had a navd88 height for the ve
Just to close this out,
New York New Jersey FEMA advisory Base Flood Elevations are ESPG:3857
> From: sgl...@hotmail.com
> To: g...@ir.bbn.com; gdal-dev@lists.osgeo.org
> Date: Sat, 2 Feb 2013 11:39:23 -0500
> Subject: Re: [gdal-dev] Fema Flood Maps NAV88 - proj4text
>
>
> The parcels are, o
Selon Stephen Woodbridge :
> Hi All,
>
> Does OGR have support for MongoDB?
>
> I would like to be able to issue a query and pull points and attributes
> into a mapserver layer. MongoDB actually has some basic spatial support
> built into it.
>
> Any thoughts on how to do this?
Yes, write the dri
Hi All,
Does OGR have support for MongoDB?
I would like to be able to issue a query and pull points and attributes
into a mapserver layer. MongoDB actually has some basic spatial support
built into it.
Any thoughts on how to do this?
Thanks,
-Steve
OK..I figured it out that the layername is not the layer object,
it is the name property of the layer object and has to be enclosed
in double quotes.
For example:
test = ds.ExecuteSQL('select * from "three_points" where Class IN (1,3)
') #returns 2 of 3 point features
http://www.gdal.org/ogr/og
> What could be wrong? What to look for? How to solve this problem?
If you look at the file with a text editor, does it look like a XML file with a
element ? If so, you can open a ticket in GDAL Trac with the file attached
for investigation.
>
> Brett
>
> Brett Walker
> mailto:brett.wal...@geom
Selon David Verbyla :
> I am trying to figure out the syntax for .ExecuteSQL using Python ogr.
>
> For example:
> fireLayer.SetAttributeFilter(None) #returns all 2623 polygons
> fireLayer.SetAttributeFilter(" FIREID < 75 ") #returns 4 polygons
>
> I am trying to get the same results using the Exec
Dave,
Try the following modified version of your code snippet below. Note
that `ExecuteSQL` expects a simple SQL string - it does not do any
interpretation of local python variables! See
http://www.gdal.org/ogr/ogr_sql.html for more information on the SQL.
import os
from osgeo import ogr
Hello Dave,
On Mon, Feb 04, 2013 at 06:32:11PM -0900, David Verbyla wrote:
> I am trying to figure out the syntax for .ExecuteSQL using Python ogr.
I have successfully been using `DataSource.ExecuteSQL` from Python
using gdal 1.9.0.
> For example:
> fireLayer.SetAttributeFilter(None) #returns al
Le mardi 5 février 2013 15:14:16 Brett Walker a écrit :
> HI,
>
Hello Brett,
> I have compiled GDAL/OGR with support for GPX files. 'ogrinfo -formats'
> reports '-> "GPX" (read/write)'. This I take as being good that GPX
> support is enabled.
>
> When I run the following command: 'ogrinfo -ro
16 matches
Mail list logo
