Skip to main content
Released

PostGIS Reader should handle multiple geometry columns in a table

Related products:Integrations
  • June 24, 2016
  • 12 replies
  • 296 views

I store multiple geometry columns in a single table. I'd like to be able to use the PostGIS Reader to decide which geometry I'd like to pull out and transform.

12 replies

ponceta
Contributor
Forum|alt.badge.img+7
  • Contributor
  • August 13, 2018

+1 Handling multiple geometries is a need.

I've encountered a bug when dealing with Postgis mutliple geometries table which requires to specify which geometry is taken into account, otherwise FME loses geometry :

https://github.com/qwat/qwat-data-model/issues/265


revesz
Supporter
Forum|alt.badge.img+22
  • Supporter
  • August 14, 2018

This may help:

https://knowledge.safe.com/articles/24702/handling-data-that-contains-multiple-geometry-colu.html

However yes, a more intuitive way would be greatly appreciated by many of us.


Forum|alt.badge.img+2

rbell
Contributor
  • Contributor
  • April 1, 2022

One of the advantages of PostGIS is that it can handle multiple geometry columns in the same table. For example and a polygon area of interest, then the gradual erosion of that AOI which regard to image collection, etc. Should not have to choose one or the other, in my opinion.


t_hohenstrater
Contributor
Forum|alt.badge.img+2

I now too have this challenge whereby the table holds multiple geometries. Coming from Oracle Spatial and seeing how easy it works with FME I was surprised Safe has not implemented the same for PostGIS


winkel_tripel
Contributor
Forum|alt.badge.img+1

I realise this idea relates to the PostGIS Reader, but it would also be good if PostGIS Writer could write to multiple geometry columns.

I tried the workaround at https://community.safe.com/s/article/template-write-multiple-geometry-types-to-an-exist, but writing the second geometry column is extremely slow, as bulk insert for this writer is switched off during translation (the following warning message is received):

POSTGIS Writer: Bulk Insert is set to Yes, but a conflicting Feature Operation has been detected. Feature type 'rc_srb.srb_01' has a Feature Operation of 'Update'. Bulk Insert is now being set to No, which can cause insert operations to be much slower

As a result, the timings for writing a dataset of 130,000 features is as follows:

  • 1st geometry column – 1 minute
  • 2nd geometry column – 42 minutes

LizAtSafe
Safer
Forum|alt.badge.img+25
  • Safer
  • February 10, 2024
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

LizAtSafe
Safer
Forum|alt.badge.img+25
  • Safer
  • December 27, 2024
OpenGathering Interest

LizAtSafe
Safer
Forum|alt.badge.img+25
  • Safer
  • May 12, 2026
Gathering InterestIn Development

LizAtSafe
Safer
Forum|alt.badge.img+25
  • Safer
  • September 15, 2026
In DevelopmentReleased

andreaatsafe
Safer
Forum|alt.badge.img+17
  • Safer
  • September 15, 2026

Hi all,

In FME 2026.3, I’m pleased to let you know that the PostGIS Reader and Writer now handle multiple geometry natively.

For more details on how to work with multiple geometry, please check out this article here.


arthur_bazin
Contributor
Forum|alt.badge.img+19
  • Contributor
  • September 16, 2026

Hi ​@andreaatsafe, that’s a wonderfull news !

Will try it ASAP

Thanks