[gdal-dev] Python Bindings

2010-07-26 Thread Jeff Hamann
I've built GDAL/OGR (1.7.2) with the following ./configure options $ ./configure \ CC="gcc -arch i386" \ CXX="g++ -arch i386" \ OBJC="gcc -arch i386" \ F77="gfortran -arch i386" \ FC="gfortran -arch i386" \ --with-pg=/usr/local/pgsql/bin/pg_config \ --without-macosx-framework \ --witho

[gdal-dev] Convert polyline to polygon

2010-07-26 Thread Paul Meems
I'm trying to convert a polyline shapefile into a polygon shapefile. The polylines are all sort of circular shaped. When the polyline is not closed and is not crossing itself it is easy to do. Just add the point of the polyline to the new polygon and add the first point as the last point to close t

[gdal-dev] Re: ogr2ogr OCI: problem loading shapes

2010-07-26 Thread Jukka Rahkonen
Sebastian E. Ovide gmail.com> writes: > > > You are right...aften done it, still getting the oringinal error due to errors in the geometries...now, If I import the same data using shp2sdo, I do NOT get any error creating the index... the shape get imported and the index is created... even if th

Re: [gdal-dev] Re: ogr2ogr OCI: problem loading shapes

2010-07-26 Thread Sebastian E. Ovide
You are right... aften done it, still getting the oringinal error due to errors in the geometries... now, If I import the same data using shp2sdo, I do NOT get any error creating the index... the shape get imported and the index is created... even if there are errors in the geometries... any ide

Re: [gdal-dev] Re: ogr2ogr OCI: problem loading shapes

2010-07-26 Thread Michael Smith
Sebastian, Looks like you didn¹t commit the change. There still is a duplicate entry in the user_sdo_geom_metadata. Delete From User_Sdo_Geom_Metadata Where Table_Name Like 'FLU%'; Commit; Mike -- Michael Smith US Army Corps of Engineers Remote Sensing/GIS Center Hanover, NH On 7/26/10 1

Re: [gdal-dev] Re: ogr2ogr OCI: problem loading shapes

2010-07-26 Thread Sebastian E. Ovide
ok... I have deleted that extra line manually (should not it be handled by ogr2ogr in some way?) Delete From User_Sdo_Geom_Metadata Where Table_Name Like 'FLU%'; now I'm getting another error: se...@seanspc:~/gdal$ time ogr2ogr -f OCI OCI:geoserver/geoser...@mfproduk_11g../shapes/Fluvial_Extent

Re: [gdal-dev] Re: ogr2ogr OCI: problem loading shapes

2010-07-26 Thread Sebastian E. Ovide
thanks for that... I'm getting closer se...@seanspc:~/gdal$ time ogr2ogr -f OCI OCI:geoserver/geoser...@mfproduk_11g../shapes/Fluvial_Extents/FluvialUD04Q200Outline.shp -lco srid=81989 -lco PRECISION=NO -progress -lco DIM=2 0...10...20...30...40...50...60...70...80...90...100 - done. ERROR 1:

Re: [gdal-dev] Re: ogr2ogr OCI: problem loading shapes

2010-07-26 Thread Rahkonen Jukka
Hi, http://gdal.org/ogr/drv_oci.html says: Layer Creation Options DIM: This may be set to 2 or 3 to force the dimension of the created layer. If not set 3 is used by default. Have you tried that? -Jukka- Sebastian E. Ovide wrote: On Fri, Jul 23, 2010 at 7:38 PM, Jukka Rahkonen wrote: > Val

Re: [gdal-dev] Re: ogr2ogr OCI: problem loading shapes

2010-07-26 Thread Sebastian E. Ovide
On Fri, Jul 23, 2010 at 7:38 PM, Jukka Rahkonen wrote: > Validate geometries validating geometries it came out: ORA-54668: a 2D SRID cannot be used with a 3D geometry therefore I've used the option -nlt POINT as suggested http://osgeo-org.1803224.n2.nabble.com/howto-flattening-of-3D-shapefiles-t

Re: [gdal-dev] exception, while creating large image

2010-07-26 Thread Tamas Szekeres
Do you have a sample data to reproduce this? Best regards, Tamas 2010/7/26 mail2vajram > > in my application i need to create multiple images with large size using > C#. > while creating multiple files first three images created successfully after > that i got the following exception. > > Con

[gdal-dev] exception, while creating large image

2010-07-26 Thread mail2vajram
in my application i need to create multiple images with large size using C#. while creating multiple files first three images created successfully after that i got the following exception. ContextSwitchDeadLock was detecteed The CLR has been unable to transition from COM context 0x204d28 to CO