Stakeholder Consultation, San Diego, June 24-25
Notes on the Day One (Saturday June 24) Presentations, recorded by
Kevin Curtin
Shift-click on the Zip file links to download
Mike Goodchild
One object model or many?
Subdivisions: {Railroads, Transit, Asset Management, Transportation planning,
Engineering, Airports}
Single model to fit all subdivisions?
How much consensus?
Users can refine objects
Don't straitjacket users
Recognize how a particular application fits in the object model
Who isn't represented?
Can we link scales and applications?
What are the objects?
What can we achieve before next meeting?
How to refine Arc8 object model to fit transportation?
Pathological cases?
Ernie Ott
Think about recruitment of under-represented stakeholders
Stakeholders meeting December 2000
European meeting Torino 11/5
Facets of UNETRANS
Build ODM for next Network (core and extensions)
Network/Routing
Linear Referencing
Geo-coding
"Street furniture" Placement
Describe Infrastructure objects for: {Roadways, Railways, Runways, Ports,
Canals, Ferries}
ArcFM Water has related but separate models
UNETRANS - ArcGIS
Define a useable GIS data model that represents transportation themes
Build a data model that works
Build with core ArcGIS technology (standard types in the Geo-Database)
Make the model shared
Why ArcGIS data models
Facilitate widespread access
Develop standards
Provide a framework for each industry
Encourage partners to build on a common platform
UNETRANS Model Goals
Build the Essential data model (not the comprehensive data model)
Work with partners
Publish and share the data model
Help users expand
Four Parts of UNETRANS
-
User and partner consortium input
-
Business partners
-
Develop geo-database "template"
-
Mechanisms for sharing the data model
-
Book - based on ArcFM Pipes/Water
-
CD with data
-
Geography network website
Foundation for solution
-
Core technology
-
ArcMap
-
ArcCatalog
-
Geo-database
-
Topology
-
Versioning
-
Rendering
-
Data model
-
Solution providers
Concepts of Data Modeling
Common component of all projects
Significant time spent on data modeling
Data migration is the longest and most expensive part of any project
Coverage replaced by geo-database
Geographic primitives remain in ArcInfo 8
Contents: ArcGIS UNETRANS Model
-
UNETRANS Book
-
CD-Rom
-
Sample database
-
Analysis diagram
-
UML
-
Symbology
-
Website
Dale Honeycutt
Overview of data modeling ArcInfo 8
Required reading
Modeling Our World
Building a Geo-database
Geo-database - new kind of coverage
New format
Objects with behavior
Layers
In coverages behavior is encapsulated in the applications
In geo-databases
Layers in a single file
Features in layer can have user defined behavior
Object = Identity + state + behavior
Object = name + attributes + methods
Core Objects
Object classes
Rows in databases
Unique ID
Non-spatial
Feature classes
Objects with geometry
Primitives
Network feature classes
Network connections
"kind" of feature
Data Modeling I
Inheritance
Relationships
Subtypes
Eliminates many classes
Performance enhanced
Attribute domains
Legal values of a field type
Can be shared among objects and classes
Connectivity rules
Maintain a valid network
Edge/junction rules
Edge/edge rules
Merge/split rules
Metadata
Stored as XML
Viewed and edited in ArcCatalog
Data Modeling II
Taxonomy of things (add behavior)
Model of behavior (add things)
Navigating models
Classic relational operations (SQL)
Network
Addition of topology
No formal query language
Model of behavior
Mechanics
UML object model (visio)
UML is not a substitute for "telling the story"
Document use cases
Microsoft repository
Code generation
Schema creation
Data model extensions
Not proprietary
Provides a standard
Modeling linear features
Weights on complex features based on merge/split rules
Apportioned across complex features
Bitgate weights
Efficient
Not user friendly
Difficult to add modes
Current limitation on number of bits
Barriers and flags (parts of solvers)
Not on the network
Place where you point
Construction zones
What we don't have
Solvers
Turns
Geo-coding
Street map (see graphics)
Potential Topics for Break-out
Groups
Transit
Travel Demand Forecasting
Asset Management
Scale
Logistics
Linear Referencing
International
Maintenance/Conversion
Dynamics/Real Time
Multi-Modal
Geo-coding