Skip to main content
Question

In my workflows I have the problem with the elements "CompoundCurve" and "Curvepolygon" when writing to a postgresql / postgis database with default schemas for osm_point, osm_line and osm_polygon.

  • August 1, 2020
  • 3 replies
  • 590 views
erido
Participant

Geometry type "CompoundCurve"

Because of the given schemas the postgis writer has problems with the geometry "CompoundCurve". I want to convert this in the process into a normal line element, which can be read in the osm_line table with the geometry "linestring". Today my process in the Workbench crashes with an element with the geometry "CompoundCurve".

 

Geometry type "Curvepolygon"

The second problem is the geometry type "Curvepolygon". This is written correctly into the postgis table osm_polygon. But then I have to delete these objects manually in pg_admin, so that the generated data can be read by the application software. Is there a possibility in FME to convert the elements with the geometry type "Curvepolygon" into a normal polygon?

 

With best thanks for your support!

 

Erido

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.

3 replies

takashi
Celebrity
  • takashiCelebrity
  • August 1, 2020

Hi @erido​ , such a situation could appear if the curve (including the boundary of a polygon) was a Path geometry containing Arc parts. Try using the ArcStroker and the GeometryRefiner to transform the curve to Line geometry before writing them into the PostGIS database table.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
piertard
J
Forum|alt.badge.img

Hi @erido​ , such a situation could appear if the curve (including the boundary of a polygon) was a Path geometry containing Arc parts. Try using the ArcStroker and the GeometryRefiner to transform the curve to Line geometry before writing them into the PostGIS database table.

@Takashi Iijima​ 

I have tried using the combination of this transformers but the issue still persist..

I would like to find a way to discard o repair these geometry ("CompoundCurve".) to avoid the WB stops when I am inserting data to postgis table.

 

GeometryFilter

GeometryValidator

ArcStrokcer

GeometryRefiner

 

piertard
Contributor
Forum|alt.badge.img
  • piertardContributor
  • Contributor
  • April 13, 2024

Hi @erido​ , such a situation could appear if the curve (including the boundary of a polygon) was a Path geometry containing Arc parts. Try using the ArcStroker and the GeometryRefiner to transform the curve to Line geometry before writing them into the PostGIS database table.

@Takashi Iijima​ 

I have tried using the combination of this transformers but the issue still persist..

I would like to find a way to discard o repair these geometry ("CompoundCurve".) to avoid the WB stops when I am inserting data to postgis table.

 

GeometryFilter

Hi @erido​ , such a situation could appear if the curve (including the boundary of a polygon) was a Path geometry containing Arc parts. Try using the ArcStroker and the GeometryRefiner to transform the curve to Line geometry before writing them into the PostGIS database table.

Mr Takashi's solution worked very well for me. I couldn't write my polygons in a GPKG and I got a curvepolygon error that couldn't be written.

GeometryValidator

Hi @erido​ , such a situation could appear if the curve (including the boundary of a polygon) was a Path geometry containing Arc parts. Try using the ArcStroker and the GeometryRefiner to transform the curve to Line geometry before writing them into the PostGIS database table.

 

ArcStrokcer

GeometryRefiner

 

 

 

Community Stats

32,154
Posts
122,043
Replies
39,812
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.