Hi GDAL-dev,
I've recently re-compiled GDAL from the trunk after the patch to fix UTM ozi
files was applied. This has worked well for most UTM files I've tried so far,
but I've come across one that produces a strange error in my code, but works OK
with gdalinfo. The following code fails for a
Eli - thanks a bunch for mentioning the .bat file - that got Oracle support
working!
I really should have seen that, and the read-me in the same directory
telling me to run it... I've just got into a routine of getting the
binaries, testing with the same commands, and being disappointed.
This may
On Tue, Nov 27, 2012 at 5:04 PM, cheesybiscuits
wrote:
> Jukka - Thanks for the suggestion. I have extracted the contents of
> release-1600-gdal-mapserver.zip ("Compiled binaries in a single .zip
> package" ) which seems to include the Oracle plugin (gdal_GEOR.dll and
> ogr_OCI.dll).
>
>
Typically
Nicolas - thanks for your input but I have only ever tried to build with the
plugin enabled. The OCI format is not listed in gdalinfo.
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/Absolutely-no-progress-trying-to-compile-GDAL-with-Oracle-support-on-Windows-tp5018926p5019
Jukka - Thanks for the suggestion. I have extracted the contents of
release-1600-gdal-mapserver.zip ("Compiled binaries in a single .zip
package" ) which seems to include the Oracle plugin (gdal_GEOR.dll and
ogr_OCI.dll).
However OCI is still not listed in gdalinfo --formats, and running my
origin
Le mardi 27 novembre 2012 09:28:06, Jukka Rahkonen a écrit :
> Even Rouault mines-paris.org> writes:
> > There was indeed something wrong in the way the layer name was written
> > for the model tree, which caused invalid PDF structure to be generated
> > when there were spaces (and potentially non
Le mardi 27 novembre 2012 17:20:00, Travis Kirstine a écrit :
> Hi all,
>
> Is there any way to extract other information besides name, description and
> geometry from a kml file using the ogr kml driver (libexpat).
... no
> I'm
> specifically looking to get the placemark snippet.
>
> Unfortun
Le mardi 27 novembre 2012 20:35:11, Tyler Mitchell a écrit :
> Just curious why the following two (seemingly similar) approaches using OGR
> Python access act differently. Should it act that way?
http://trac.osgeo.org/gdal/wiki/PythonGotchas ...
>
> This works:
> ...
> f1 = lay1.GetFeature(1)
Just curious why the following two (seemingly similar) approaches using OGR
Python access act differently. Should it act that way?
This works:
...
f1 = lay1.GetFeature(1)
g1 = f1.GetGeometryRef()
g1.ExportToWkt()
This seg faults:
...
g1 = lay1.GetFeature(1).GetGeometryRef()
g1.ExportToWk
Hi all,
Is there any way to extract other information besides name, description and
geometry from a kml file using the ogr kml driver (libexpat). I'm
specifically looking to get the placemark snippet.
Unfortunately I cannot use LIBKML, I'm restricted to the elgis repo
Thanks
___
Hello,
Could should try gdalinfo --formats ?
It will shows you if OCI driver was correctly included in the build.
If it's not the case, may be you should force a new rebuild with these
commands
nmake -f makefile.vc clean
nmake -f makefile.vc
nmake -f makefile.vc install
I
Thanks for all of your responses...
we're a trying some of your suggestions, using some tools to accomplish
this task.
I think we're close enough now. (the polygon shapefile is almost correctly
generated from a shape with a bunch of lines which compose closed
boundaries of polygons).
On Mon, Nov
Even Rouault mines-paris.org> writes:
>
> There was indeed something wrong in the way the layer name was written for
> the
> model tree, which caused invalid PDF structure to be generated when there
> were
> spaces (and potentially non-alphanumeric characters) in the layer name. This
> sho
13 matches
Mail list logo
