Skip to main content
Solved

Manually Geocoding

  • November 13, 2017
  • 1 reply
  • 20 views
E

I am trying to manually geocode some addresses, and am having a hard time developing the correct workflow to acheive this. I have a dataset coming from a SQL database that is full of addresses with unknown coordinates. I am geocoding with a CSV file that I have created that contains the addresses compiled from county auditor websites with the associated latitude and longitude fields for each address.

I am starting with FeatureMerger because if both address fields are an exact match then this works perfect. -- address geocoded successfully. However some addresses will not match based on different suffix types. (i.e. ROAD vs. RD or HIGHWAY vs HWY) I have added a string replacer transformer to the workflow to trim off the suffixes that could eliminate the addresses from matching via a rubular expression. The part I am struggling with is how do I compare these fields again after I have trimmed off the various suffixes? I have attached a picture of my workflow.

Best answer by laurawatsafe

Hi @ethanheidtman

Looking at the way you currently have your workspace set up with the StringReplacer connected after the FeatureMerger, you would need to add a second FeatureMerger after the StringReplacer to re-merge the two datasets with the fixed up suffixes.

I think the simplest option would be to place the StringReplacer before the FeatureMerger to fix up those issues before they go into the FeatureMerger.

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

laurawatsafe
Safer
Forum|alt.badge.img+13
  • laurawatsafeSafer
  • Safer
  • Best Answer
  • November 14, 2017

Hi @ethanheidtman

Looking at the way you currently have your workspace set up with the StringReplacer connected after the FeatureMerger, you would need to add a second FeatureMerger after the StringReplacer to re-merge the two datasets with the fixed up suffixes.

I think the simplest option would be to place the StringReplacer before the FeatureMerger to fix up those issues before they go into the FeatureMerger.

Community Stats

32,154
Posts
122,048
Replies
39,812
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.