Skip to main content
Question

Clipper: Clipped split aggregates fail to write to GDB API.

  • May 30, 2018
  • 1 reply
  • 9 views
nielsgerrits
VIP
Forum|alt.badge.img+64

For documentation only as this one is allready reported. (C137061) Like to share as this one took me by surprise, in production.

Aggregates split by a clipper can't be written to geodatabase featureclass using GDB API writer. No issues when writing with GDB ArcObjects writer. This only occurs when input geometry is an aggregate and the result is a splitted aggregate.

Found in 2016.1.1.0 Was able to reproduce in 2017.1.2.0 and 2018.0.0.3

Workaround is to deaggregate and aggregate again.

 

Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
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.

1 reply

fmelizard
Safer
Forum|alt.badge.img+21
  • fmelizardSafer
  • Safer
  • May 30, 2018

@nielsgerrits This is a known issue - nested aggregates can't be written to FILEGDB. For reference, PR70582.

Community Stats

32,207
Posts
122,305
Replies
39,891
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.