ogr: GML_ID bei Fehlermeldungen ausgeben

[oknopp]

Siehe auch #4

[warmerdam]

Waiting for specific example in #4.

[astrid.emde]

• we create the databaseschema with the SQL ​https://trac.wheregroup.com/PostNAS/browser/trunk/data/konvert/postnas_0.5/alkis_PostNAS_0.5_schema.sql?rev=90
• When I import the sample-data (​https://trac.wheregroup.com/PostNAS/attachment/ticket/11/NBA_RIO_20110430T000000_0von0_0_0.xml), I get two warnings, but I do not know, which object they refer to:

Warning 1: Geometry to be inserted is of type Polygon, whereas the layer geometry type is Multi Polygon.
Insertion is likely to fail
Warning 1: Geometry to be inserted is of type Polygon, whereas the layer geometry type is Multi Polygon.
Insertion is likely to fail

• it would be good to add the SQL for the objects that make problems to the logfile too

[astrid.emde]

we worked on the database schema and changed column lage to character varying(5). The new SQL is at the following location:

​https://trac.wheregroup.com/PostNAS/browser/trunk/data/konvert/postnas_0.6/alkis_PostNAS_0.6_schema.sql

It does not work with gdal 1.8 but with gdal > 1.8 (you can download the sources (​http://svn.osgeo.org/gdal/trunk/gdal) and compile gal. Have a look at [BuildingOgrPostNASDriver].

You get nightly builds at: ​http://vbkto.dyndns.org:1280/sdk/

[warmerdam]

The warning is produced by the OGR PostGIS driver. It compares the geometry type being inserted with the geometry type declared for the geometry column in the geometry_columns table. If you can ensure that the geometry type constraint is dropped and alter the setting in the geometry_columns table to declare the geometry as being any kind of geometry then the warnings will go away.

Unfortunately it is not easy to report the gml_id of the feature in the PostGIS driver as it does not know this as a special attribute. Only the in the NAS driver do we have the context to realize this is a good way to report on the feature but by the point the feature has been handed off to the postgis driver we lose that context.

So I think you can adjust how you setup the schema (and geometry_columns entries). I cannot see anything I can practically do within OGR.

[j.e.fischer]

I guess we can close this - the NAS driver now reports the gml_id when it detects some NAS specific internal problems.

But as this one is because the NAS driver doesn't know where ogr2ogr loads the data to we'd probably need a ogr2ogr independant importer to get a handle on this - and that's very unlikely to happen.