Frank,
Sorry for the confusion. Please disregard my last message. I didn't had the
time to edit it properly.
But I am happy to see that the discussion has brought some interesting ideas
and some important concerns.
That is what I think we should do:
- Keep backward compatibility. Simple files
> Yes, my intention was to regularize how connection strings are done.
> So if applied to the postgres driver we would have stuff like:
>
> @driver=pg,host=localhost,password=tiger,dbname=ottawa
>
> What I don't like now is that the connection string parsing,
> quoting, etc is handled different
Hi,
The failing layer doesn't have a geometry column, it associates with another
view that contains the geometries. Would this cause error?
The ogrinfo returns the same error: "FAILURE: Couldn't fetch requested layer
'AIRWAY' "
Oracle user who created the view is the same as the ogr2ogr user, I
On Tue, Oct 4, 2011 at 11:42 AM, Even Rouault
wrote:
> That's exactly my understanding of what the latest patch
> http://trac.osgeo.org/gdal/attachment/ticket/3043/open_by_drivername_v3.patch
> does.
Even,
Good, but I didn't understand what Ivan was suggesting/proposing.
>> The main advantage o
Le mardi 04 octobre 2011 20:20:50, Frank Warmerdam a écrit :
> On Tue, Oct 4, 2011 at 6:58 AM, Ivan Lucena wrote:
> >> I believe that is because it is hard to know if HFA:test.tif was really
> >> something other than a request for the HFA driver. It could actually
> >> be a file named "HFA:tes
>
> I think we want a syntax that can easily be entered by a user at the
> command line, or in the text field of a desktop or web user interface.
> That definitely rules out exotic characters, and ideally we'd lean
> towards a simpler syntax.
For a desktop user interface, *ideally*, I think the u
On Tue, Oct 4, 2011 at 6:58 AM, Ivan Lucena wrote:
>> I believe that is because it is hard to know if HFA:test.tif was really
>> something other than a request for the HFA driver. It could actually
>> be a file named "HFA:test.tif" or it could be that another driver happens
>> to use the HFA:
On 11-10-04 10:56 AM, Chris 'Xenon' Hanson wrote:
My suggestion would be to look for a token that is NOT valid in a
conventional
file-path-name/URL/URI. I would also possibly place that token in the FIRST
string
character location for fast detection of this special condition without having
Hi all,
On Tue, Oct 4, 2011 at 9:58 AM, Ivan Lucena wrote:
> Frank,
>
>> ---Original Message---
>> From: Frank Warmerdam
>> To: Daniel Morissette
>> Cc: gdal-dev@lists.osgeo.org
>> Subject: Re: [gdal-dev] Resquest for comments (RFC 36)
>> Sent: Oct 03 '11 21:04
>>
>> On Mon, Oct
On 10/3/2011 6:02 PM, Ivan Lucena wrote:
> Hi All,
> RFC 36: http://trac.osgeo.org/gdal/wiki/rfc36_open_by_drivername
> The goal of RFC 36 is to save processing time by telling GDALOpen what driver
> to use, avoiding the driver-probing mechanism (Where all drivers are asked to
> checked if they r
Gdal_translate.exe -of KMLSUPEROVERLAY c:\my.tif c:\myResult.kmz -co FORMAT=PNG
From: gdal-dev-boun...@lists.osgeo.org
[mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Luisa Peña
Sent: Tuesday, October 04, 2011 9:22 AM
To: gdal-dev@lists.osgeo.org
Subject: [gdal-dev] Generating a Google Ear
Frank,
> ---Original Message---
> From: Frank Warmerdam
> To: Daniel Morissette
> Cc: gdal-dev@lists.osgeo.org
> Subject: Re: [gdal-dev] Resquest for comments (RFC 36)
> Sent: Oct 03 '11 21:04
>
> On Mon, Oct 3, 2011 at 6:14 PM, Daniel Morissette
> wrote:
> > I like the idea,
Greetings
I have a raster RGB image (Geotiff) and I want to create an image overlay
KML file to be seen on Google Earth. Is it possible to do this in GDAL? If
yes, how ?
Thanks
Best regards,
Luisa
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http:/
Hi Jukka,
That is a very important concern, you could try the path on your machine so
that we can make sure. But I believe that because the functions does not strip
the driver name from the oOpenInfo.pszFilename, when it fails and go back to
the original code, it will also fails because no driv
Hi Even.
Thanks, using single-quotes around the fully qualified table name solved it.
But I cannot use a where clause... it always results in an error. I have tried
everything I could remember: single quotes, double-quotes, fully qualified
field name, quotes and double-quotes on the value... no
15 matches
Mail list logo