20
CONNECT. TRANSFORM. AUTOMATE. Using FME to transfer Park asset data from an Oracle database to Trimble GPS units and back Amanda Nunns GIS Technician

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

Embed Size (px)

DESCRIPTION

Presente

Citation preview

Page 1: 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 Amanda NunnsGIS Technician

Page 2: 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 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.

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

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.

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

Data Flow

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

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

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

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)

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

Oracle to Trimble SSF

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

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.

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

SSF to Access

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

Combine Access Files

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

Update Oracle: Overview

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

Update Oracle: Part 1

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

Update Oracle: Part 2

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

Update Oracle: Part 3

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

Insert Oracle: Overview

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

Insert Oracle: Part 1

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

Insert Oracle: Part 2

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

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.)

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

Full Insert to Oracle Workbench

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

Thank You!

Questions?

For more information: [email protected] Community Services, City of Edmonton