This document summarizes how FME is used to automate data management for Washington State address and parcel data from 38 counties. Key steps include standardizing differing source data schemas, validating addresses, writing validated data to a production database, and scheduling regular updates. Dashboards built with FME and ESRI Portal display standardized data counts and usage. Future goals include making workspaces adaptable to different environments and storing configuration details in a database for improved scheduling and reporting.

1. Automating Data Management With
FME
Austin Hildreth

2. Task – Capture Address Data

3. Place your screenshot here
Washington State Counties

4. Data and Uses
Derived Products:
 Address (points)
 Parcels (boundaries)
 Streets (centerlines)
 Owner Information (tabular)
 Geocoding
 Land base

5. Challenges
 38 Counties
 All in different data schemas
 Source formats are different
Keeping data up to date

6. Tools
Safe Software
• Desktop 2017/16
• Server 2017
Microsoft
• Management Studio 2014
• Server 2012
ESRI
• Desktop 10.5.1
• AGS 10.5.1
• Portal 10.5.1

7. Proccess

8. Standardize Data

9. 1 - Map Data
2 - Scheduler
FME Workbench(s)
Data Mapping
Attr1
Attr2
Attr3
Derived Prod Info
Attr1
Attr2
Attr3
3 – Download Data
County FTP
FME Workbench(s)
Map data to StandardFME Workbench(s)
Check data
WAMAS Data
Service
Derived Product
Attr1
Attr2
Attr3
4 – Data Validation
schedule

10. FME Workbench – Address Points
1 – Call workbenches for each County

11. FME Workbench – Address Points
1 – Call workbenches for each County

12. FME Workbench – Address Points
1 – Call workbenches for each County

13. 1 – Call workbenches for each County
FME Workbench – Address Points

14. FME Workbench – Address Points

15. FME Workbench – Address Points
2 – Get attribute mapping for county schema

16. FME Workbench – Address Points
2 – Get attribute mapping for county schema
To next workbench
@Value(attrValue)
@Value(attrValue)
@Value(attrValue)
@Value(attrValue)

17. FME Workbench – Address Points
3 – Parse Address and validate
servernam
eservernam
e

18. FME Workbench – Address Points
3 – Parse Address and validate

19. FME Workbench – Address Points
3 – Parse Address and validate
@Value(attrValue)

20. FME Workbench – Address Points
3 – Parse Address and validate
servername
servername

21. FME Workbench – Address Points
4 – Validate and write to Prod
https://state-
wamas.wa.gov/webdirectory/pagename.asmx/Getstandardizedaddress?address=@Value(mADDR)&a
ddress2=@Value(mADDR2)&city=@Value(mCITY)&zip=@Value(mZIP)&zip4=@Value(mPLUS4)&state
=@Value(mSTATE)&company=&Consumer=@Value(mCONSUMER) HTTP/1.1

22. FME Workbench – HTML Reports

23. FME Workbench – HTML Reports

24. FME Workbench – HTML Reports
Transformers:
HTMLReportGenerator
Sorter
HTMLLayouter
Writer:
HTMLWriter

25. FME Workbench – HTML Reports

26. FME Workbench – HTML Reports

27. FME Server – Schedule

28. D.O.R. Internal Self Serve Portal
(ESRI Portal for ArcGIS Server)

31. Parcel and Owner Information

32. Street Information

33. Address Point Information

34. Address Point Information (City)

35. Data Counts and Usage
 Address Points – 2,167,403
 Parcels – 3,114,394
 Streets – 731,172
 Owner Information – 2,101,161
 PSAP Streets (911) – 566,910

36. Challenges
- FME 2017 – FMEServerJobSubmitter @Value(xxxx)
- FTP data moving to OpenData
Next Steps
- Environment adaptable workspaces (Projects)
- Email notifications (job completions and errors)

37. Store attributes/configuration in
database
Schedule Workbench Multiple
Workbenches
Log processes and generate
reports
Create Universal Custom
Transformers (re-usable)

38. THANK YOU!
Austin Hildreth
DORDLI.S.GISTeam@DOR.WA.GOV