Skip to main content
Question

Geometry replacer error

  • May 15, 2019
  • 3 replies
  • 76 views
gis2020
Contributor
Forum|alt.badge.img+5

Hi All,

I am doing the geometry extraction of polylines using the geometry extractor with encoded polyline option and storing this in a dbf file formation. later part of my process is using this dbf file to replace the geometry and use this further for processing and then finally upload this on geoserver. During geometry replacer process few of the feature are getting rejected with error msg "@Geometry: Unable to replace the geometry from attribute '_GEOMETRY'." not sure how i can resolve this error .

Can somebody suggest how i can resolve this ?

 

Thank you in advance.

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

david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • May 15, 2019

Are you sure that the encoded geometries aren't truncated in the dbf?

Also, is there a particular reason for not using something more efficient for geometry storage?

gis2020
Contributor
Forum|alt.badge.img+5
  • gis2020Contributor
  • Author
  • Contributor
  • 61 replies
  • May 15, 2019

Are you sure that the encoded geometries aren't truncated in the dbf?

Also, is there a particular reason for not using something more efficient for geometry storage?

not sure of the first part .. but i am suspecting that it truncating the geometry during the dbf conversion.

 

is there a efficient way to store the geometry . This is the first time i am trying this to store geometry and then use that file to recreate it .
david_r
Celebrity
  • david_rCelebrity
  • 8394 replies
  • May 15, 2019
not sure of the first part .. but i am suspecting that it truncating the geometry during the dbf conversion.

 

is there a efficient way to store the geometry . This is the first time i am trying this to store geometry and then use that file to recreate it .

It's difficult to give a concrete recommendation without knowing your use case, but if you want to stick with DBF as the underlying data format, you should consider using the Shapefile format, which is simply DBF with some sidecar files containing binary geometries. FME allows you to read and write directly to this format and it's very fast.

For a more modern approach you could consider using GeoPackage or SpatiaLite, both also natively supported by FME.

If the data is only to be used with FME, you could use the internal FFS format, it is very fast and supports anything that you can throw at it.

Community Stats

32,080
Posts
121,820
Replies
39,714
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.