Blending Enterprise Data with FME Server
-
Upload
safe-software -
Category
Technology
-
view
44 -
download
4
Transcript of Blending Enterprise Data with FME Server
![Page 1: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/1.jpg)
![Page 2: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/2.jpg)
About Me
GIS Analyst, Central SanCarl Von Stetten
![Page 3: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/3.jpg)
The sojourn continues…
![Page 4: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/4.jpg)
What is “Enterprise
Data”?
• Non-spatial tabular data
• Often part of Commercial Off-The-Shelf (COTS) software
• Computerized Maintenance Management Systems (CMMS)
• Enterprise Resource Planning (ERP) systems
• CCTV or other inspection systems
• Stored in an enterprise DBMS• Oracle
• Microsoft SQL Server
• IBM DB2
• SAP
• Microsoft Access**
• Frequently involves lots of related tables
![Page 5: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/5.jpg)
![Page 6: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/6.jpg)
Old Autodesk MapGuide Web GIS
![Page 7: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/7.jpg)
Old Web GIS Pop-Up Reports
AccesstoEnterpriseDatavia
Linksonly
![Page 8: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/8.jpg)
New Geocortex Web GIS
![Page 9: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/9.jpg)
Geocortex Details Pane
ThisistheperfectplaceforsomeEnterprisedata!
![Page 10: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/10.jpg)
![Page 11: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/11.jpg)
![Page 12: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/12.jpg)
Evolution of a Gravity Sewer Main
1989– PipeinstalledM1 M2
Pipe ID: M2/M1
2003– CCTVinspection
M1 M2M5
M6
Pipe ID: M5/M1 Pipe ID: M2/M5
2005– NewMHinstalled
![Page 13: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/13.jpg)
CCTV Pipes vs. GIS Pipes
M1 M4PR2 PR3
M4/PR3PR3/PR2PR2/M1
GISPipes
M1 M4PR2 PR3
M4/M1
“NonstopMHtoMH”CCTVInspection
M1 M4PR2 PR3“PerfectMatch”CCTVInspection
M4/PR3PR3/PR2PR2/M1
M1 M4PR2 PR3“Reverse”CCTVInspection
PR3/M4PR2/PR3M1/PR2
![Page 14: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/14.jpg)
Identification Formats Change
StructureTypeOldGISIDFormat CCTVIDFormat GISIDFormat
Manhole 75A1M12 75A1M12 75A1-M12
Cleanout 9E7CO10 9E7CO10 13B7-CO10
JunctionStructure 47C3JS5 47C3JS5 47C3-JS5
RoddingInlet 101E7 R22 101E7R22 101E7-RI22
PressureRelief 47D6P 6 47D6P6 47D6-PR6
Wye 13B5W5.3 13B5W5.3 13B5-W5.3
![Page 15: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/15.jpg)
![Page 16: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/16.jpg)
1
1 GravitySewerMainEvolution
FME Server Process Builds “Junction Table”
2
2
2 CCTVvs.GISPipes
4 CreateJunctionTableRecords
4
3
3
IdentificationFormatChange3
![Page 17: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/17.jpg)
FME Server Process Builds “Junction Table”
![Page 18: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/18.jpg)
FME Server Process Builds “Junction Table”
![Page 19: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/19.jpg)
![Page 20: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/20.jpg)
Cross-Database joins
• May not be common primary/foreign key columns
• May not be optimally indexed
• Datatypes may not match (casting is slow)
• May mix DBMS platforms• MS Sql Server• Oracle• IBM DB2• Sybase• MS Access
![Page 21: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/21.jpg)
Enterprise database table
joins
• 1:Many relationships may need aggregation
• May not be optimally indexed for joins
• Data may not be consistent
• May be deeply nestedTable1
idPK
blahblahblah
yadayadayada
Table2
idPK
blahblahblah
yadayadayada
fk_idFK
1:M
Table3
idPK
blahblahblah
yadayadayada
fk_idFK
1:M
![Page 22: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/22.jpg)
Geocortexsupports joining
to Enterprise databases, but…
• Still subject to the “pain points”
• poor performance• data inconsistencies• aggregation
• Users must “drill down” through relationships to get to the joined data (e.g.: extra clicks)
• Doesn’t support nested table joins and 1:Many relationships
![Page 23: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/23.jpg)
![Page 24: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/24.jpg)
“Blend” the Enterprise data
into the GIS features
1. Add extra fields to relevant geodatabase feature classes
2. Use FME Server to write the enterprise data into those fields
3. Profit! J
![Page 25: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/25.jpg)
![Page 26: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/26.jpg)
![Page 27: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/27.jpg)
“Blend” the Enterprise and GIS data into a non-versioned
“Publish” geodatabase
1. Duplicate the geodatabase schema to new “Publish” geodatabase
2. Add extra fields to relevant geodatabase feature classes
3. Use FME Server to truncate/repopulate the geodatabase with the “blended” data
4. Profit! J
![Page 28: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/28.jpg)
FME Server Publishes “Blended” Sewer Features
![Page 29: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/29.jpg)
InlineQuerier gets the job done
![Page 30: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/30.jpg)
Cross-Database Joins
Citworks workorderdatapulledinviaSQLCreator
transformers
GISFeatures
WinCan CCTVdatapulledinviaSQLCreator
transformerCCTV“JunctionTable”createdinSolution#1
![Page 31: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/31.jpg)
7tablesforparceladdressandownership
datainERP
DoesparcelhaspermitsinERP?
DoesEnvironmentalCompliancemonitorbusinessesonthis
parcel?
GISFeatures/AttributeTables
ResultsfromFMEPointOnAreaOverlayer
Transformers
Cross-Database and Nested Table Joins
![Page 32: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/32.jpg)
AttributeManger Conditional Values
![Page 33: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/33.jpg)
FME Server Works While I Sleep!
ParcelBlenderMon-Fri@10:30pm
SewerBlenderMon-Fri@11:30pm
CCTVJunctionTableMon-Fri@10:30pm
![Page 34: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/34.jpg)
Blended Sewer Data in 3 Clicks
Place your screenshot here
![Page 35: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/35.jpg)
Blended Sewer Data in a Themed Layer
Place your screenshot here
![Page 36: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/36.jpg)
Blended Parcel Data in 3 Clicks
Place your screenshot here
![Page 37: Blending Enterprise Data with FME Server](https://reader031.fdocuments.net/reader031/viewer/2022030307/58e7e48a1a28abbc0b8b4add/html5/thumbnails/37.jpg)