Fishy Polygon file conversion behavior

[darkblueB]

Run ogr2ogr to convert a trivial polygon from KML to something else

varying results, including outright failure (eg operation not completed)

However, ogrinfo on the same KML source shows a well-defined polygon

hence the title "fishy", where is the error, in the KML driver ? maybe

examples I used were GML output (very similar output to the KML input) SQLite "known to have shortcomings" re crschmidt PostgreSQL - the clincher, because the same test DB target accepted a

15,000 polygon layer from a Shape file, but fails on this test

[warmerdam]

Brian,

Could you paste in the error you get so we know when we have hit the same problem?

Flipping to Mateusz to address...

[darkblueB]

PostgreSQL: set up a new PG database, add the plpgsql language and execute file lwpostgis.sql (sp?). Attempt to import the file Polygon.kml with ogr2ogr. Observe the error:

ERROR 1: CREATE TABLE Polygon."kml" ( OGC_FID SERIAL, CONSTRAINT "kml_pk" PRIMARY KEY (OGC_FID) ) ERROR: schema "polygon" does not exist

SQLite: import Polygon.KML to SQLite. ogrinfo on the SQLite result shows a polygon. However, my SQLite viewer 'SQLite Database Browser 1.3' shows the table with the CREATE string, but no contents? something is confusing the viewer...

[darkblueB]

PG continued- In an attempt to make sure I was not missing a step with PG, I executed the query from the PostGIS instructions page which makes a new table with a SpatialGeometry column: CREATE TABLE gtest ( ID int4, NAME varchar(20) );

SELECT AddGeometryColumn(, 'gtest','geom',-1,'LINESTRING',2);

this worked fine, as expected.

Later, I imported with ogr2ogr a stock Shape file I use for many tests, about 15,000 polygons. Import worked fine the first time.

[Even Rouault]

The following works for me :

ogr2ogr -f GML polygon.gml polygon.kml; ogrinfo -ro -al polygon.gml
ogr2ogr -f SQLITE polygon.sqlite polygon.kml; ogrinfo -ro -al polygon.sqlite 
ogr2ogr -f PostgreSQL PG:dbname=test polygon.kml -nln polygon;  ogrinfo -ro -al PG:dbname=test polygon

Note the -nln for the PG case because the KML layer name is "polygon.kml" which is interprated by the PG driver as beging a schema.table name, but I have no "polygon" schema ... It might be that your 'SQLite Database Browser 1.3' doesn't like "polygon.kml" as a layer name either. -nln could also be useful in that case.