Changes between Version 26 and Version 27 of GDAL20Changes


Ignore:
Timestamp:
01/02/13 04:56:06 (12 years ago)
Author:
Even Rouault
Comment:

Add section "Expose shapefiles of type Polygon as MultiPolygon (LineString as MultiLineString) ?"

Legend:

Unmodified
Added
Removed
Modified

  • GDAL20Changes

    v26 v27  
    9696RFC23 has left some users unhappy, particularly with how encoding management is done with shapefiles. There are quite a few tickets on that issue and in #4808 a patch is proposed so that OGR drivers report their source encoding ( OGRLayer::GetEncoding() ). RFC23 should be amended if this approach was accepted.
    9797
     98== Expose shapefiles of type Polygon as MultiPolygon (and LineString as MultiLineString) ? ==
     99
     100The OGR Shapefile driver expose a layer geometry type Polygon, even if the shapefile contains multipolygons. This causes issues when converting such shapefiles with ogr2ogr to formats that have strict geometry type checking (PostGIS, Spatialite, etc...). A possibility would be to expose a layer geometry type MultiPolygon, and automatically promote single part polygons as multipolygons.
     101
     102The issue is discussed in #4939.
     103
    98104== Housekeeping issues ==
    99105
    … …  
    134140 * #4620 - OGRPGTableLayer does not check for bUpdateAccess in CreateField
    135141 * #4808 - [PATCH] Shapefile: interpreting LDID/87 not as ISO-8859-1 but as no codepage specified
     142 * #4939 - shapefile to postgresql : ERROR: Geometry type (MultiPolygon) does not match column type (Polygon)