Using FME to Transfer Park Asset Data From an Oracle Database to Trimble GPS Units and Back
CONNECT. TRANSFORM. AUTOMATE.
Using FME to transfer Park asset
data from an Oracle database to
Trimble GPS units and back
924 parks within the City of Edmonton.
4971 Park Maintenance sites that contain Park
assets and are collected as part of the Summer
31 types of park assets are inventoried each
All these assets need to be inspected to validate
the inventory stored in Oracle spatial and update
the condition record used in various Capital
planning and Inventory management programs.
Summer Inventory Project
6-8 summer students update approximately ¼ of
the city per year using Trimble GPS units.
Collect the current condition of all assets owned or
maintained by Parks Operations.
The data needs to be transferred from an Oracle
database to handheld GPS units so it can be
updated. It then needs to be processed and
uploaded back into the Oracle database.
Data for each asset is stored in 2 or 3 tables:
Spatial Asset table
Stores information that is constant for the asset (ex.
Non-Spatial Condition table (Shared between all
Spatial Condition Location table (For assets with
multiple conditions, ex. Trails)
Oracle to SSF:
Trimble has a character limit on it’s attribute
values. Some values need to be changed to a
Ex: Type of Fence is “Chain Link with Barbwire”,
changed to “Chain Link +Barbwire”.
Done using a Tester and an AttributeSetter.
Trimble does not accept compound geometry,
therefore some features need to be split according
to their geometry type.
Any attribute values that had been shortened for
the SSF files need to be changed back.
Also a chance to catch any common data errors
and automatically clean them. (Ex. Missing