Skip to main content
Solved

How to save and read "Geocoded Addresses" table at the same time

  • June 1, 2026
  • 2 replies
  • 55 views

parhatborani
Contributor
Forum|alt.badge.img+2

Hi there,

Below illustrates a conceptual level of diagram (of a customer transformer), which ideally should be able to intake new (or old) addresses, check if the addresses are already in the “Geocoded Addresses” table; if not, go to a Geocoder, get the address geocoded and then write it back to the same “Geocoded Addresses” table. The challenging part is that the newly geocoded addresses that just got entered into the “Geocoded Addresses” table or list should be reflected on the “Geocoded Addresses” reader on the left hand side so that when next address is being checked, the “Geocoded Addresses” table should have gotten refreshed with the new values (the addresses that just got entered). 

Is there any better way to do this? 

 

Thanks in advance. 

Best answer by crystalwang

Hi ​@parhatborani,

Thank you for posting your question on the FME Community!

To address this, I would suggest adding a DuplicateFilter before your FeatureMerger to remove any repeated addresses from the incoming batch.

Since each address is now unique in the run, the FeatureReader only needs to read the cache table once at the start and you won’t be in a situation where a newly geocoded address needs to be visible mid-run.

Let me know if this helps!

2 replies

crystalwang
Safer
Forum|alt.badge.img+22
  • Safer
  • Best Answer
  • June 9, 2026

Hi ​@parhatborani,

Thank you for posting your question on the FME Community!

To address this, I would suggest adding a DuplicateFilter before your FeatureMerger to remove any repeated addresses from the incoming batch.

Since each address is now unique in the run, the FeatureReader only needs to read the cache table once at the start and you won’t be in a situation where a newly geocoded address needs to be visible mid-run.

Let me know if this helps!


parhatborani
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • June 9, 2026

Hi ​@parhatborani,

Thank you for posting your question on the FME Community!

To address this, I would suggest adding a DuplicateFilter before your FeatureMerger to remove any repeated addresses from the incoming batch.

Since each address is now unique in the run, the FeatureReader only needs to read the cache table once at the start and you won’t be in a situation where a newly geocoded address needs to be visible mid-run.

Let me know if this helps!

Thanks a lot.