I loaded a Geodatabase with FME into Postgis recently. The data were polygons. <\/p>\n\n\n\n
After loading I noticed it was taking a long time for the connection to be made, there were a lot of errors which isn’t that unusual due to some of the data originally coming from CAD and doesn’t meet OGC requirements.<\/p>\n\n\n\n
That was not all though, there was something else going on with these data. I ran check geometry and ST_IsValid which told me that there were a whole lot of Ring Self-Intersection errors as expected.<\/p>\n\n\n\n
Using this query:<\/p>\n\n\n\n
SELECT ST_GeometryType(geom) as geomtype
FROM public.\"MyTable\"
group by geomtype
<\/pre>\n\n\n\nI found that the database had stored 4 kinds of geometry:<\/p>\n\n\n\n
“ST_CurvePolygon”
\n“ST_MultiPolygon”
\n“ST_MultiSurface”
\n“ST_Polygon”<\/p>\n\n\n\nThis was surprising because the source was a File Geodatabase and should only have one type of geometry, which should store as ST_MultiPolygon. <\/p>\n\n\n\n
I am not sure if FME recreated these geometries or if the File Geodatabase itself was a geometry collection.<\/p>\n\n\n\n
Additionally, using the Database Manager tool in Qgis, the table would not load as there were too many errors, that I think were QGIS enforcing the single geometry datatype.<\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n<\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"I loaded a Geodatabase with FME into Postgis recently. The data were polygons. After loading I noticed it was taking a long time for the connection to be made, there were a lot of errors which isn’t that unusual due to some of the data originally coming from CAD and doesn’t meet OGC requirements. That … Continue reading Multiple Geometries in database checking<\/span>