Ticket #5 (closed enhancement: wontfix)

Opened 9 years ago

Last modified 7 years ago

ogr: GML_ID bei Fehlermeldungen ausgeben

Reported by: oknopp Owned by: warmerdam
Priority: major Milestone: 0.6 release
Component: ogr Version: 0.5
Keywords: Cc: frank.jaeger, frank.haertel@…

Description

Siehe auch #4

Change History

comment:1 Changed 9 years ago by astrid.emde

  • Version set to 0.5
  • Component changed from Karte to ogr
  • Milestone set to 0.6 release

comment:2 Changed 9 years ago by warmerdam

Waiting for specific example in #4.

comment:3 Changed 9 years ago by astrid.emde

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

comment:4 Changed 9 years ago by astrid.emde

  • Cc frank.jaeger, frank.haertel@… added
  • Owner changed from somebody to warmerdam

comment:5 Changed 9 years ago by 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/

comment:6 Changed 9 years ago by 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.

comment:7 Changed 7 years ago by j.e.fischer

  • Status changed from new to closed
  • Resolution set to wontfix

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.

Note: See TracTickets for help on using tickets.