21
Connecting Field Operations and the Corporate Office - FME Server Near Real-time Processing Mark Giesbrecht, M.Sc. Devon Canada

Connecting Field Operations and the Corporate Office - FME Server as a Near Real-time Processing Engine for Logistics Data and Wildfire Monitoring

Embed Size (px)

Citation preview

Connecting Field Operations and the Corporate Office - FME Server Near Real-time Processing

Mark Giesbrecht, M.Sc.Devon Canada

About Me

Mark Giesbrecht

Near-Time FME

- Field Logistics Application

- Wildfire Monitoring

Field Logistics Application- Update every two minutes, during

business hours- Devon developed REST services- FME used to tear apart the feeds, write to

Geodatabase- Email alerts when jobs fail

Creating Batteries/Facilities

Field Logistics Workflow

Job Details - Workbench Sequence

Field Logistics Workflow

GeoTRAC SOAP Calls

End Result

Main point: FME rocks, makes us look smart

Wildfire Monitoring- Scrape services and write to Geodatabase

- Consume directly- Archive for audit purposes- Control and integrate with internal

environment- ArcGIS Services

(FeatureServer/MapServer)- Text/KML- Python shutdown scripts for notifications

Wildfire Map

Consume ArcGIS Services- Read in FeatureServer from

AB Agr. And Forestry- Layer file- Add in SDE audit columns- Write out on an hourly basis- Increase frequency as

needed

Consume CSV from AB Gov- Download more frequently

updated data- Simple CSV -> Spatial- Write to GeoDB- Write to ArcGIS Online for

mobile use

Consume KML from BC WMB- ‘Discovered’ KML file from

BC WMB- Similar to AB, download and

insert- Archive for audit purposes- No timestamp data

available

Consume NASA Data Feeds- VIIRS Hotspot data- Thermal signatures- 375m resolution- Updated 2x daily

VIIRS Hotspot Notifications- Post download- Unique ‘HotSpot’ ID- Read and write to same

featureclass- Python shutdown script- Sends email only if point

exists in polygon

Wildfire Alerts

Main point: FME rocks, makes us look good