Skip to main content
Question

First input in Append is being entered twice.


Forum|alt.badge.img

The circled number is exactly 2x the number of records in that input - an sde point file. This happens no matter which file is "on top."

In the translation log, the Total Features Read is exactly the right number.

Total Features Written is too high by exactly the number of records in the first input. All other inputs are appended correctly.

Does anyone know why this is happening?

Thank you,

Randy McGregor

Capture

3 replies

deanhowell
Influencer
Forum|alt.badge.img+23
  • Influencer
  • August 21, 2020

Hello @ramcgreg​ What is being read in and what are the parameters that you have set for the reader?

I have seen something similar when reading in a DWG file that has features in model space that are being read through the viewport.


Forum|alt.badge.img
  • Author
  • August 21, 2020
deanhowell wrote:

Hello @ramcgreg​ What is being read in and what are the parameters that you have set for the reader?

I have seen something similar when reading in a DWG file that has features in model space that are being read through the viewport.

SDE point layers are being read. I have used default parameters. I just have them all pointed to a reader to append them (A GIS "merge.") It works beautifully, except for the doubling of records of the first input.

I have entered all point layers into one writer. Maybe a writer for each layer?

Thank you,

Randy


Forum|alt.badge.img
  • Author
  • August 21, 2020
ramcgreg wrote:

SDE point layers are being read. I have used default parameters. I just have them all pointed to a reader to append them (A GIS "merge.") It works beautifully, except for the doubling of records of the first input.

I have entered all point layers into one writer. Maybe a writer for each layer?

Thank you,

Randy

DuplicateFilter to the rescue. Seems to work, but no idea why it's necessary.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings