This document summarizes the Capital Improvement Program (CIP) at the City of Austin. It discusses how CIP projects, which can cost millions, are mapped using FME software to integrate data from different departments into a single geodatabase. This allows users to view over $500 million in annual projects and helps coordinate projects between departments. It also describes IMMPACT, a web application that displays mapped CIP projects and permits to improve planning and identify opportunities for collaboration.
Varsha Sewlal- Cyber Attacks on Critical Critical Infrastructure
Mapping Austin's Capital Improvement Projects
1. Mapping Capital Improvement
Program Projects at the City of
Austin
Logan Pugh – Programmer Analyst
Ben Vanderford – GIS Analyst
Annie Van Zant - Project Coordinator
April 8, 2013
2. The Capital Improvement Program
Projects can cost millions of dollars to design and construct:
Animal Services Center, Water Treatment Plants, the Street
Reconstruction Program, the new Central Library, Park and
Facility Improvements
Funded by the following
voter-approved bond elections
utility revenue bonds
grants
the capital budget
3. Why Map These Projects?
Replace “elevator project coordination”
Improve situational awareness
Create dig-once opportunities between City departments
and other agencies/municipalities
Provide information to citizens
Assist with business reporting
Account for traffic control, special events planning, and
hauling routes
4. The Process
1. CIP Project Managers maintain information in a project
management database
2. Project Managers contact their department’s GIS
coordinator(s) to map their project with the project ID and
approximate limits of construction
3. An FME workspace runs nightly on FME Server:
Integrates each department’s source features into one polygon
feature class in an SDE geodatabase
Joins the polygon feature class to the project management
database using the project ID, adding key project coordination
information
Custom change detection technique is used to perform
incremental updates/additions/deletions
6. Key Transformers
SQLCreator
Used to query the project management database – creates a feature for each
record returned
FeatureMerger
Used to join the attributes of the project management database to the
departments’ source features.
Also used in change detection to take the appropriate attributes from either the
original or the updated features.
SchemaMapper
Allows us to use external files to define how attributes and values are mapped
from departments’ source features to the CIP Feature Class.
Also used to map large number of different project types in the project
management database to a more manageable number for symbolization in GIS
and web applications
CRCCalculator
Given a set of attributes and the geometry of a feature, produces a unique
“check value” that can be stored and later used to compare against the same
feature in order to determine whether it has been modified since.
7. This part of the workspace reads in our source features and queries
the project management database. Then we map the attributes of
both streams of data into a common schema.
8. Here we join the records
from the project
management database to
the source features on the
project ID
We also map the large
number of project types
from the project
management database to a
smaller number of project
types using an external
lookup table
9. Here we buffer point and line features so that the all the output
features are polygons.
A fixed buffer amount of 20 feet is used, although we could allow
for different buffer amounts for different types of features.
10. We calculate a CRC for each incoming feature and compare it
against that of the feature stored in the SDE feature class.
11. We also check whether the feature was added or removed
depending on which port of the FeatureMerger it comes out of
12. IMMPACT
Infrastructure Management, Mapping, Planning, And
Coordination Tool
Web-based mapping application
First City of Austin application to show CIP projects and
permits together
Explorer View: shows CIP projects and permits in a geographic
context
Details View: lists potential conflicts & opportunities for any
given CIP project or permit
Reports View: users can query CIP projects and permits based
on defined criteria
13.
14.
15.
16. Lessons Learned
Use database of record information
Need create a 1-to-1 relationship between projects &
features
Create a culture of cooperative planning efforts between
departments to establish standards and best practices
Future Recommendations
Take advantage of new features in FME Server
Provide project information to the public
Include other departments with CIP mapping
Create a similar process for projects not funded by the CIP