21
Our first 60 days with FME Steven Cyphers / GHD
| Date post: | 08-Apr-2017 |
| Category: |
Technology |
| Upload: | safe-software |
| View: | 24 times |
| Download: | 0 times |
Our first 60 days with FME
Steven Cyphers / GHD
[email protected]@scyphers_
[email protected]@scyphers_
[email protected]@scyphers_
[email protected]@scyphers_
[email protected]@scyphers_
ExpectoTransformeriallis
DriverRationalize some arcpy and modelbuilder scripts into FME
RationaleEnterprise Data Automation
Data
Internal Business needDeliver Stakeholder requirementFlexible to Adapt to changes in Schema
Schema
Data
Alohomora
Iseewhatyoudidthere.
Unlock
One way is dynamic read to build the query that is then executed
Meta-query is that a thing?
Yup
Place your screenshot here
Using the metadata tablesselect owner.table.columnas col, atc.table, atc.ownerfrom all_tab_columns atcwhere 1=1and atc.table_name in distinct(TABLE_NAME) from gis.FEATURESwhere template = ‘$(param)’)order by table, column_id
To Build a query to be then used in a subsequent SQLExecutor
Schema Changes
handledPlace your screenshot here
"Transfigurationyouhavetogetitexactlyright,Transfigurationismorescientific."—J.K.Rowling
The whole ETL enchilada
Lumosarcpy / modelbuilder• Effective• Statically defined to schema,
fragile• Time to maintain scripts• Time/License to run them
FME• Effective • Dynamic in schema• Redefine ‘Our’ schema as data
models change• Reach data at the source,
manipulate and write to the endpoint
• Time to upskill in FME• Run the scripts @interval
