CONNECT. TRANSFORM. AUTOMATE.
Using FME to transfer Park asset
data from an Oracle database to
Trimble GPS units and back
...
Background
 924 parks within the City of Edmonton.
 4971 Park Maintenance sites that contain Park
assets and are collect...
Overview
 Summer Inventory Project
 6-8 summer students update approximately ¼ of
the city per year using Trimble GPS un...
Data Flow
Tracked Assets
 Beds
 Bike Racks
 Bleachers
 Bollard
 Bridges
 Curbing
 Decks
 Drinking Fountains
 Fences
 Fire ...
Data Structure
 Data for each asset is stored in 2 or 3 tables:
 Spatial Asset table
 Stores information that is consta...
Oracle to Trimble SSF
Complexities
 Oracle to SSF:
 Trimble has a character limit on it’s attribute
values. Some values need to be changed to ...
SSF to Access
Combine Access Files
Update Oracle: Overview
Update Oracle: Part 1
Update Oracle: Part 2
Update Oracle: Part 3
Insert Oracle: Overview
Insert Oracle: Part 1
Insert Oracle: Part 2
Complexities
 Any attribute values that had been shortened for
the SSF files need to be changed back.
 Also a chance to ...
Full Insert to Oracle
Workbench
Thank You!
 Questions?
 For more information:
 Amanda.Nunns@edmonton.ca
 Community Services, City of Edmonton
Upcoming SlideShare
Loading in …5
×

Using FME to Transfer Park Asset Data From an Oracle Database to Trimble GPS Units and Back

1,065 views
950 views

Published on

Presente

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,065
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Using FME to Transfer Park Asset Data From an Oracle Database to Trimble GPS Units and Back

  1. 1. CONNECT. TRANSFORM. AUTOMATE. Using FME to transfer Park asset data from an Oracle database to Trimble GPS units and back Amanda Nunns GIS Technician
  2. 2. Background  924 parks within the City of Edmonton.  4971 Park Maintenance sites that contain Park assets and are collected as part of the Summer Inventory project.  31 types of park assets are inventoried each summer.  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.
  3. 3. Overview  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.
  4. 4. Data Flow
  5. 5. Tracked Assets  Beds  Bike Racks  Bleachers  Bollard  Bridges  Curbing  Decks  Drinking Fountains  Fences  Fire Fixtures  Flag Poles  Hedges  Hydro Features  Light Fixtures  Litter Containers  Natural Vegetation Areas  Pads  Park Utilities  Phones  Plaques  Playgrounds  Prefabricated Curbing  Retaining Structures  Roads  Signs  Sports Fields  Sports Fixtures  Stairs  Statues & Art  Tables & Benches  Trails
  6. 6. Data Structure  Data for each asset is stored in 2 or 3 tables:  Spatial Asset table  Stores information that is constant for the asset (ex. Material)  Non-Spatial Condition table (Shared between all the assets)  Spatial Condition Location table (For assets with multiple conditions, ex. Trails)
  7. 7. Oracle to Trimble SSF
  8. 8. Complexities  Oracle to SSF:  Trimble has a character limit on it’s attribute values. Some values need to be changed to a shorter version.  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.
  9. 9. SSF to Access
  10. 10. Combine Access Files
  11. 11. Update Oracle: Overview
  12. 12. Update Oracle: Part 1
  13. 13. Update Oracle: Part 2
  14. 14. Update Oracle: Part 3
  15. 15. Insert Oracle: Overview
  16. 16. Insert Oracle: Part 1
  17. 17. Insert Oracle: Part 2
  18. 18. Complexities  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 capitalization.)
  19. 19. Full Insert to Oracle Workbench
  20. 20. Thank You!  Questions?  For more information:  Amanda.Nunns@edmonton.ca  Community Services, City of Edmonton

×