Stakeholder Consultation, Redlands, December 7/8
Proceedings
On Thursday the development team presented the current draft of the model.
Although questions were officially limited to clarifications, they evolved
into discussions. On Friday we broke into two groups: one dealt primarily
with linear referencing; the other focused on infrastructure object hierarchies.
There was a short summary of the breakouts, and the meeting adjourned at
3 p.m.
In general participants felt the model as presented was 80% satisfactory,
with additional work required in a few areas as detailed below.
Package 1 Navigable Transportation Network
Working draft of this package as
presented (GIF)
Comments: require additional work on
-
Carriageways
-
Sidewalks
-
Events in pathfinding
-
Scaling of attributes
Note: some of these comments are already reflected in the draft linked
above.
Package 2 Assets
Working draft of this package as
presented (GIF)
Comments: require additional work on
-
Rail infrastructure
-
Time
-
Condition
-
Event as a project
-
Point assets: streetlights, trees
-
Linear assets: striping, reflectors, etc
-
Polygon assets: Right of way, Traffic Analysis Zone
Note: some of these comments are already reflected in the draft linked
above.
Package 3 Vehicles
Working draft of this package as
presented (GIF)
Comments: require additional work on
-
Time
-
Start, stop position: goes from depot to ...: model as a separate object
class
-
Transport vehicle: capacity as user-definable object (hook; show example
only)
-
Distinguish between piggybackers (e.g. railcars and pedestrians) and free
agents (e.g. bicycles, ships, etc)
-
Truck types: see 13 federal classes defined by FHWA
-
Fleet aggregation: aggregate ID
-
Relationship to network
Note: some of these comments are already reflected in the draft linked
above
Package 4 Business
Working draft of this package as
presented (GIF)
Comments: require additional work on
-
Linear referencing: should be part of a separate Locators package?
-
Route
-
Turns and addressing don't belong in the business package
-
Business needs are best addressed by providing hooks to external enterprise-defined
models
Note: some of these comments are already reflected in the draft linked
above
Package 5 Relationships
Working draft of this package as
presented (GIF)
Comments: require additional work on
-
Simple vs complex edge: combine?
-
Lane migration
Note: some of these comments are already reflected in the draft linked
above
Package 6 Linear Referencing
Working draft of this package as presented (GIF)
Comments: require additional work on
-
Mimics 20-27(2). Better to capture essential objects of 20-27(2)
rather than to reproduce it
-
For example, 20-27(2) separates line (cartography) from topology, whereas
in the Unetrans model these come together in the TransportEdge. Similarly,
node, link, etc, do not need to be defined as part of this package.
Note: some of these comments are already reflected in the draft linked
above
The UNETRANS Book
The book accompanying the model will be organized as follows:
-
The model
-
Modeling requirements of specific user communities (e.g. transit, linear
referencing)
-
Guidance on modeling difficult pathological cases (e.g. HOV lanes)
-
Use cases
-
Applications
Schedule of Action Items
January |
Glossary/standard definitions
of terms |
January |
Data model description:
30 pages |
March |
Model ready for test deployment |
July |
Presentation and review
at ESRI User Conference |
October |
Final copy |
December |
Accompanying book published |
Post-conference note: this schedule is being pushed back
Technical Contacts
For further information please contact one of the UNETRANS technical team
reps (below).
ESRI
Jennifer Cadkin <jcadkin@esri.com>
Steve Grise <sgrise@esri.com>
Ernie Ott <eott@esri.com>
UCSB
Kevin Curtin <curtin@ncgia.ucsb.edu>
Mike Goodchild <good@ncgia.ucsb.edu>
Val Noronha <noronha@ncgia.ucsb.edu>