Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Overview

This document examines the suitability of automating the process of publishing and updating TC Smart Maps data onto the EGIS Portal using FME Server or FME Cloud.

Typical TC Smart Maps Data Processing

TC Smart Maps data derived from various sources and can be categorized as follows:

  1. Web Services - WMS, WFS etc.

  2. GIS Spatial Format - SHP, TAB, KML, Oracle Spatial etc.

  3. CAD Format - AutoCAD, MicroStation, etc.

  4. Database Format - Oracle, SQL Server, MS Access, Excel, CSV etc.

  5. Document Format - PDF, Word, Text, XML etc

  6. Website Site - Web page or any internet site

The data requires either full or semi FME automation for TC Smart Maps consumption, i.e. KML/KMZ format, or alternatively to EGIS Portal as ArcGIS Feature Class.

Integrating FME with EGIS Workflow

Based on TC Smart Maps FME Workflow Diagram, output to EGIS Portal can be grouped as follows:

  1. Items 1: Consumed by EGIS directly.
    Connect to WMS, WFS service as map layer.
    e.g. Natonal Railway Network, Canada Base Maps etc.

  2. Item 2, 3 and 4: Full automation using FME.
    Publish existing FME Workbench onto FME Server then schedule Workspace to run on fixed, flexible or real-time. Depending in changes of source file name and location, minor adjustment might be required for the input file.
    e.g. TC DFRP, NPP Projects, Obstacle Data etc.

  3. Item 5 and 6: Semi-automation using FME
    Front end preparation required either manually or using FME to manipulate, extract or parse text strings from source. As the source data are nonspatial, front-end preparation can be a multi-steps process each requiring validation and quality control.
    e.g. Canada Airspace, Canada Airport, CADORS etc.

FME Server

FME Server is a powerful product that automates the flow of large volume of data between applications at enterprise level. FME Server includes a REST API and supports common protocols such as emails, WebSockets, JMS, and more. It is hosted on premises, securely behind the firewall. It has three core capabilities:

Self-Serve is the ability for the end-user to select and download the data they require, in the format and structure they require; or to upload data for processing. It eliminates the need for a data manager/analyst to carry out manual data distribution tasks.

Real-Time is the ability to react to real-time events and sensors, to carry out immediate updates, and to deliver instant notifications. It allows subscribers to have the most up-to-date information for their business decision making.

Automation is the ability to carry out data processing at a specific schedule and to spontaneously move data through different systems and web services – even onto mobile platforms and devices. It allows data to move from anywhere, to anywhere, without manual intervention.

FME Cloud

FME Cloud is the hosted version of FME Server . It's the ultimate platform for connecting the web, combining the automation power of FME Server with the flexibility of the cloud.

FME Server vs FME Cloud

In general, if the majority of your data is in the cloud or you don't want to worry about costs for hardware acquisition and maintenance, then select FME Cloud. However, if the majority of your data is on-premises or you need some advanced configurations or all formats, then select FME Server.

FME Pricing

FME Desktop (Node Locked)
ESRI Edition
$4,500
Database Edition
$7,800

FME Desktop (Floating/Concurrent License)
ESRI Edition
$11,700
$3,000 (Additional license)
Database Edition
$14,250
$4,750 (Additional License)

FME Server
$18,800 (includes first engine)
$7,800 Addition Engine (Optional)

FME Cloud Annual Software ManitenanceThis fee allows for unrestricted updates and software support.Cost: 25% of software

  • No labels