OK Sebastian,
I will take a look on that later on.
Regards,
Ivan
> ---Original Message---
> From: Sebastian E. Ovide
> To: Ivan Lucena
> Cc: gdal-dev
> Subject: Re: [gdal-dev] Re: ogr2ogr OCI: problem loading shapes
> Sent: Jul 27 '10 07:06
>
&g
Hi Ivan
Do you think you can write a bug report on GDAL track so I can take a look
> on that problem?
>
> It looks like I am going to need a copy of one of your Shapefile sets
> (.shp, .dbf, etc.) to debug that problem.
> --
>
sure,
http://trac.osgeo.org/gdal/ticket/3698
I have attach a shape f
so with shp2sdo there is one row that is not loaded into the table:
Record 28832: Rejected - Error on table SEBAS, column GEOM.SDO_ORDINATES.
element count is greater than maximum allowed for the column
Table SEBAS:
28891 Rows successfully loaded.
1 Row not loaded due to data errors.
0 Rows
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
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
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
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
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:
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
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
Sebastian E. Ovide gmail.com> writes:
>
> ORA-13034: Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY
objectORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 10
> in CREATE INDEX "OSI_15101" ON FLUVIALUD04Q75OUTLINE("ORA_GEOMETRY")
INDEXTYPE IS MDSYS.SPATIAL_INDEXreal 1m25.698suser
11 matches
Mail list logo
