Skip to main content
Question

Problems using postgis reader/writer

  • April 5, 2019
  • 4 replies
  • 24 views

Forum|alt.badge.img

So I'm having a bit of an issue using the fme postgis reader/writer combo. I have a big model that works perfectly using shapefiles (with some adaptations) or using esri gdb. The thing is that I'm trying to only use postgis as entry files and output files. The entry files arepolylines and the output files are polygons. The issue is with the ouput. The input of polylines from postgis seams to affect the ouput.

1. Shapefile reader: No problem

2. .gdb reader: No problem

3. postgis reader: polygons are converted to polylines

A few things to note:

1. When using the postgis reader I can still write the polygons in a shapefile

2. When using a shapefile or a gdb as input I can write the polygons in postgis format.

The issue to me seems that the spatial column is carried out from the entry data and I don't know how to get it to a blank slate.

Sorry for my bad english.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

Forum|alt.badge.img
  • Author
  • April 5, 2019

I've looked further into this issue and I'm pretty sure the error comes from the featureMerger. If I try writing to postgis before the featureMerger, it writes polygons and if I write after the transformer it writes Polylines. The suppliers are polylines and the requestor polygons. I've attached a snapshot of the transformer.


Forum|alt.badge.img
  • Author
  • April 5, 2019

Ok so I just found a solution. I find it kind of stupid though and I don't know why it works... I just buffered the polylines coming into the featureMerger. Now that the supplier are polygons it works. What I don't understand is how that makes a difference. I guess the geometry column is carried out form the supplier, but why is it since the featureMerge type is set to attributes only.


david_r
Celebrity
  • April 5, 2019

I've looked further into this issue and I'm pretty sure the error comes from the featureMerger. If I try writing to postgis before the featureMerger, it writes polygons and if I write after the transformer it writes Polylines. The suppliers are polylines and the requestor polygons. I've attached a snapshot of the transformer.

If you don't need the supplier geometry (polylines), you can insert a GeometryRemover on the suppliers just before the FeatureMerger.


Forum|alt.badge.img
  • Author
  • April 5, 2019

If you don't need the supplier geometry (polylines), you can insert a GeometryRemover on the suppliers just before the FeatureMerger.

That works! Thanks, I just don't know why the geometry column of the supplier would be carried