Casting to MultiPolygon and MultiPolyLine from "untyped" formats

[lpercich]

I'm having problems when inserting MapInfo data into a PostgreSQL table with a MultiPolygon or MultiPolyLine geometry column.

MapInfo has no geometric typing at the schema (column) level (i.e. the geometric column type in MapInfo is always "GEOMETRY"); nor it makes distinction at the programmatic or data model level between Polygons and Multipolygons, or PolyLines and MultiPolyLines. Thus when reading a "MultiPolygon" MapInfo layer in OGR, the one-ring poligons will be read as Polygons, and not as one-element MultiPolygons.

---

I don't know if other formats have the same limitation with geometric typing. The best solution anyway could be adding a -lco TO_MULTI=ON|OFF to force casting single geometries into collections of one geometry. (More than a -lco this is related with the source format)

As a workaround, I'm generating SQL with WKT through PGDump format, and processing it with sed:

sed -r 's/;(POLYGON|LINESTRING)[ ]*\(([\(\)0-9,\. ]+)\)/;MULTI\1 ((\2))/' "$sqlsingle" >> $sqlmulti

which is faster than inserting into an untyped geometry temp PG table, updating with multi(geom) and inserting into the final table.

[lpercich]

Generating a PG Dump from a MapInfo table containing polygons and multipolygons

[Even Rouault]

Did you try the -nlt MULTILINESTRING or -nlt MULTIPOLYGON options of ogr2ogr ? It looks like it is what you need

[lpercich]

Replying to rouault:

Did you try the -nlt MULTILINESTRING or -nlt MULTIPOLYGON options of ogr2ogr ? It looks like it is what you need

Yes, you are right! I just tried it with PGDump and PostGIS driver, works fine both when creating the layer and when appending to an existing layer of the appropriate type. I will RTMT (Read the manual... TWICE!)

In this case, shall I close the ticket? Or will you do it?

Thanks for your patience

Sig