The OGDI source builds a bit of a broken library for OS X (library name, endian
problem, plugin naming problem). See the OS X build notes on my site for
patches and info to get something useable.
On Sep 23, 2010, at 8:04 PM, Jeshua Lacock wrote:
>
>
> Greetings,
>
> Is gdal 1.7.2 supposed t
Greetings,
Is gdal 1.7.2 supposed to be compatible with OGDI 3.2 beta 2?
I am getting the following (I tried making a symbolic link from my
libogdi.dylib to libogdi31.dylib:
configure:18511: result: no
configure:18530: checking for cln_GetLayerCapabilities in -logdi31
configure:18555: gcc -o
Frank:
Thanks for the reply. I tried again with"
strcat(connectBuf, "PG:dbname='postgis' host='' port='5432'
user='postgres' password='>Pwd>'");
*dataSource = OGRSFDriverRegistrar::Open(connectBuf
/*connectString.c_str() */, FALSE);
And still no connection and *dataSource was returned NULL.
Clay, Bruce wrote:
I can not connect to a posgresql/postgis database using GDAL. I have
verified that the PostgreSql drivers are in the DLL by calling ogrinfo
–formats.
PostgreSql is on the list
From c++ code I try the following:
strcat(connectBuf, "PG:\"dbname='postgis' host='user='
I can not connect to a posgresql/postgis database using GDAL. I have
verified that the PostgreSql drivers are in the DLL by calling ogrinfo
-formats.
PostgreSql is on the list
From c++ code I try the following:
strcat(connectBuf, "PG:\"dbname='postgis' host=' user=postgis password=
dbname
No, you must not write CETAG = 'GEOLOB', ... as the value of the TRE. You must
really format the TRE byte by byte, without any separator or field name,
according to its documentation.
gdal_translate -of NITF foo.tif foo.ntf -co
"TRE=GEOLOB=073932800080076800-096.9774560321+045.1446198929"
Le j
Even, thanks for responding. The ultimate goal is to serve up NITFs via
MapServer. So if we need to specify a TRE option, we would need to define it
in the mapfile.
Still, this is a good lead. Do you have any guidance on exercising this from
the command-line?
gdal_translate -of NITF -co TRE=GE
Tamas Szekeres wrote:
>
> Count me as a "new" committer as I've also done some changes in this
> part, however bug has also been added with these changes at
> http://trac.osgeo.org/gdal/ticket/3687 ;-) We may indeed forget to
> duplicate this into the other BugTracker which would require a more
>
2010/9/23 Daniel Morissette
>
> Updates have to be committed upstream, ideally by submitting a ticket at
> http://bugzilla.maptools.org/ ... eventually I should open the MITAB CVS
> repository to more GDAL committers to facilitate this process.
>
> I have to admit that as new GDAL committers have
Ivan Lucena wrote:
We can always have 1.10 and 1.11 etc. That would not be uncommon (there
is for example Perl 5.10 as we're waiting for Perl 6). However, I'm for
I like that.
Folks,
Well, I hate two digit releases, and they confuse the versioning
in stuff like OSGeo4W. Not a compelling r
> ---Original Message---
> From: Ari Jolma
> To: gdal-dev@lists.osgeo.org
> Subject: Re: [gdal-dev] GDAL/OGR 2.0 Notes
> Sent: Sep 23 '10 09:04
>
> On 09/22/2010 09:52 PM, Frank Warmerdam wrote:
> > Folks,
> >
> > In IRC I was just mentioning to Howard that we might want to drop
Tamas Szekeres wrote:
>
> I don't think we extensively use filenames and URLs in the style strings
> however we may indeed consider the dot '.' as a reserved char for
> example in the parameters which could be a float value in the style
> strings. In such sense the comma ',' could also be a charac
It is true that the driver doesn't write automatically the GEOLOB TRE, but you
can manually do it by using the TRE creation option of the NITF driver. See
http://gdal.org/frmt_nitf.html and http://gdal.org/frmt_nitf_advanced.html.
This will require you to format it "at hand" properly from the ge
Daniel,
I don't think we extensively use filenames and URLs in the style strings
however we may indeed consider the dot '.' as a reserved char for example in
the parameters which could be a float value in the style strings. In such
sense the comma ',' could also be a character which already used a
(Cross-posted to mapserver-dev)
Okay, I finally found traces of the previous discussions on this topic
in one GDAL ticket, and a related MITAB bugzilla entry:
http://trac.osgeo.org/gdal/ticket/3571
and
http://bugzilla.maptools.org/show_bug.cgi?id=2206
Tamas and I would have saved lots of time
ahmet,
Perhaps the python script rgb2pct.py can help you. ( Refer to
http://www.gdal.org/rgb2pct.html & http://www.gdal.org/gdal_utilities.html )
PS: You can easily set some fancy color tables using some desktop GIS
applications.
On Thu, Sep 23, 2010 at 5:48 PM, ahmet temiz wrote:
> I learnt l
Hi Tamas,
I remember that I discussed with other devs this a little while ago, I'm
just not sure if that was on the list or on IRC... however I'm a bit
surprised since I see that r19724 was done by winkey and I thought I had
this discussion with aboudreault, so I'll need to dig a bit further to
re
On 09/22/2010 09:52 PM, Frank Warmerdam wrote:
Folks,
In IRC I was just mentioning to Howard that we might want to drop use of
CPL_STDCALL in the GDAL API if a 2.0 release ever occurs. It seemed
to me
that such ideas ought to be kept track of so off the "Developer"
section of
the Trac wiki I
Just wanted to confirm. NITFs potentially store location data in 2 places.
IGEOLO and GEOLOB. But GEOLOB has more accuracy (more decimal places).
There was a ticket which modified the NITF driver to read GEOLOB (if
present),
http://trac.osgeo.org/gdal/ticket/3180
But the NITF driver does not w
Hi,
I was curious about the new gdal klmsuperoverlay driver
(frmts/kmlsuperoverlay). I have installed minizip, and ran make in the
frmts/kmlsuperoverlay folder, which resulted in a
kmlsuperoverlaydataset.o. Now what? How would I incorporate this into my
gdal lib, either internally or as a pl
I learnt later. This color file should be created by myself.
I had asked if there was any automatic way of generation of that file
as in "GMT makecpt"
regards
2010/9/23 Chaitanya kumar CH :
> ahmet,
>
> The gdaldem color-relief utility uses the color entries from a text file
> which is given a
hello
I have two tif maps. One is mask, the other is DEM.
as usual, I want to trim the part of DEM which is out of this mask.
how can I do that ?
regards
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-
22 matches
Mail list logo
