Skip to main content
Solved

Geometry fails OGC - GeometryValidator fails to repair

  • May 19, 2020
  • 4 replies
  • 765 views
mathiku
Supporter
Forum|alt.badge.img+8

I am receiving geometries from MapInfo .TAB-files.

They are then to be passed on to a server in a XML-file. I parse the geometries using GeometryExtractor -> GML 3.1.1.

No problem - the GeometryValidator -> DonutBuilder -> GeometryExtractor seems rock solid.

Today I encountered this geometry which I can't seem to pass on. It fails OGC and GeometryValidator fails to repair it.

For now my workaround is to add a small buffer, but does anybody have a better method?

Attached is the geometry as TAB_file.

Best answer by virtualcitymatt

I find that the GeometryValidator never repairs when performing the OGC test. Perhaps try the validator without the OGC test - as @takashi for the case you have here a SpikeRemover should work, or alternatively setting the tolerance a little higher in the self-intersecting test or duplicate/consecutive points test.

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

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • May 19, 2020

Hi @mathiku, the SpikeRemover might help you.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
virtualcitymatt
Celebrity
Forum|alt.badge.img+47
  • virtualcitymattCelebrity
  • Celebrity
  • 2000 replies
  • Best Answer
  • May 20, 2020

I find that the GeometryValidator never repairs when performing the OGC test. Perhaps try the validator without the OGC test - as @takashi for the case you have here a SpikeRemover should work, or alternatively setting the tolerance a little higher in the self-intersecting test or duplicate/consecutive points test.

mathiku
Supporter
Forum|alt.badge.img+8
  • mathikuSupporter
  • Author
  • Supporter
  • 69 replies
  • May 20, 2020

I find that the GeometryValidator never repairs when performing the OGC test. Perhaps try the validator without the OGC test - as @takashi for the case you have here a SpikeRemover should work, or alternatively setting the tolerance a little higher in the self-intersecting test or duplicate/consecutive points test.

Thanks. Removing the OGC tests did the trick. Very simple :)

mathiku
Supporter
Forum|alt.badge.img+8
  • mathikuSupporter
  • Author
  • Supporter
  • 69 replies
  • May 20, 2020

Hi @mathiku, the SpikeRemover might help you.

Thanks for the suggestion. I tried some different settings, but didn't get the desired result, and changing settings in GeometryValidator was really simple.

Community Stats

32,076
Posts
121,791
Replies
39,702
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.