2007-09 GIS in Transportation

Transportation Special Interest Group Meeting
Simon Lewis
Terry C. Bills
Ray Carnes
GIS in Transportation 1
Introductions
• Agency Introductions
• Purpose of the Meeting
• Future Directions
2 GIS in Transportation
Agenda – Part A
• Linear Referencing Systems and Dynamic

Segmentation: Conceptual and Practical
• Straight Line Diagrams
• Temporal Data Issues
• Network Management
• Routing / Dynamic Routing
• Transportation Functionality
Agenda – Part B
• ESRI User Conference
• UNETRANS Update
• Best Practice Examples
• ESRI Resources
Linear Referencing and Dynamic Segmentation
Learning More
• Books
– Linear Referencing in ArcGIS

– Building a Geodatabase
• White paper
– Linear Referencing in ArcGIS: Practical

considerations for the Development of an
Enterprisewide GIS
Straight Line Diagrams
Straight Line Diagrams
• Purpose of an SLD
• Varieties of SLDs
• SLDs and GIS
• Future of SLD?
Purpose of SLDs
• Represents Historical Way Data was Stored

and Maintained
• An Engineering View of Roadway – Often the

Original CAD Drawing was a Part of the SLD
• Represent all Roadway Characteristics on a

Measured Straight Line
• Carried into the Field for Inspections /

Maintenance
Highway Inventory
0.000 24.712
2.640 6.486 9.764 18.753
Speed 55 50 45 35 55
Limits
6.216 12.984 20.395

Pavement 5 7 6 7 6 8
Condition
14.539 18.044
1.033 4.002 8.311 15.638 22.478
Intersections
R8-3 W1-2R W1-2L
Signs
R8-3 W1-2R W1-2R
Inventory Tables
Speed Limit Table
roadway ID begin ML end ML speed limit
33S058 0.000 2.640 55
33S058 2.640 6.486 50
33S058 6.486 9.764 45
33S058 9.764 18.753 35
33S058 18.753 24.712 55
Pavement Condition Table

roadway ID begin ML end ML condition
33S058 0.000 6.216 5
33S058 6.216 12.984 7
33S058 12.984 14.539 6
33S058 14.539 18.044 7
33S058 18.044 20.395 6
33S058 20.395 24.712 8
Classic SLD: Ohio DOT
Straight Line Diagram: New Jersey DOT
Colorado DOT SLD
http://dtdexternal.dot.state.co.us/sld/
South Dakota Route Log
Future of SLDs?
• SLDs were Designed Prior to GIS and

Represented a Tabular “Mainframe”
Orientation to Data
• Precursor to GIS
• Now that GIS can represent all of the

Roadway Characteristics in Proper Spatial
Location, Do We Still Need SLDs?
Working with Temporal Data
Temporal GIS
Integrated Time in a GIS
• Extended Data Model
• Tools for Manipulation

– Query View Control
Room
– Change Analysis
– Iterative Processing
Multi Dimension Data
– Visualization Sets (NetCDF)
• Animation
• Charting T
y
– Tracking Analysis
Current
Modeling
Modeling
Date x
Simulation Files
Archive/History
Date
Real Time
T1
Retire Sensor Network
Future
History / Present
Archiving
Past
Mobile
Stationary
. . . New Ways to Manage, Analyze &
Visualize Geography
Persisted Versions – To manage long transactions, history,
and replication
Historical Replication
Multi-user Archive
Editing
Edit
st
Po
Default
Version Archive
Views
Temporal Data
• Past, Current & Future Networks
• Highway Realignments and Accident Data
• Roadway Conditions at Different Time Points
Temporal Data
• Master Networks
• Versioning
• Chapter 6, Page 5
Retaining History
Table Class template supporting
Entity continuous versioning
Allow Default Pre-
Field name Data type nulls value Domain cision Scale Length
OBJECTID Object ID
EntityID Long Integer Yes 0 Identifier of entity
RecordDate Date Yes Date record was created
FromDate Date Yes Starting date of validity
ToDate Date Yes Ending date of validity
RecordStatus Short Integer Yes RecordCode 0 Status of record
EntityStatus Short Integer Yes EntityCode 0 Status of entity in the real world
Table Enhanced class template

Entity supporting edit process
Allow Default Pre- management
Field name Data type nulls value Domain cision Scale Length
OBJECTID Object ID
EntityID Long Integer Yes 0 Identifier of entity
RecordDate Date Yes Date record was created
EnteredBy String Yes 30 Name of person creating record
FromDate Date Yes Starting date of validity
ToDate Date Yes Ending date of validity
RecordStatus Short Integer Yes RecordCode 0 Status of record
EditReason Short Integer Yes EditCode 0 Reason the update was made
Comment String Yes 255 Comment field for additional information
EntityStatus Short Integer Yes EntityCode 0 Status of entity in the real world
Network Management / Editing
Multi-user Data Management
Workflows and Versioning
User User User

• A key part of the design is
the approach for using
T T T
versioning in the workflow
GeoDatabase
processes
• Need to think about this as
part of the database design
– Key impact on when QC
processes happen, data
update processes, ArcSDE Enterprise
information model
T = Transactions
Distributed Data Management
• Replicated Geodatabases
• Periodically Updated
• Administration Tools T = Transactions
• History/Archiving
T T
Update
Messages
National T
T
State
T
Local
Information Management
Version Replication
• System scalability
• Consolidate edits
Read-Write Read-Write
Geodatabase Two-Way
Geodatabase
Web users
One-Way
ArcGIS
ArcIMS
Server
• Peer to peer • Read-only ‘cache’

• Editing Check-out/in
• Hierarchical Read-only
Geodatabase
Managing Distributed Data
Replication of Geographic Information
Supports
• Change Only Updates • Collaborating Agencies
• Synchronized Periodically • Co-Data Producers
• Central & Regional Offices
• Works on the Web or Courier
• Mobile Units
Central
Read / Two
Write Read /
Way Write
One
Hierarchy Way
National
Read
Only ArcIMS
State
Local
. . . Key Technology For GeoWeb

Routing
Multi-modal networks in real world
First Generation Routing Systems
• Same basic route

finding algorithms
for web and
vehicle
• Built on a
“network” dataset
• Used for
commercial
purposes as well
Second Generation Routing Systems
• ESRI is currently building full Dynamic Routing

incorporating historical (predictive) travel time,
real time travel speeds, real time incident data
into a single routing engine.
• These applications are for personal and

commercial solutions, although ESRI’s primary
focus is commercial and institutional
Second Generation Routing Systems
Dynamic
Routing will
play an ever
increasing
role in
emergency
dispatch and
emergency
operations
Dynamic Routing
Server Finds Shortest Time Path Delivers to Any Client
Why Should I Care About Routing?
ArcLogistics Route:
Service Routing and Scheduling
Manifest with Maps & Directions
Orkin
(Recurring services work for
pest control services)
Sears Mobile Mapping and in-vehicle navigation
system (SST)
GPS
• In-Vehicle
navigation (11,000
units)
• Satellite and
terrestrial
communication
• Verbalized
Turn Right on East
directions Washington Street
• Touch screen
• Mobile Workstation
• Nationwide
Geocoding
• Nationwide Routing
Public Works Portal
• ArcWeb Services
• IBM WebSphere
• Sprint BMF
• Ubiquity
• Manage Asset Locations
• Vehicles
• Equipment
• Personnel
• Geofencing & Alerts
• Detailed Reports
GIS Logistics: sample savings
Schindler Elevator Co. Î Annual Savings: > 3 million/Yr
Sempra Energy Î Mileage Reduction: 2 million/Yr
Sears Home Delivery Î Productivity Increase: 9%
- Mileage Reduction: 5%
- Overtime Reduction: 23%
- On-time performance: 19% increase
- Facility Consolidation 48 to 6
- Annual Savings: >$50 million
City of LA Bureau of Sanitation Î Mileage Reduction: 11%
A Major Energy Company Î Mileage Reduction 13%
A Major Telco Î Annual Savings: $50 million
A Major Insurance Company Î Productivity Increase: 14%
A Major Courier Company Î Reduction in Routes: 30%
A Major Beverage Distributor Î Reduction in Vehicles: 25%
A Major Retailer Î Annual Savings: $4 million
A Government Agency Î Reduction in Routes 33%
Third Generation Mobile Systems
Field
Information
Collection
In-Vehicle
Navigation
Vehicle
Tracking / Mobile
Security GIS
Work Order
Optimized Management
Routing
and
Scheduling
All Integrated with Corporate ERP and CRM
Transportation Functionality
Agenda – Part B
• ESRI User Conference
• UNETRANS Update
• Best Practice Examples
• ESRI Resources
ESRI User Conference
• 14,000 Users From Around the World
• Sample Papers:
– Travel Time: An Empirical method for Determining
Average Network Speeds
– Conflating a Traffic Model Network with a Road
Inventory
– Regional Growth and Transportation Study in Kent
County, Delaware
– Integrating Applications and Databases with
NCDOT Linear Referencing Systems
– NCDOT Highway Milemarker Inventory and
Integration with LRS
ESRI User Conference
• Sample Papers:
– Dynamic Segmentation as a Tool for Transport-
Related Data Management
– Network Analyst Multi-modal Routing Tool for the
Commodity Flow Survey
– Truck Trip Estimation by Facilities Using ArcInfo
– Development of an Intermodal Network for Freight
Transportation Analysis
– Geospatial Modeling of Ship Traffic and Air
Emissions
– Serving Up Enterprise Data
– Centralizing Data for the Louisiana TIMED Program
UNETRANS Update
• New Transportation Data Model
• A “How-To” Book: Step by Step to Design and

Build your Transportation Data Model
• Designed for all Levels
• Due for UC 2008
Key Technology Issues / Best Practice
Key DOT IT Issues
• Integration to Support Agency-Wide Business

Functions:
– Need to provide easy access to data and

information: “ A seamless flow of information
regardless of format, platform or location”
– Need to integrate data across the enterprise; to

integrate the DOT “project lifecycle”
Integration to Support Agency-Wide Business
• Why an Issue? Because Increasingly the Most

Valuable Resource Within a DOT is the Information
Infrastructure
– 85 Percent of Data in Modern Organizations is Unstructured*

– 30 Percent of People’s Time is Spent Searching for Relevant
Information*
– 60 Percent of CEOs and Agency Directors Feel They Do Not
Have the Type of Information Support to Make Good
Decisions*
– 90 Percent of Information in a DOT has a Spatial Component
* Source: IBM
• DOTs are often plagued by Stovepipe

Applications, creating: “Islands of Data”
• Data is located at the application level, often in

different formats
• Major Gaps in Information Flow across the

Agency
Smooth Information Flow?
Design
Planning
Infrastructure
Life-Cycle
Construction
Maintenance
N
Operations
System-Wide Data View
http://dashboard.virginiadot.org/def
ault.aspx
Key DOT IT Issues
• Support for complex IT environments can often
involve multiple operating systems and multiple
application environments
• Support for a Distributed Environment
• Desire to support best of breed COTS

solutions
• Need to provide technology which supports

and enriches business processes, not the other
way around
Integration: Technology Trends
What is an information system?
Driven by mission and business needs
• An information system is a tool for providing useful

information through management and analysis of data.
Interface
System
information Data
Users
Information system
• The design of the system is based on the information we want the
system to provide and to manage and the necessary workflows for
compiling and managing the information.
Obtaining Value from Enterprise Programs
– Goal is to provide a long lasting technical
architecture that meets business needs and
efficiently leverages COTS technology.
– Matching technology capabilities to business
needs.
– An iterative process; maturity takes time!
Business
Business
Applications Applications
Instead of…
Data Data
Technology
Technology
• Approaches to Enterprise Application

Integration (EAI):
– Point to Point APIs
– Data integration / Data Warehousing: through

use of ETL tools, creation of a common DBMS
– Web Services
– Service Oriented Architecture: integrating

Business processes through Message Buses
(Enterprise Services Buses)
Point-to-Point APIs
Ca pital
Capit al Rig ht of
Right of
Programming
Progra mm ing y
As sets
Asse ts
Wa
Way
Cras
Cr Data
ashh Da ta
Ro uting
Routi ng
signn
Desig
De Pro jects
Projec ts
Contr
Co acts
ntrac ts
Pave
Pa ment
veme nt
Ve ndors
Vend ors
ction Traffic
Tra lumes
Volum
ffic Vo es
Cons
Co tructi
nstru on
GIS En viron
Envir ntall
menta
onme
GIS
Data Warehousing
Right of Way
Capital Crash Data
Programming
Projects Traffic
Volumes
Data
Warehouse
Assets
Construction
Pavement
Environmental
GIS
Web Services
Assets
Assets
Design
Design Contracts
Contracts
Capital
Capital Right
Right of
of Crash
Crash Data
Data
Programming
Programming Way
Way
Routing
Routing
Integration Platform and Workflow Applications

Traffic
Traffic Volumes
Volumes Environmental
Environmental GIS
GIS
Projects
Projects
Vendors
Vendors
Pavement
Pavement
Construction
Construction
Services Oriented Architecture
• Allows you to build applications, drawing data

and logic from different existing sources, and
combine them in ways that meet your current
business requirements
• A flexible and agile integration framework;

technology and platform independent
• Reflects IT Best Practice: “By 2008, SOA will

be a prevailing software engineering practice”
(Gartner)
Service Oriented Architecture
An approach for building distributed computing systems

based on encapsulating business functions as services
that can be easily accessed in a loosely coupled fashion.
Service
Service
Directory
Directory
Find /
Details Publish
Service
Service Service
Service
Consumer
Consumer Bind / Provider
Provider
Invoke
SOA Benefits
• Top 3 Benefits *
1. Expose IT resources in an easily consumable fashion
(Architecture Partitioning)
2. Incremental Deployment and Maintenance
3. Reuse of Services
• Additional Long-Term Benefits

• Faster time to market
• Reduced cost
• Risk mitigation
• Continuous business-process improvement
* “Latest SOA Trends”, D. Stang, Gartner, 2005
Desktop Clients Desktop Clients Browser Clients Mobile Clients Mobile Clients Embedded Clients
(heavy ) (light ) (heavy ) (light)
`
Extensions Applications Applications Applications Applications Applications
FirstView ArcGIS Engine Transportation One - ArcPad .NET CF, MIDP, ArcGIS Engine
ArcGIS Desktop ArcObjects Stop Portal Application Builder CLDC, Native ArcObjects
ArcObjects Java, .NET, VB, ArcGIS Server VBScript Java, .NET, VB,
C++ ArcIMS C++
.NET, VB, C++ HTML, JavaScipt,
CSS, Flash, Ajax,
SVG, Applet
Service Orchestration - BPEL

GIS Web Server Service Discovery – UDDI - Create sequence of
services and expose Web
- Geocode_Service Applications
- LRS Service as a new service. (Stitch Engine
- Find_Closest_Project_Service services together)
Use services.
- Get_Map_Service
- Query Catalog
- Reporting Work order Schedule_WO
Tool - Get asset Data
- Real Time Service Description - WSDL
- Metadata - Locate
Describes how to use a service
- Find WO History
- Get Map
- Get External Data
- Notify Utilities
- Schedule WO
Enterprise Service Bus
Messaging service, routing service, filtering service, etc.
Real-Time Data
-Traffic
ArcSDE ArcSDE Dynamic Data -Incidents
NM DOT Centralized -Weather
Operational Publication Feeds
Database -Vehicles
Replication -Construction etc.
Version1 Version2
Adapters /ETL
CIS
Bridge
Legacy Roadway Maintenance
CIS Legacy Traffic CIS
Pavement
Legacy Other
CISDOT
Legacy
Legacy
CIS Legacy CIS Legacy Accidents
Management
Data Inventory Management
Data Transport CARS Management Management
Data Data
Data Data
(MMS) System
Enterprise Architecture
• Regardless of your approach (data warehouse,

web services, or a services oriented
architecture), integrated and managed data is
still the key requirement
• Given that most data within a DOT has a spatial

component, this inevitably leads to a
consideration of an enterprise view of GIS
• That enterprise orientation has to involve, if not

come from IT
Enterprise GIS
GIS is Evolving
From Project and Workgroup
to Enterprise Information System
Web Services
Networks
Client/Server
Systems
Desktop Tools &
Data
Enterprise
Workgroup GIS
Personal Services
Professional Information
Productivity Management
Principle Purposes of Enterprise GIS
• Provide broad access to geospatial data and

functionality
• Provide a common infrastructure upon which to
build and deploy GIS
• Gain significant economies of scale through
organization-wide GIS deployment
Bottom line: enterprise GIS is intended to
address an enterprise’s functional needs
collectively instead of individually
Data Integration
Maintain Between Systems Mapping for Visual
Infrastructure Data Analysis and Reporting
Web and Mobile-

based Clients
Enterprise
Technology
Manage Large
Spatial Databases
Remotely Access
Central Web Access to
and Edit Data
Information Resources
Support Business
(including GIS)
Processes with Applicable
72 GIS in Transportation Spatial Information
STANDARD DOT FUNCTIONS
Administration
Planning / Environmental Engineering Operations Maintenance ROW

Programming
•Advanced Planning • EIR • Design • TMC Pavement •Property

Management
•STIP •Air Quality • Construction • Signs / Signals •Utilities
System (PMS)
•Inter-Agency Plng •Hazardous • Construction / • Counts / Surveys •Property
Maintenance Mgt
Waste Project Mgt
•Inter-Modal / Goods • W-I-M System (MMS)
Management
Movement •Noise •Leasing
• Overweight Landscape
•Structures
•Aeronautics •Storm Water Permits
•Transit • Closures /
Detours
•Rail
• Traveler Info
•CMAQ
• Safety
• ITS
• Micro-Simulation
Modeling
Data Integration
Pavement Data
Roadway Imagery
HPMS Data
Spatial Data Supporting Asset Lifecycle
SHA’s IDS Highway Information Management
SEMI
PI 60% FINAL
30% 90%
• Query about asset at any time in lifecycle STUDIES

PS&E
100%
Directly DESIGN
• View asset as feature SELECTED

ALTERNATE
ADVERTISE
With GIS data FINAL

REPORTS PLATS
ADDENDA
• View design plan

ENVIRON
CONSTRUCTION
DOCUMENT
PLANNING
ENGNR CONTRACT
MAPPING DOCUMENTS
Any phase to as-built PUBLIC

HEARINGS
ELECTRONIC
FILE ROOM
SHOP
DRAWINGS
Information
• Ask questions across db’s GIS DATA
MAPPING
Management AS BUILTS
ALTERNATES REDLINE
Integrated data model RETAINED
SPECS STANDARDS
FIELD
CHANGES
• Make decisions about asset ALTERNATES

WORKSHO P GREEN
LINES
In any phase MAINTENANCE

GIS DATA NON
ADVERTISED
PROJECTS
ASSET INSPECT
DATA FEDERAL REPORTS
REPORTS
Enterprise Implementation
Web Services-centric
Application Server
(Enterprise Integration)
ERP ArcGIS
ECMS
RDBMS
RDBMS
RDBMS
Enterprise Business Enterprise Spatial

Systems Systems
Core Technologies
Enterprise Implementation
• Four core technologies which are central to a

DOT IT Architecture:
– ERP: Financials and HR systems
– Electronic Content Management Systems
– GIS
– RDBMS
• To support the Enterprise, these systems

should be integrated
ERP Integration
• Why?:
– Project Management and Tracking
– Consistent Project Financials through Planning,

Design, Construction, Operations and
Maintenance: capture full life cycle costs of projects
– Integrated Maintenance and Work Order

Management
– Linkage to HR Systems
Construction and Project Management
Design and Estimating
Project and Construction Management
Facility (Asset) Management w SAP
Facility Management
ECMS Integration
• What is an Electronic Content Management

System? 6 Key Components*:
– Document Management (DM)
– Web Content Management
– Records Management (RM)
– Document Imaging and Capture
– Document Centric Collaboration
– Workflow
* Gartner
Why Integrate?
Disparate information management

technologies have arisen that cope with the
special characteristics of different types of data.
• DBMS for structured, tabular data

• ECM for unstructured documents and files
• GIS for spatial information
Goal is to Remove Barriers between
Information Technologies
Spatial Document
User Integration User
GIS ECM
Business RDBMS
Requirements
Tabular User
Why Integrate?
So that users are not burdened by the fact that some of

the information or functionality they might need is in one
system while the rest is somewhere else.
“ A seamless flow of information regardless of format,

platform or location”
DynSeg Link
Geo-Registration
ESRI’s Content Management Relationships
ESRI Corporate Alliances ESRI Business Partners

• Documentum • Hyland Software (On base)
• Hummingbird • Spescom Software
• FileNet
• Laserfiche
BP Integrators:
• GIS Technology Inc (GTI)
• OpenText
• Spatial Data
• IBM • MetaCarta
• Many Others
Enterprise GIS Products and Tools
• We hope we have made the Case for an
Enterprise GIS, and the Integration of the Core
Technologies
• How does ESRI help you achieve this Goal?:

– Enterprise Software Products
– Common Component Architecture
– IT Standards Based
– Interoperability
– Established Relationships with More Leading IT
Companies than Anyone else
– Continuous Research and Product Development
– Commitment to our Customers’ Success
Best Practice Solutions
Planning Applications
Long Range Planning
• The Major Demand Forecasting Packages are

integrated with ESRI Technology:
Long Range Planning
Long Range Planning
Transportation Improvement Plans
NY DOT TIP Project Tracker

Goods Movement
101 image—
image—
Intermodal Facilities – Public Review

Florida DOT’s Intermodal Application

Environmental Practice

Environmental GIS
• Project
Review
Focus

Environmental Site Analysis

Greek Rail
Washington DOT

Environmental Review

Environmental Justice Review

Ozone Concentrations

Design

CAD/GIS Translation
CAD Drawings
Geo-Processing
Models
Geo-Processing
Models
Geodatabase

CAD / GIS Integration

As Builts

Design and Estimating

Construction

Greek Roads: Egnatia Odos

3D

Soils

Geotechnical

Archeological Excavations

ΑΡΧΑΙΟΛΟΓΙΚΕΣ ΑΝΑΣΚΑΦΕΣ

Web Site: Current Hwy Status

Construction Management

Construction and Project Management

Operations

Real Time Control Rooms Are Becoming
Spatially Enabled

Incident Management
All Information is
Map+Detail page. Clicking on an incident symbol logged in the database
displays the incident details.
www.511.0rg
Traveler Information Systems

ITS and Traffic Management

RWIS

Evacuation Systems

Geneva : Real time information
¾ State of traffic
¾ Parking
availability
¾ Live images
(cameras)
¾ Road works
on the public
highway
www.geneve.ch/infomobilite
ITS & Traffic Control Systems

RTA Traffic Management

Siemens’ Comet System
Traffic
Management
Anomaly
Detection
Congestion
Monitoring
Incident
Management

Traffic Management: Frankfurt
GIS-System
based on
ArcGIS
additional
laminar view

Traffic Conditions
Generic diagrams for any data
Visualization of traffic state
Journal component

Traffic state information
Traffic state in Munich

on the motorway
Traffic state in Frankfurt via

Internet and ArcIMS
142
Toll Collection
GIS is used for managing 3,500 toll station terminals

along 12,000 km of motorways and 2,500 junctions
BAIRS GIS

WYDOT Oversize Routing & Permitting
ArcView
BRASS Integration
Network Routing
US DOT: Nation Wide Highway Performance Monitoring
System (HPMS)

TxDOT: Load Restricted Bridges

Ticket and Accident Location

NYS Accident Location Information System
Location Coding Data Entry Module

Custom ArcGIS Server Analysis
Show
ShowMeMethe
the
Top
Top25
25Crash
Crash
Locations
Locations

Analytical Tools

Analysis and reporting

NYDOT Planning Analysis
Example of using GIS to integrate several Management Systems
to deliver better decisions
• Pavement Surface score = 6 candidate for simple paving job

• NYDOT did not want to pave highways with certain
accident histories without safety analysis Pavement Management
– Speeds increase on new pavement could Congestion Management
exacerbate the safety problem Accident Management
• Pavement score on Mile Point
• Accident data on Reference Marker
Maintenance

Pavement Management

Maintenance and Inspection Management

Asset Inspection

Bridge Inventory

Work Order Management

Right of Way

Property Acquisition

Conclusion
• Integration to Support Agency-Wide Business

Functions:
– Need to provide easy access to data and

information: “ A seamless flow of information
regardless of format, platform or location”
– Need to integrate data across the enterprise; to

integrate the DOT “project lifecycle”

Questions?

Server GIS supports your needs
Sanitation
Truck Routing
Model Development,
Server Editing Workflows,
Asset Management,
GIS etc.
Public Works
Pavement
Department
Condition Parcel &
Landbase
Zoning Maintenance
Application
Server
GIS Server
Centerline Editing
GIS
W
Central IT Planning
W
W Department Department
Field Data
Collection
Public Access
Website
Mobile Applications ERP & other
business systems
Integration

2007-09 GIS in Transportation

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2007-09 GIS in Transportation

Uploaded by

Copyright:

Available Formats

Transportation Special Interest Group Meeting

• Purpose of the Meeting

• Linear Referencing Systems and Dynamic

• Temporal Data Issues

• Routing / Dynamic Routing

• ESRI User Conference

• Best Practice Examples

– Linear Referencing in ArcGIS

– Linear Referencing in ArcGIS: Practical

• SLDs and GIS

• Represents Historical Way Data was Stored

• An Engineering View of Roadway – Often the

• Represent all Roadway Characteristics on a

• Carried into the Field for Inspections /

6.216 12.984 20.395

1.033 4.002 8.311 15.638 22.478

R8-3 W1-2R W1-2L

Pavement Condition Table

• SLDs were Designed Prior to GIS and

• Now that GIS can represent all of the

• Tools for Manipulation

• Past, Current & Future Networks

• Highway Realignments and Accident Data

• Roadway Conditions at Different Time Points

Table Enhanced class template

User User User

• Peer to peer • Read-only ‘cache’

. . . Key Technology For GeoWeb

• Same basic route

• ESRI is currently building full Dynamic Routing

• These applications are for personal and

Server Finds Shortest Time Path Delivers to Any Client

• ESRI User Conference

• Best Practice Examples

• 14,000 Users From Around the World

• New Transportation Data Model

• A “How-To” Book: Step by Step to Design and

• Designed for all Levels

• Due for UC 2008

• Integration to Support Agency-Wide Business

– Need to provide easy access to data and

– Need to integrate data across the enterprise; to

• Why an Issue? Because Increasingly the Most

– 85 Percent of Data in Modern Organizations is Unstructured*

• DOTs are often plagued by Stovepipe

• Data is located at the application level, often in

• Major Gaps in Information Flow across the

• Support for a Distributed Environment

• Desire to support best of breed COTS

• Need to provide technology which supports

• An information system is a tool for providing useful

• Approaches to Enterprise Application

– Point to Point APIs

– Data integration / Data Warehousing: through

– Service Oriented Architecture: integrating

Integration Platform and Workflow Applications

• Allows you to build applications, drawing data

• A flexible and agile integration framework;

• Reflects IT Best Practice: “By 2008, SOA will

An approach for building distributed computing systems

• Additional Long-Term Benefits

Service Orchestration - BPEL

• Regardless of your approach (data warehouse,